So it has been a while since I updated windows 10 (feature updates only, others are updated once a week or so) because the installation always fails (and bluescreens) at a random percentage, and that "Undoing changes made to your computer" will appear, over and over. Mostly a bios update fixes it, but doing that is way too annoying for my system, just one problem after another. Does anybody have another solution to this problem? To this day, my device is still attempting updates overnight, I never have stopped it in hope that someday it will actually successfully update, record was past 70.
Firstly, try one ISO which has been integrated with latest cumulative update to do in-place upgrade. Lastly, go back to the build that won't cause such awkward "repeated undoing" to your device.
What is the device ? If it is a laptop, it may not have any suitable space left for updates. First clean all update files in Windows>Software Distribution>Download, make sure that there is sufficient space in the C drive and try to update. If all of these steps fail, you may have to do a fresh-install. Regards
try mediacreationtool.bat - download the attached zip in the first post - unzip batch file inside - rename batch file as: auto mediacreationtool.bat - double-click to run it will download 21H1 version from microsoft and start the upgrade process with troubleshooting options good luck!
@lammethe24 I'll give one more plus on my part, ie it is that if you already have to upgrade (or reinstall), then why not 21H1 (OS Build 19043.928). It works great, at least I haven't had any problems. I am currently using it on two computers and the reason was similar - I just needed to do a clean installation. Another thing is that you could also provide information about your computer. Then it would be easier to understand what to recommend to you. We don't know anything about your system right now ...
Because it's still considered Beta channel but considering it's the same base as 20H1/2 it probably won't miraculously work. If the bios needs to be updated for the offered build being able to run, then that, most likely, will be the only fix (if the suggestion by @BAU doesn't work, i only would go for 20H2 as long as 21H1 still is beta, don't know why he mentioned 21H1). What build is the system currently running (can you run the QT from here and post the saved report here in code tags (don't post the private version))?
I've suggested 21H1 because I found it working on a potato that otherwise could not setup any 1904x before. It's a long shot. Some configurations simply have blocking issues that prevent going above a certain version. I would use LTSB 2015 / LTSB 2016 on such pesky machines. And of course, the current install could also be broken beyond repair, needing a fresh install. Waiting for a new version to magically fix upgrades is pointless - most likely it won't happen. (and letting the machine go in failed setup loops is very damaging to the hardware on the long run)
??? If done via the script I've shared it does not actually check for windows updates, but for required setup files. MCT needs to download those from the internet, and that uses BITS, then it needs to process the .esd package file and that uses cryptsvc and so on. No wonder it fails for you if you follow bad advice and stop critical services used in upgrading..