The Windows 11 2022 Update that Microsoft started rolling out in September is in its teething phase, with warnings of unexpected restarts and half-completed out of box experiences for users when deploying on new devices.
Those applying provisioning packages (.PPKG files that are used to help configure new devices for use on an org's networks) during initial setup are most likely to be impacted, Microsoft admits.
Microsoft released Windows 11 2022 Update (version 22H2) to the first eligible devices on September 20. While the update brought a raft of fresh security features to Windows 11, it is not bug-free itself, and has already thrown up some significant printing issues.
If you're looking after Windows updates on your organization's systems and are already planning to run the big Windows 11 2022 Update on new devices you've ordered for the working-from-home crowd (or fresh PCs for the office if you've been dragged back to HQ), Redmond suggests you provision the Windows device before upgrading to 22H2, which apparently will prevent the issue.
This isn't a problem that will likely affect consumers at home, Microsoft said, and it won't be an issue for those in businesses or schools who use the vendor's simplified setup, Windows Autopilot.
Microsoft is still actively investigating an issue where a security update for Secure Boot (KB5012170) sent some PCs into BitLocker Recovery back in August.
Register readers previously warned that some OEM firmware won't allow the update to be installed. Microsoft has since confirmed that when some users apply KB5012170, it will fail to install, and the error code 0x800f0922 might appear.
Microsoft says the issue can be mitigated on some devices if you update the UEFI bios to the latest version before you try to install the update.
This doesn't only apply to devices running Windows 11 22H2 (it's shown up on several other platforms, including Windows 22H1, Windows 10, and some Windows Server platforms - there's a full list on the Microsoft KB here), but, along with provisioning, it's one of the issues under active investigation as the 22H2 rollout becomes available to more and more of the world's PCs.
Both the provisioning issue and the KB5012170 update problem are marked down as something Microsoft will sort out in an upcoming release.
Microsoft earlier this week stopped the 22H2 update for Windows 11 systems with the IPP Class Driver or the Universal Print Class Driver.
The issue causes installed printers to only allow default settings - meaning they are unable to use "printer specific features" including "color, two-sided/duplex printing, paper size... or resolutions higher than 300x300dpi." Microsoft slapped a "compatibility hold" on Windows devices using the relevant drivers, meaning if you've got either of those installed, you won't be offered Windows 11, 22H2 in order to "safeguard your upgrade experience" and keep being able to print in color.
Microsoft said on its health dashboard earlier this week that it was "entering a new phase" of the 22H2 rollout updates and was increasing its availability to "all who check for updates on eligible Windows devices." ®
In brief Plus: DeepMind beats humans at Stratego
Banishing memory safety bugs cuts critical vulnerabilities
Yep. The very same JPEG-XL that's just been axed from Chromium
As for Twitter, politicians need to grow thick skins and stop mistaking it for advertisement
Record keeping rules might need a tweak to ensure content is preserved
Intel's 'Ice Lake' and AMD's 'Milan' chips bump up speeds and feeds
RE:INVENT Amazon web arm investing in Microsoft's platform to help customers escape Windows