Windows 10 version upgrading, there may be such a thing as "jumping too many forward"

[mikeymikec]

For years I've been using an official MS USB Win10 1607 stick to do clean installs with, and mainly as part of the testing process I like to be able to see that the hardware *can* do the work necessary to do a WIndows 10 upgrade.

I think maybe until quite recently, Windows would only offer the 2004 version as an automatic update and going from 1607 to 2004 wasn't ever a problem here. However I think they've changed to offering 20H2 as the auto option, and I couldn't upgrade a brand-new laptop from 1607 to 20H2 or 21H2 (via Windows 10 Update Assistant) because every time I got error 80004005 (aka. "access denied", nothing helpful to me in setuperr.log). I tried a full Windows reset (I've now learnt that a full Windows reset keeps updated drivers which seems like a seriously bad idea to me, but anyway), a second clean install of 1607 (neither install had anything other than Windows installed, first one had manufacturer drivers installed afterwards, second one didn't), no dice. I tried an old DVD with Win10 1803 on and used the Update Assistant (Intel 10thgen and old version of Windows 10 = CPU not clocking beyond the minimum, so updating is very slow) to upgrade straight to 21H1, no problems.

 

[WilliamM2]

Why wouldn't you just start with the latest version? It would have the most up to date drivers.

 

[VirtualLarry]

Newest MSMCT USB version of Win10 won't boot on my 13.3" AMD A4 'Ematic' WM laptop.

I blew away Windows, trying to install the newest version fresh, and now I can't install it. Linux Mint 20.2 Cinnamon installed like a treat though.

 

[mikeymikec]

Why wouldn't you just start with the latest version? It would have the most up to date drivers.

I explained that in the first paragraph of the OP. Synthetic testing doesn't necessarily rule out hardware problems, and real world use sometimes does. I'd rather get a mix of both in if I can.

 

[JackMDS]

This is just general experience of Win 10 Fresh and Upgrade Install

I deal with 22 Desktop (3 locations) about 14 are self build and the rest Dell and HP. There date of release from varies from 2008 to date.

Most of them Run Win 10 Pro x64 21H1, some run Win 10 Home x32 (they run medical software that is Not compatible with x64).

I have No problem with Fresh install or Update from one version to the most recent using Win 10 20H2 using USB Boot ISO.

All of them updated fast and flawlessly using Win 10 21H1 USB Boot ISO. (I did not do any fresh install in last 6 month so I have No data about Win 10 21H1 fresh install).

I also have 6 Laptops, the oldest is a Gateway 17” circa 2008 (original Vista) It ran for years using Win 7 then Upgraded to Win 10 Pro 1709. Currently it runs 20H2.

That said I did have some problem with other Laptops along the line described in the OP.

So.. I do not see any need to go to “”BC”’ times with Desktops.

Win laptops YMWV.

 

[mikeymikec]

I've just had the same issue on a Samsung AIO desktop (Core i3 3220T processor), same error code.