Run setupdiag > post a share link into this thread
https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
Uninstall any of these non-Microsoft software:
a) antivirus
b) firewall
c) drive encryption
See if you can perform an in place upgrade repair using a Windows 10 iso 21H1.
If the in place upgrade fails > post any error code and message
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
https://www.microsoft.com/en-us/software-download/windows10
https://www.tenforums.com/tutorials/9230-download-windows-10-iso-file.html
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
On the bottom of each post there is:
Propose as answer = answered the question
On the left side of each post: Vote = a helpful post
.
.
.
.
Thanks for the responses. I've still been struggling with this. I've tried with antivirus disabled on test workstations, done the windows update troubleshooter, reset windows update, etc. All of the suggestions you normally see when you search solutions online short of a Windows reset. Ultimately, I tried upgrading one using the media creation tool. That took forever, but seemed to stabilize it and get it to 21H1. Not exactly an ideal solution seeing as though most of our desktops appear to be affected by this.
TTo answer a previous question, we have a WSUS server deployed, but dual scan is enabled on the desktops. So while they check into the WSUS server, their actually getting their OS updates from Microsoft. I've tried the check online for updates as well, but that does not seem to make a difference. I've also disabled dual scan and tried serving updates directly from WSUS, but that hasn't changed the results either.
So right now my only clear fix appears to be an update via media creation tool. Not sure what else I can do at this point. If there are people following this thread who understand the Windows Update Log better than I do, I can post a snippet of the log from a failed attempt. I can see different failures and codes in there, but nothing I have been able to make sense out of or has led me to a solution.
@Robert Sturtevant
I understand your current difficulty, it seems that updating through media creation tools is the only feasible way at the moment.
Since most machines in the environment have similar problems, it is speculated that there may be problems during deployment
Due to security policy, community support cannot download and save user’s personal data such as dump or log files, please install WinDbg from Microsoft website and analyze crash dump files.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools
If this problem is more urgent for you I still recommend that you open a case to Microsoft for further professional help.
https://support.microsoft.com/en-us/help/4341255/support-for-business
Haven't commented on this in a while. But just thought I'd update that the solution to this appears to be a full computer shut down followed by a power on. We have done this to multiple computers experiencing the issue so far, and they have applied their updates fine afterward. Restarting doesn't do it. It has to be a shut down. Very weird. Just posting here in case anyone might no of what mechanism may be happening during a shut down that is not happening during a restart that may be impacting the updates. If I can figure out what that is, then maybe I c can reset it administratively without having to find a way to power off and on all those remote PCs. Otherwise, at least I have something that seems to work. Thanks again for all of the input.
Sign in to comment