Blog Post

Windows IT Pro Blog
6 MIN READ

Known Issue Rollback: Helping you keep Windows devices protected and productive

Eric_Vernon's avatar
Eric_Vernon
Icon for Microsoft rankMicrosoft
Mar 02, 2021
Today I'm sharing details about Known Issue Rollback (KIR), a new capability that can quickly return an impacted device back to productive use if an issue arises during a Windows update. In this blog...
Updated Mar 26, 2021
Version 5.0
servicing and updates
Mike_Pisano's avatar
Mike_Pisano
Brass Contributor
Nov 17, 2021

Vatsan_Madhavan 

If the cloud is the thousands of people dealing with this, then Yes; We were going to push it out via GP, but now their is no point if it wont work in the future.....

I had been testing it with 5006670 in lieu of replacing Win32Spl.dll, Localspl.dll and Spoolsv,exe with the September versions (.1237)

 

Adding 713073804 did fix my issue with 5006670 (.1320) installed, but now with Insiders build KB5007253 (.1379) printing is broken again and this merge no longer works.

 

Analyzing it in Wireshark, All our issues seem to be related to the newer print stack forcing NTLM_Negotiate  & Challenge  followed by the new encryption on the OpenPrinter().

 

We need is a permanent way for the Spooler services to function the way it had for decades or else when .1379 (or the final Dec cumulative) rolls out we will be force to roll the 3 files back again or shut down MS updates all together.