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, cumulative updates KB5005565 and KB5005566 they are reliving 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. Because of this failure, documents cannot be printed, and the error is fixed 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 it hangs when a document is printed.
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 vulnerability that allows run remote code, and 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 which 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 in this regard there have not been so many complaints. In addition, 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.