Forum Discussion
Unable to Print after installing 2021-09 Cumulative Update (KB5005573)
We have the same problem. Uninstalling KB5005573 seems to fix the printing issue for windows 10 users, however having less luck w/windows 7 users- keeps asking to reinstall drivers, does so (takes forever to install drivers), then fails to print. rinse and repeat...
I'm actively looking for solution, and will post what I find to all forums I visit, please reciprocate in kind?
Thx,
RS
Night now, our fix is to not install. But will update you if we come up with anything else.
Michael
- GeekNaHalfSep 16, 2021Copper Contributor
Here are the KB's to watch out for: (that I've found so far)
2016 - KB5005573 2019 - KB5005568 2012 - KB5005613
RS
- Simon_LauOct 14, 2021Copper ContributorThanks. Removing KB5005573 also fixed MacBook printing issues using Equitrac client with Windows backend server.
- GeekNaHalfSep 16, 2021Copper ContributorUpdated list per: https://candid.technology/printnighmare-patch-windows-issue/
KB5005606 (Windows Server 2008)
KB5005618 (Windows Server 2008)
KB5005623 (Windows Server 2012)
KB5005607 (Windows Server 2012)
KB5005613 (Windows Server 2012 R2)
KB5005627 (Windows Server 2012 R2)
KB5005568 (Windows Server 2019)
KB5005615 (Windows 7 Windows Server 2008 R2)
KB5005565 (Windows 10 2004, 20H2, and 21H1)
KB5005566 (Windows 10 1909)
RS- OneToad4uSep 20, 2021Copper Contributor
GeekNaHalf patching caused quite the commotion for me this morning. I ended up rolling back KB5005573 and restarted the print servers. It would appear that this has been long in the process according to this link: https://support.microsoft.com/en-us/topic/managing-deployment-of-printer-rpc-binding-changes-for-cve-2021-1678-kb4599464-12a69652-30b9-3d61-d9f7-7201623a8b25
Unfortunately with everyone and anyone making noise about the issue... I did not feel I had enough time to research the root cause. That article would have been nice to be made aware of prior to patching this last weekend.
I am currently in the testing phase on that article to see if it works or not. I suspect it will work, but I'm not sure why Microsoft doesn't just address the problem rather than disable a feature that everyone seems to use.