Home » Technology » Microsoft » PrintNightmare Second Update Is On Its Way

PrintNightmare Second Update Is On Its Way


Things have not quieted down around the security vulnerability called “PrintNightmare” and the associated bug fixes from Microsoft. After experts initially criticized that the patch only worked half-heartedly, there are now problems with the printer and another update for users is on the way.

This emerges from various reports from those affected. According to this, some users are having problems with their printer after installing Microsoft’s Windows emergency patch. Printing attempts fail and it is unclear how common this error message is. Microsoft has now at least confirmed that the patch can cause problems. Problems with selected printers are now admitted. According to current knowledge, the printers in question are probably Zebra brand printers.

Zebra makes special printers for companies, for example for labeling shipping packages and the like. It is not yet known which other manufacturers are affected, but there are reports from affected Dymo users. Microsoft now comments on the problem in the Windows 10 documentation.

The Second Update Is On The Way

“We are aware of a printing issue caused by the July 6 Windows update KB5004945 that affects multiple printer brands. Microsoft has investigated this issue and plans to release an update in the next 1-2 business days to fix this issue. An immediate way to fix the issue is to uninstall Windows update KB5004945 or uninstall the affected printer driver and reinstall it with administrator privileges. In the long term, we recommend using the newer Windows update that Microsoft plans to release. Customers who need assistance with Zebra printers can contact our technical support. “

Uninstalling the Windows update KB5004945 is probably the worst possible solution, as the update fixes the PrintNightmare vulnerability.

The cited update is now on its way. According to Microsoft, the issue has been fixed with the Known Issue Rollback (KIR) update. You can now force this update by restarting the computer. Otherwise, the patch is in distribution and should be offered automatically in the next few hours, Microsoft writes.