This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 51%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERR%3C/text%3E%3C/svg%3E)
In my testing, my test 1909 machines are seeing all updates except for these, even after reboots:
Windows 10 June 2021 Cumulative Rollup Update for Version 1909 (KB5003635)
June 2021 Servicing Stack Update for Windows 10 Version 1909 (KB5003710)
Both of these patches are listed in WSUS and deployed with everything else, the Office security updates and the Third Party updates from PatchMyPC. All other updates installed just fine.
These computers have the April 13, 2021 servicing stack update (SSU) (KB5001406) and also have the May 11, 2021 Servicing Stack Update for Windows 10 Version 1909 (KB5003244).
I have been deploying Windows Updates from Microsoft via WSUS for 11 years. I worked for Microsoft Technical Support from 1998 to 2004. There have been many Windows 10 versions that have come and gone. All versions that went end of life still had updates available for several months after the technical end of life date. Never yet, until now, have I seen Windows Updates fail to install when they were offered via WSUS.
As a test, I manually installed the June 2021 Servicing Stack Update for Windows 10 Version 1909 (KB5003710) downloaded from Microsoft’s Update Catalog last night on one PC that had this issue and has never before had an issue with Windows Updates.
I rebooted, then checked WSUS again for any security updates, such as KB5003635. None were found. I checked again this morning. Same issue. I installed KB5003635 manually. It went through the install, provided Installation Complete screen, rebooted, got to 98% complete, then failed, and rolled back. Windows Updates on this computer shows Windows Updates error 0x800f0922.
I took another computer, that also had this issue and had never had an issue with Windows Updates, and I manually installed the Windows 10 June 2021 Cumulative Rollup Update for Version 1909 (KB5003635) to see if it would install on a computer that did not have the June Servicing Stack Update KB5003710 installed, but had the April and May Servicing Stacks. It went through the install, rebooted, then failed, and rolled back.
I installed KB5003710 manually. I installed KB5003635 manually. It went through the install, provided Installation Complete screen, rebooted, got to 98% complete, then failed, and rolled back. Windows Updates shows error 0x800f0922.
I went into WSUS and imported KB5003710 and KB5003635 into WSUS, but it didn’t help – the updates were still not seen by my endpoints.
I took another computer, with Windows 10 20H2, and checked for updates. It installed Windows 10 June 2021 Cumulative Rollup Update for Version 20H2 (KB5003637) without issues.
I checked https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-10-1909 but the issues with KB5003635 are not listed there.
I think there is an issue with the updates KB5003710 and KB5003635. Could someone look into this and fix the issue? We have 5,000 computers with Windows 10 1909 that are now in the lurch. Let me know if you would like the WindowsUpdates.log, or if the issues I am seeing with the two updates could simply be fixed.
Sincerely,
Richard Roati
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 10%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBR%3C/text%3E%3C/svg%3E)
Hey, I am working with a MS Engineer on this right now and one thing we noticed was the machines this is failing on has a super old copy of robocopy from 2003 in C:\Windows\System32\Robocopy.exe. Are you seeing the same thing?
Ok, we managed to use a workaround in our company. The issue was Microsoft issued an update to robocopy.exe and when performing the patch install we had a very old version of robocopy on our system which the patch didn't like as the hash values didn't match. It was getting the robocopy from C:\Windows\WinSxS\amd64_microsoft-windows-robocopy_31bf3856ad364e35_10.0.18362.1_none_99649f7c699cab99. The way to see which file the patch doesn't like go to C:\Windows\Logs\CBS and open cbs.log with notepad++ or your preferred log reader. Look for failures. Ours showed access denied and robocopy.exe failed.
You said you had a more recent version of robocopy so i don't think your problem is robocopy.exe but another file hash value isn't matching up with Windows pushed down. We are still investigating how we got a really old version of robocopy on our systems. It seems to have come during imaging by a certain application.
In meantime, we copied robocopy from a good system and copied it to its own side by side folder in C:\Windows\WinSxS\amd64_microsoft-windows-robocopy_31bf3856ad364e35_10.0.18362.1_none_99649f7c699cab99. This did require to manipulate the security settings in file and parent folder.
Hope this helps you!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 93%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
Same issue here, we dont use WSUS but we use Vmware Workspace One and also KACE SMA as an optional deployment MDM and neither can deploy. Im not 5000 but around 350 on 1909 so we are hanging in the wind on this. Microsoft, this is urgent.
We are having the same issue here as well. Other updates install fine except KB5003635.
Since the issue only occurred on 1909 machines, if it is feasible, please upgrade your clients to 20H2 or 21H1 for patching.
If it is infeasible, I suggest to pause install KB5003635 for a period of time or skip this KB and wait for the next, we have submit this case to Microsoft via our channel.
Please note, Debugging windows log is beyond scope of forums support so if further assistance were needed you could open a request ticket with Microsoft support.
https://support.serviceshub.microsoft.com/supportforbusiness
-------------------------------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you Teemo Tang, for submitting this case to Microsoft via your channel.
Please let us all know what is Microsoft's response.
Also, Microsoft released KB5003646, the June 2021 Cumulative Patch for Windows 10 1809, on June 8, 2021. Can Microsoft confirm whether this patch works as well, and also fix it if needed? We have 72 computers with Windows10 1809 and we would also like to see this patch work.
Thanks,
Richard Roati
Hi BahenaRene-5074,
Thank you for working with Microsoft regarding the inability to install KB5003635 on Windows 10 1909. I can confirm that C:\Windows\System32\robocopy.exe on our 1909 machines is dated 3/18/2019 and is 132 kb. Please keep us posted on the progress in fixing KB5003635 and KB5003646!
Thanks,
Richard Roati
Hi BahenaRene,
Thank you for posting your resolution, it gives me hope!
I checked the C:\Windows\Logs\CBS\CBS.log for the word "fail" on one of the computers I tried to install KB5003635 on manually as well as from WSUS, but didn't find much that would help, only this:
2021-06-11 10:18:31, Info CBS Appl: Evaluating package applicability for package Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~10.0.18362.1, applicable state: Installed
So, unfortunately, I don't think that helps much. :)
I would load the CBS.log to this post, but it is apparently too large for the forums. :(
Meanwhile, MS has released a new servicing stack update for Windows 10 1909 in WSUS today, KB5003974.
So far, it is not seen either by my endpoints either.
However, it does give me hope that MS is still releasing updates for Windows 10 1909.
Just took a look at the file and it seems too small. Mine was over 100MB in size. I did a search but there wasn't much in that log file.
Thank you for looking, Rene.