[German]Microsoft has released a troubleshooter to fix printer issues last Friday (October 21, 2022). This troubleshooter helps against the compatibility issues with the drivers of certain printers on Windows 11 21H2 and 22H2 confirmed at the end of September 2022. This can result in the printers only being able to be used with default printing options. Microsoft has blocked the feature update to Windows 11 version 22H2 on the affected systems.
Upgrade stopper for printer drivers
I had reported in the blog post Windows 11 22H2: Issues and upgrade stoppers that Microsoft had set an upgrade blocker for certain Microsoft IPP Class Drivers – but details were still unknown. The official confirmation by Microsoft was made on the Windows Release Healt Status page of Windows 11 as of Sept. 29, 2022 – see also my post Windows 11: Printer driver confirmed as upgrade stopper (Sep 29, 2022). Microsoft's support document Some installed printers might only allow default settings states:
Microsoft has found an issue when an installed printer uses Microsoft IPP Class Driver or Universal Print Class Driver and is installed on a Windows device with connectivity issues to the printer.
Windows needs connectivity to the printer to identify all the features of the printer. Without connectivity, the printer is set up with default settings and in some scenarios might not get updated once connectivity to the printer is restored.
You might be affected by this issue if your printer is unable to use printer specific features such as color, two-sided/duplex printing, paper size or type settings, or resolutions higher than 300x300dpi. Currently, installed printers in this state will carry this issue forward when upgraded to Windows 11, version 22H2.
It has been confirmed that Microsoft has therefore set a compatibility block (upgrade blocker) for Windows devices with printers that use the Microsoft IPP Class Driver or the Universal Print Class Driver. The post has been updated by Microsoft as of October 7, 2022 in content to only block drivers that "currently only allow default settings". These devices will not be offered Windows 11 version 22H2 as a feature update. If Update Compliance is used in companies, the protection ID is 41332279.
"Troubleshooter" and workarounds
Microsoft is working on a solution and wants to roll it out with one of the upcoming updates, the company had announced. A manual workaround was available for affected users:
- If a printer that only allows default settings (or throws BlueScreens) has already been installed, removing and reinstalling the printer should fix this problem.
- To upgrade to Windows 11 version 22H2, users could remove any installed printers with Microsoft IPP Class Driver or Universal Print Class Driver.
In another addition to the support post Some installed printers might only allow default settings, Microsoft announced a troubleshooter for the problem by October 21, 2022. It states:
A troubleshooter has been released that will automatically download and fix this issue on affected devices running Windows 11, version 22H2. Once the issue with the installed printer is resolved,
Once all affected installed printers have been manually removed or the Troubleshooter has been run, compatible devices should be offered and able to upgrade to Windows 11 version 22H2 within 48 hours. If you restart the Windows system and check for updates, you may be offered the upgrade to version 22H2 sooner after taking measures such as uninstalling drivers. (via)
Windows 10 2022 Update (22H2) released (Oct. 18, 2022)
Prevent upgrade to Windows 11
Windows 11 22H2: (Moments 1) out-of-band update KB5019509 (October 18, 2022)
Lansweeper Windows 11 Readyness-Test: Almost 50% of systems still incompatible in October 2022
Windows 11 22H2: Windows Hello upgrade blocker will be lifted in mid-October 2022
Windows 11 22H2: Microsoft confirms performance issues when copying files
Windows 11: Microsoft helps to re-gain gaming performance
Windows 11 22H2: Microsoft investigates RDP issues
Windows 11 22H2: Provisioning packages may not work as expected
Cookies helps to fund this blog: Cookie settings