A new Windows 11 bug gives problems with some printers
Lately there doesn't seem to be much blood between Microsoft's operating system and printers working on the network: after the security update for Windows 10 which had a bug that prevented access to networked printers, a similar problem began to appear. even on Windows 11. This time it seems that the problem concerns the phase of installing printers on the network, when the procedure is performed by accessing the servers via HTTP connections, but the same problem would also appear to occur with installations performed via the Internet Printing Protocol (IPP) .
The best solution currently proposed by Microsoft, waiting for an update that fixes the automatic printer installation process, is to install the drivers of the printer used locally, by copying the driver package from a workstation. (business case) from which the printer can be used correctly. Since the bug appears to have affected both client and server versions of Windows, here is a complete list of the offending updates:
Client: Windows 10 21H1; Windows 10 20H2; Windows 10 2004; Windows 10 1909; Windows 10 1809; Windows 10 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11 21H2; Server: Windows Server 2022; Windows Server 20H2; Windows Server 2004; Windows Server 1909; Windows Server 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2; While Microsoft works on the next update which, among other things, aims to fix this bug related to the installation of printers, it has stated that it is possible, for all users who are still using previous versions of Windows (including Windows 10 and Windows Server 2022 ), install the “October Patch Tuesday” update to fix the problem temporarily.
Credit: Microsoft The only plausible explanation, as Microsoft says, is that this problem stems from an error in the construction of the data file that contains the printer's properties. As a result, all clients receiving this corrupt file will not bea> able to use it properly and will therefore apply the default print settings. This explains why servers using standard print settings were not affected by the problem, which appears to have occurred only in the case of custom print settings.
sportsgaming.win reports to you the excellent HUAWEI MateBook D15 currently in offer on Amazon!
The best solution currently proposed by Microsoft, waiting for an update that fixes the automatic printer installation process, is to install the drivers of the printer used locally, by copying the driver package from a workstation. (business case) from which the printer can be used correctly. Since the bug appears to have affected both client and server versions of Windows, here is a complete list of the offending updates:
Client: Windows 10 21H1; Windows 10 20H2; Windows 10 2004; Windows 10 1909; Windows 10 1809; Windows 10 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1; Windows 11 21H2; Server: Windows Server 2022; Windows Server 20H2; Windows Server 2004; Windows Server 1909; Windows Server 1809; Windows Server 2016; Windows Server 2012; Windows Server 2008 SP2; While Microsoft works on the next update which, among other things, aims to fix this bug related to the installation of printers, it has stated that it is possible, for all users who are still using previous versions of Windows (including Windows 10 and Windows Server 2022 ), install the “October Patch Tuesday” update to fix the problem temporarily.
Credit: Microsoft The only plausible explanation, as Microsoft says, is that this problem stems from an error in the construction of the data file that contains the printer's properties. As a result, all clients receiving this corrupt file will not bea> able to use it properly and will therefore apply the default print settings. This explains why servers using standard print settings were not affected by the problem, which appears to have occurred only in the case of custom print settings.
sportsgaming.win reports to you the excellent HUAWEI MateBook D15 currently in offer on Amazon!