Your Device Is not Ready Vs 2004

My message has changed a bit.

Attached is the Sysinternals BSOD File collector results of the old computer. Tell me if I need to start a new thread in the BSOD section

Just an FYI - Since the op used a image from a pretty old machine which probably has a lot of old baggage (IE un-supported drivers, etc), and now the op wants to upgrade to the latest and greatest version of W10, there are many good reasons why it doesn't install. Since the new system is only 6 months old I assume that the version he installed is 1909 or at least 1903 ?

I question (other than not wanting to re-install 10yr old software) on a new system, why the op chose to dump an image of a 10 year old system on his new 6 month old system. If the OP bought the new system it probably had one of the latest versions of W10 on it from the factory. But if the OP built the new system from the ground up, how did an image from a really old system get registered with MS licensing ? Please explain ?

Attached in the Sysnative BSOD File Collector for the 6 month old Gigabyte Motherboard.
The 10 year old machine has been continuously updated. The Gigabyte Motherboards drivers are the same and there are no newer ones for this motherboard. All devices are working correctly no yellow flags in the Device Manager. Image has steadily upgraded from 1703 to 1909 on the old computer after every 6 months with no issues. I took an image of the computer at 1903 and restored it to the Newer Gigabyte motherboard computer. Then I upgraded each Desktop to 1909 using the same downloaded ISO image. Both computers work flawlessly. Using the same downloaded ISO image for 2004 on both computers, they both fail with BSOD on second boot. Exception Thread Not Handled. Both computers have the latest nVidia GPU driver from the nVidia web site. Please check the BSOD collector zipped file for more info

I' m unclear. The Panther file is too large zipped up to attach.
I believe the Sysnative log files that were previously attached hold the same information

All of these logfiles are already collected in the Sysnative Zipped file that is attached, please read them First

V2 log collector results:

:\WINDOWS\system32>Setupmem.dmp'Setupmem.dmp' is not recognized as an internal or external command,operable program or batch fileC:\WINDOWS\system32>setupapi.dev.log'setupapi.dev.log' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>BlueBox.log'BlueBox.log' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Event logs (*.evtx)'Event' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>C:\$Windows.~BT\Sources\RollbackC:\WINDOWS\system32>$Windows.~bt\Sources\Ro llback\setupmem.dmpThe system cannot find the path specified.C:\WINDOWS\system32>$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.logThe system cannot find the path specified.C:\WINDOWS\system32>$Windows.~bt\Sources\Rollback*.evtxThe system cannot find the path specified.C:\WINDOWS\system32>$Windows.~BT\Sources\Panther\UnattendGCThe system cannot find the path specified.C:\WINDOWS\system32>miglog.xml'miglog.xml' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>Windows\Logs\MosetupThe system cannot find the path specified.C:\WINDOWS\system32>Setupapi.offline.log'Setupapi.offline.log' is not recognized as an internal or external command,operable program or batch file.

Microsoft Security AV- No 3rd party
:MS Firewall- no 3rd party
No encryption
I'm not sure what PS Is?