Site icon WinCert

Printing issues with cumulative update KB5005573

<p>After installing the cumulative update &lpar;KB5005573&rpar; on the print server many of our customers reported printing issues&period;<&sol;p>&NewLine;<p><img class&equals;"alignnone size-full wp-image-4371" src&equals;"https&colon;&sol;&sol;www&period;wincert&period;net&sol;wp-content&sol;uploads&sol;2021&sol;10&sol;update-list-printers&period;png" alt&equals;"" width&equals;"643" height&equals;"248" &sol;><&sol;p>&NewLine;<p>Upon further investigation&comma; we have noticed that many clients were receiving <em>Access Denied<&sol;em> error messages for the printer that was shared on the print server&period; Users may also receive credential prompts when trying to print or connect to the printer&period;<&sol;p>&NewLine;<p><img class&equals;"alignnone size-full wp-image-4372" src&equals;"https&colon;&sol;&sol;www&period;wincert&period;net&sol;wp-content&sol;uploads&sol;2021&sol;10&sol;printer-error&period;jpg" alt&equals;"" width&equals;"554" height&equals;"264" &sol;><&sol;p>&NewLine;<p>So&comma; in order to resolve this issue&comma; we had to uninstall the patch &lpar;<strong>KB5005573<&sol;strong>&rpar;&period; Along with the patch removal&comma; the printer had to be removed and added again on the client-side&comma; after which the clients were able to print normally again&period; As removing Cumulative Updates for Windows Server is not a very smart idea if you want to stay protected we had to find possible mitigation until the problem is resolved by Microsoft&period;<&sol;p>&NewLine;<p>To mitigate this issue we have to edit the registry on the print server&period;<&sol;p>&NewLine;<p>From the run prompt type Regedit and navigate to the following handle to the registry key&period;<&sol;p>&NewLine;<p><strong>HKEY&lowbar;LOCAL&lowbar;MACHINE&bsol;SYSTEM&bsol;CurrentControlSet&bsol;Control&bsol;Print<&sol;strong><&sol;p>&NewLine;<p>in the right pane <strong>right-click<&sol;strong> <strong>New<&sol;strong> and select <strong>DWORD &lpar;32-bit&rpar; Value<&sol;strong><&sol;p>&NewLine;<p>Create the following key&colon; <strong>RpcAuthnLevelPrivacyEnabled<&sol;strong><&sol;p>&NewLine;<p>Leave its <strong>value data<&sol;strong> set to <strong>0<&sol;strong>&period;<&sol;p>&NewLine;<p>Close the registry editor and from the <strong>services&period;msc<&sol;strong> snap-in <strong>restart the Print Spooler&period;<&sol;strong><&sol;p>&NewLine;<p>Hope this helps&excl;<&sol;p>&NewLine;<p>Microsoft has acknowledged this printing issue and confirmed that they are working on a resolution&period; The fix should become available later this month&period;<&sol;p>&NewLine;

Exit mobile version