Microsoft’s recent record with printers isn’t the best and now seems to be extending to Windows 11. The updates, which are expected to be hassle-free, have brought new situations that aren’t always easy to fix.
This scenario exists again and again and again printer problems have returned. For Windows 11, this is the first event, but in the remaining versions it is again unfortunately normal and no one wants it.
Just a few days ago, Microsoft released another set of updates. It was the first release of the new Windows 11, but it did not come without problems. What was described shows that everyone who tries to install new printers via HTTP does not succeed.
- Windows 11: 21H2;
- Windows 10: 21H1, 20H2, 2004, 1909, 1809, 1607, Enterprise 2015 LTSB;
- Windows 8.1 operating system;
- Windows 7 SP1;
- Windows Server: 2022, 20H2, 2004, 1909, 1809, 2016, 2012, 2008 SP2.
The versions of Windows listed above have this problem and cannot install printers. The recommendation in this case is to put the files on the local disk and install them in this way.
In addition to the error described above, the update of Windows 11 and other versions has another specific situation. It's also on printers, but this time on Internet Printing Protocol (IPP), which companies use to share these devices.
- Windows 11: 21H2;
- Windows 10: 21H1, 20H2, 2004, 1809, 1909;
- Windows Server: 20H2, 2004, 1809, 2022, 1909.
In this case, the problem affects fewer versions of Windows, but again Windows 11 new and recent versions are affected. In this case too, there is a solution, but it eliminates the notion of sharing. Again, the files must be copied to the disk and the installation completed locally.
The positive in these two cases is that Microsoft has already recognized the situation and will actually work to resolve it. Soon, without a scheduled or even announced date, Windows 11 and the remaining versions will receive an update to correct the problem.
This situation is certainly recognized by many, who have recently seen their systems stop printing. At the time, Windows 10 was affected, but this time Windows 11 was also a victim of this problem.
