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(128, 27%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERB%3C/text%3E%3C/svg%3E)
Hello All,
So, if you are updating this via WSUS. I found a fix. Please stop and disable the SMS agent host service. Wait for an hour or 2. Restart the computer. Start and set as Automatic to SMS agent host, run the action cycle and see, if the updates are installing fine now.
![](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)
I assume this is on the WSUS server? We dont run Wsus. Im pouring through the logs and cant find the issue. We were pushing to go to 20h2/21h1 but some wont make the leap.. FIgured the reason but no solution yet. MS is delaying the feature release due to firmware.
Hi Bharath,
I don't have the SMS Agent host service on my WSUS Server, and we are not deploying via SCCM. However, the Windows 10 1909 June Cumulative Update won't install even when installed manually on a 1909 Pro computer. My guess is that Microsoft made this patch for 1909 Enterprise only, but I would like to hear that from Microsoft. If this is true, it should be simple for MS to also make it applicable for 10 Pro. Microsoft has done this in the past for all other builds of Windows 10 that technically were end of life in the Pro version.
Last month was the first ever that MS stopped providing updates potentially for three different Windows 10 Pro versions: 1803, 1809, and 1909. We expected that they would stop providing patches for 1803. We were hopeful they would continue to provide patches for 1909 at least, as they had done in the past, as we work through our issues with our 20H2 Upgrade via SCCM. I found the below article to be helpful to keep track of the different Windows 10 Versions. Microsoft's pace in expiring operating systems is getting quicker and quicker. I am hoping for a reprieve for a few months on 1909, which may have been expired unprecedentedly early.
https://en.wikipedia.org/wiki/Windows_10_version_history
![](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(252.8, 46%, 34%)' 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)
KB5003635 is showing as Not Applicable for my Windows 10 Pro Build 1909 computers in WSUS. Is this because this update is only for Windows 10 Enterprise? The July updates for Windows 10 are nearly here. Hopefully the July Windows 10 1909 security updates will show as applicable for Windows 10 1909 Pro.
I am having the same issues installing the July Cumulative Update KB5004946 on Windows 10 1909 Pro as I was having with the June Cumulative update KB5003635 on Windows 10 Pro 1909. The update installs, the computer reboots, the installation gets to 98%, then Windows rolls back the update. I can't upload the C:\Windows\Logs\CBS.log file because the maximum size allowed in the forums is 3.1 mb and it must be a .log file, not a .zip file. If I delete or rename the CBS.log file will a new one be recreated with a smaller size? Is there any resolution to the June and July Cumulative Updates not installing on Windows 10 1909 Pro. The June Update KB5003635 has been confirmed to fail by many users of this forum.
Thanks,
Richard
![](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(243.2, 49%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
This article is what i've been looking for several months since all Cumulative Update on SCCM show as No Require. Hope we're gonna find out a solution for this. Microsoft team, please kindly get it fixed.
![](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(243.2, 53%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hello all.
I'm thinking that the following excerpt from an aritcal on Znet by By Liam Tung | May 13, 2021 -- 11:12 GMT (04:12 PDT) | Topic: Enterprise Software
Will make my and your issues much more transparent or at least give you insight.
"Windows 10, version 1909 is at end of service on May 11, 2021 for devices running the Home, Pro, Pro for Workstation, Nano Container, and Server SAC editions," it said in release notes, adding that it will continue to support Enterprise, Education, and IoT Enterprise editions. Windows 10 1909 for Enterprise and Education ends on 10 May 2022.
That explain why I stuck regardless because my windows 10 pro 1909 will not be included in any updates or patches going forward regardless of my efforts to install
them as my version is not included in the update release supported versions going forward.
Even manual install come up with " is not applicable to your version"
I guess that my rig is going to become a stand alone just to keep my 3D functionality working on one specific flight simulator game.
Bestest.