Server patchers – issues with KB4601318

Topic

New Reply

KB4601318 fails to update, fails at 24% Windows Server 2016 – Microsoft Q&A Just a heads up for those doing patching on Server 2016.  Reports from
[See the full post at: Server patchers – issues with KB4601318]

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

mcbsys, abbodi86

Reply | Quote

Replies

I just synced our WSUS server again, and Microsoft has pulled KB4601392, which is the servicing stack for Server 2016. That’s likely the culprit.

Reply | Quote

Updates on Server 2016 are a disaster. I remember Windows 10 1607 (its client sibling) had the same problems with stuck updates and I’m surprised that it was never fixed. Even when the updates do install, it’s incredibly slow. I know of a handful of clients that upgraded from 2016 to 2019 for this reason alone.

Reply | Quote

A recent comment in the thread Susan linked includes a link to this post about Feb 9 updates:

https://support.microsoft.com/en-us/topic/february-9-2021-kb4601318-os-build-14393-4225-c5e3de6c-e3e6-ffb5-6197-48b9ce16446e

This post now confirms, “KB4601392 has been removed and will no longer be offered to devices. We are working on a resolution and will provide an update in an upcoming release.”

Reply | Quote

We have already deployed the Feb SSU to 2016 and don’t download or deploy “Express Updates” on our SCCM / SECM 2002 site, which was the mitigating factor for further deployment of the Feb Monthly CU for 2016 deployment.  But that was before the update was pulled completely.

Does any know if we are going to fail at 24% for deploying the CU even if you don’t do “Express Updates”?

Reply | Quote

I have a Sev A call open with MS Support. What they are telling me and this is based on internal docs and discussions with the devices team is that the issue with SCCM aka SECM is if you have your Software Updates setup to allow Express Updates. If this is turned on and you have deployed the 2016 Feb SSU you get the problem. If you don’t do Express Updates you should not see an issue with the Feb 2021 Cumulative Update installing.

We deploy SSUs ahead of our normal scheduled weekend maintenance windows so we have over 3000 systems that already have the Feb 2016 SSU for 2016 KB4601392 installed and are not going to pull the Feb 2021 CU for 2016 KB4601318 from the SUG and see what happens during the early windows to decide if we are going to halt that deployment.

Reply | Quote

https://twitter.com/jandreacola/status/1360356112592228361

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote