Windows 10: Failed Upgrade to 2004

Split from this thread.​

Greg, Everything had been running fine until Windows decided to update/upgrade itself, I think from 1903 to 2004. I thought I had blocked any feature upgrades because when 2004 first installed several months ago I lost all usb 2.0 functions and had to have 1903 reinstalled.


The upgrade took a very long time to complete. Now when I start up the computer I get to the spotlight sign on screens, I am able to sign in, but then all I get is black screen which I can see the mouse pointer. Contorl/Alt/Delete brings up the task manger menu but all that functions is log out or shut down. Executing task manger takes to to the black screen and mouse pointer.


I tried a bios boot to system recovery and then system restore hoping to be able to go back to 1903. It's telling me there are no restore points. I know I created restore points several times.


Can this be salvaged without completely reinstalling everything all over again?


Pics attached.



:)

 

Ssd upgrade

What do you mean "no good"? At which step did it fail?

 

Windows 10 version 2004 upgrade fails with error 0xA0000400

Hi,

Did you try using the Media Creation Tool? Please note that even if your device is listed as compatible your device may not work as expected.

Try updating to version 2004 using the Media Creation tool and if it fails let us know.

The fastest way to get the upgrade is through the Media creation tool or ISO file.

Please download Media Creation Tool from the link below and select Upgrade this PC at the first screen.

https://go.microsoft.com/fwlink/?LinkId=691209

All steps, including upgrading using ISO file and Media creation tool, are covered here:

https://www.yourwindowsguide.com/2020/05/featur...

Content on the above blog is written by a Microsoft MVP so it is safe.

 

Problem with 2004 IS0

It does help if you read the replies *Wink I mentioned the 4GB Fat32 limit in post #6

As for getting MCT to run on your machines, I showed in post #6 a screenshot of it running on mine.

In post #18 I suggested troubleshooting steps to get the MCT to run, and if that failed a way to split up an install.wim that's larger than 4GB.