Windows: The “PrintNightmare” is still a big problem

With Windows “PrintNightmare”, the name really says it all. The security vulnerability, which became known in the early summer of 2021, still exists in October. Even the security updates released on October 12 could not change this.

Windows can not close security hole

It is quite amazing how many problems Windows has with its so-called PrintNightmare. Under the waschechten nightmare of many Windows users vulnerabilities are summarized, which exist in the Windows printer spooler service. These gaps open the door for potential cyber criminals who are on the hunt for sensitive data. Since experience shows that the number of possible data leaks keeps increasing, it is therefore highly advisable to perform regular updates. Unfortunately, these bring with them noticeable problems.

The problems can take many forms and have been noticeable since July of this year. For example, after installing a security patch, individual functions of the printer or even the entire printing process suddenly no longer work. Unfortunately, the current security update from October 12 also brought such problems. Namely, it is the update “KB5006670”, which was rolled out for the server and desktop versions of Microsoft’s operating system.

Microsoft is not idle

At the same time, the software and hardware giant from Redmond can by no means be accused of remaining inactive and watching the problem grow. Quite the contrary. The U.S. company is working at full speed to combat old problems that arose in the course of previous security updates. As is often the case in life, the acceptance of a bug is the first step before fixing it. And here, too, the company is definitely showing some understanding. For example, Microsoft has confirmed that many printing problems occurred in the September update (KB5005565). In particular, printers with IPP could no longer be installed successfully when the update was installed. According to its own information, Microsoft is meanwhile working at full speed on a solution to the problem.

Another problem, which can be subsumed under the PrintNightmare, is the linchpin of the now released update. The print client no longer remembers the print settings of the last print process. As a result, the printer printed with default settings every time. The reason for this “forgetfulness” of the client was the September update. If you take a look at Microsoft’s update history, it all seems a bit confusing. Microsoft lists the problem in question under “Resolved” with the release of its October update. However, one day later it was already listed among the open issues again. Now, of course, the question is whether the October 12 update really fixed the bug or not.

Never ending Story

It really seems like a construction site is opening up for Microsoft here, and its scale is growing all the time. When one problem has been fixed, it feels like three new ones have sprung up elsewhere. This is not only evident with the “forgetful client” problem described above. Microsoft has similar dating problems in other places as well. For example, with the error that in the network environments of some users can no longer be printed on the servers. Instead of printing a desired document, Windows demands admin authorization to be able to install the printer driver first. For this problem, October 12 was also given as the “Resolved” date. On October 15, however, it is said to have been reopened.

Now, of course, the question arises again whether the problem is really history or has reappeared. As has now become known, some users have the described problem even after installing the latest security update KB5006670. This gives two possibilities for speculation. Either the problem persists despite the security update. Alternatively, it is also possible that a new security hole has simply opened up, the shape of which corresponds to the previous problem. The theory of a new site seems more likely, but not really more reassuring. After all, it makes it clear that this is obviously a real patchwork that Windows cannot get to grips with. By the way, Microsoft is supposed to roll out a solution to the newly surfaced problem before the end of October. We hope that Microsoft’s printer nightmare will finally come to an end.