Nice to see your issue is solved.
All users don't get 21H1 same time, but build 19042.1055 is latest available for 20H2.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Windows 10 Pro
Build 19041 release 191206-1406
I know the Windows 10 files are problematic. Windows updates occasionally install, but mostly don't. The package files are corrupted, according to Tweaking.com. I've had this happen before with other PCs/builds, and updating with the ISO file always solves the problem, until now.
After running through the initial set up, the system only gives me the option to install without keeping anything. Reason given is that Windows is installed in a non-standard directory. This, of course, is not the case, it's installed where it should be.
I would REALLY not want to go this route. It seems extreme and there must be a way to get this fixed. Yes, all files are backed up 2x. Yes I have a boot disc.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Nice to see your issue is solved.
All users don't get 21H1 same time, but build 19042.1055 is latest available for 20H2.
I would wait to see if you receive 21H1 automatically via windows update. This is via an Enablement package and so is a small quick update. You may find you get further cumulative updates or select check for updates in Settings > Update and security.
There is no need to try a repair first (I don't think) if you want to try the Upgrade Assistant via
http://www.microsoft.com/en-us/software-download/windows10 to manually update to 21H1 then that is up to you. If it still doesn't work then you can go the repair route first by using the 20H2 ISO file.
Glad it worked out in the end by the way, or so far at least.
another note I would remove the email address from your screenshot.
Thanks Sumit, this is the page with registry edit I was referring to, but I couldn't find it. Bookmarked now.
You are welcome :) There are a lot of people who are stuck on 19042.630 or earlier, so the article is still handy.
>I wondered if updating to a later build using the catalog might help that.
That would be one solution which I mentioned on page 2.
I have seen registry trick (didn't find it now) how to turn 19042 to 19041 and get inplace repair to work, but when you edit registry you have to know what you are doing to avoid disaster.
OK. I edited the registry and apparently I was successful. It was OS Build 19042-630
There's been a lot of info in this thread and so I don't get it wrong now that this is fixed what are my next steps?
I believe repair with 20H2 and then update to 21H1, or do I attempted to update to 20H2?
This is the first thing that apparently had an impact, and I'm hoping this will continue.