Last Tuesday, Microsoft launched the Patch Tuesday corresponding to the month of September . These patches are released on the second Tuesday of each month, and this one was released on September 14 afternoon. In recent days, many users have started complaining about problems, and one of them is, unfortunately, an old acquaintance.
Throughout this year we have experienced a real disaster in terms of problems with printers in Windows 10. The company had to release numerous patches to fix vulnerabilities, as well as broke compatibility at times. Now, the cumulative updates KB5005565 and KB5005566 are reviving ghosts from the past.
Failure in the latest Windows 10 patches
After installing the latest updates to the system, Windows 10 users claim that they are having problems with network-connected printers, be it a printer connected via WiFi or via Ethernet. Due to this bug, it is not possible to print documents , and the error is solved by reverting to the previous version. Therefore, the culprit of the failure is clearly the patch.
Interestingly, the operating system detects the printer perfectly, and even starts printing. The problem is that, although the printer starts the movements, nothing is printed. Other users claim that Explorer.exe hangs when they print a document.
The update released Tuesday contains fixes to vulnerabilities related to PrintNightmare ( CVE-2021-36958 ). This vulnerability was disclosed early in June by mistake, forcing Microsoft to patch it as quickly as possible, leading to bugs like this one.
PrintNightmare’s shadow is elongated
PrintNightmare is a remote code execution vulnerability that resides in the Windows 10 Print Queue . The Print Queue has been present in all versions of Windows for decades. Thus, any attacker could obtain administrator permissions and do whatever he wanted on the computer if we did not have it patched.
Therefore, it is even more sad to have to uninstall this latest patch that completely solved all the vulnerabilities related to this failure in case we want to be able to print again.
Some users claim that they are also having trouble installing the update via Windows Update , although there have not been as many complaints in this regard. Also, seeing the bugs that it introduces, it is almost better that the system does not insist on installing the update. We will have to wait at least until the end of the month so that Microsoft can launch something to solve this failure. In the event that it is released, that update will have to be installed manually by going to Windows Update. If not, we will have to wait until the second Tuesday in October (which falls on the 12th) for the monthly update to be downloaded and installed.
