Microsoft fixes printing gremlin, ends that block on Windows 11 upgrades
- Reference: 1666679352
- News link: https://www.theregister.co.uk/2022/10/25/microsoft_windows_22h2_printer/
- Source link:
A troubleshooting [1]fix will correct the printing gremlin on affected machines. And if that issue was blocking the installation of the 22H2 update for you, well, there's even better news.
"Once the issue with the installed printer is resolved, the safeguard should be removed and you should be able to upgrade to Windows 11, version 22H2," according to the update.
[2]
Some PC users who tried to make the Windows 11 22H2 jump found that doing so may have caused them to run into [3]connectivity issues with printers relying on the Universal Print Class or the IPP Class drivers. The result was that the printers would fall back to basic defaults, unable to use printer-specific capabilities.
[4]
[5]
In practice, this meant the printer would not offer color, two-sided, or duplex printing, and custom settings would go out the window along with the handling of anything with resolutions higher than 300dpi.
Microsoft put a compatibility hold on Windows devices using printers with those specific drivers – making them unable to upgrade to version 22H2 – and offered workarounds for those who didn't want to wait for the official fix.
[6]
Even with this troubleshooting update now available (it should automatically download and install) it will take up to 48 hours before the 22H2 upgrade to Windows 11 is offered, even assuming there are no other blockers. Redmond's engineers said restarting the system and checking for updates may speed up the process.
[7]More than 4 in 10 PCs still can't upgrade to Windows 11
[8]Microsoft debuts Windows 11 2022 Update – now with features added monthly
[9]Microsoft warns: Windows 11 update breaks provisioning
[10]Windows 11 22H2 is almost here. Is it ready for the enterprise?
To address the problem manually, you can remove and reinstall any printers that use the two specific drivers, forcing Windows to use the latest versions.
There have been [11]other issues , including Daylight Saving Time changes in Jordan.
Curiously, there are also reliability issues with SSL/TLS handshakes when establishing secure connections, and with signing in with Windows Hello, which may not work as expected after upgrading to Windows 11 22H2. Microsoft issued a workaround – essentially saying users could sign in with passwords instead of using face or fingerprint recognition or a PIN – and earlier this month resolved the issue.
Microsoft is still investigating issues using provisioning packages with the latest update – the company suggests provisioning the Windows device before updates to version 22H2 to prevent the problem until an update is included in the next release. There's also a compatibility issue between Windows 11 and certain versions of drivers for Intel Smart Sound Technology (SST) that could result in a blue screen. ®
Get our [12]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2#2913msgdesc
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Y1ezu3AtmJakImTAokPRuwAAABQ&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://www.theregister.com/2022/10/06/windows_11_22h2/
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y1ezu3AtmJakImTAokPRuwAAABQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y1ezu3AtmJakImTAokPRuwAAABQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y1ezu3AtmJakImTAokPRuwAAABQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://www.theregister.com/2022/10/10/windows_11_adoption/
[8] https://www.theregister.com/2022/09/21/windows_11_2022_h2/
[9] https://www.theregister.com/2022/10/06/windows_11_22h2/
[10] https://www.theregister.com/2022/06/23/windows_11_22h2_is_almost/
[11] https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2
[12] https://whitepapers.theregister.com/
Re: Bet ya can't wait to slap that Windows 11 on your machine
I've actively avoided Windows on my home machines since 8 came out. The fact they've completely trashed the UI from 7 onwards and then royally fucked up both networking and printing in 10 shows MS lost the plot years ago. And I will never be convinced 11 is even an upgrade.
Re: Bet ya can't wait to slap that Windows 11 on your machine
Bet ya can't wait to slap that Windows 11 on your machine. I'm sticking with Windows 10
I'm sticking with not using Windows at all, or anything else made by Microsoft. Given all the problems I have avoided over the 15 years or so since I decided this, it has emerged as one of the smarted decisions I've ever made.
It's got breaking bugs in it
But because the numbers affected are low enough, they ship it anyway. The actions of a monopoly.
Re: It's got breaking bugs in it
I'm not sure it's entirely because of Microsoft being a monopoly, but it is allowing them to get away with it easier. Many other software providers acted like asses, and still do, but aren't monopolies.
Microsoft, in particular, are showing just how stupid it is to be run by a nefarious pairing of marketdroids and accountants.
Re: It's got breaking bugs in it
Boggles my mind on how anyone can downvote you for telling the absolute truth (unless they did it by mistake lol).
CPU usage incorrectly reported under Windows 11 2H22
As Missing Semicolon posted above, it's got breaking bugs in it.
One of those is that total and per-process CPU usage are incorrectly reported, even within the new Windows Task Manager itself (all the CPU usage values reported in the Details tab of Task Manager are incorrect). Total CPU usage not based on the Processor Utility counters is broken too, and this bug also affects 3rd party applications.
It seems these days you can count on Microsoft to not even bother to test their own stuff. Wonder how long it will take for this to be fixed (or even if it will be fixed, given how Windows Insiders had already been reporting this issue long before 2H22 official release).
As a developer I just feel completely dismayed at how bad things have gotten inside Microsoft for them to reach this point of "don't care" on what is essentially a monopolistic OS to the general population.
Bet ya can't wait to slap that Windows 11 on your machine
Bet ya can't wait to slap that Windows 11 on your machine. I'm sticking with Windows 10 thank you if only to stop the One Drive bloody takeover!