Microsoft has started the forced rollout of Windows 11 22H2 to systems running Windows 11 21H2 that are approaching their end-of-support (EOS) date on October 10, 2023.
Redmond is regularly initiating automatic feature updates to ensure that it can continue to service these devices near their EOS date and to provide them with the latest updates, security updates, and improvements.
The automated feature update rollout phase comes after Windows 11 22H2 (known as the Windows 11 2022 update) has also become available for broad deployment today to users with eligible devices via Windows Update.
"Today we begin to automatically update consumer and non-managed business devices running Windows 11, version 21H2 Home and Pro editions to Windows 11, version 22H2," Microsoft said in an update to the health dashboard.
"Since Windows 10, we have been helping Windows users stay up to date and secure with supported versions of Windows through automatic updates. We are utilizing this same approach for Windows 11 to help you stay protected and productive."
The automatic updates will roll out gradually, starting with the devices running Windows 11 21H2 for the longest time.
"If you are interested in moving to Windows 11, version 22H2 right away, open Windows Update settings and select Check for updates. If your device is ready, you will see the option to Download and install," Microsoft added today.
One compatibility hold could block updates on some devices
"If we detect that your device might have an issue, such as compatibility, we might put a safeguard hold in place. In this case, the update will not be installed automatically until the issue is resolved."
Right now, the only compatibility hold blocking the Windows 11 2022 Update affects systems with specific driver versions for Intel Smart Sound Technology (Intel SST) on Intel 11th Gen Core processors that trigger blue screens of death (BSODs).
However, Microsoft provides a workaround for those who want to install Windows 11 22H2, requiring them to check if Intel has an updated driver for their systems.
The issue is resolved by updating the Intel SST drivers to version 10.30.00.5714 and later or 10.29.00.5714 and later.
After updating the affected Intel driver, it can take up to 48 hours before you can install the Windows 11 2022 Update on your system.
You can use this Windows support document or follow this guided walk-through to troubleshoot Windows 10 22H2 update problems or fix any errors you encounter.
Comments
Tikibobo68 - 1 year ago
Why am I being forced to buy à new computer just to have 11?
My system is running perfectly fine. Sounds like Microsoft is getting kickbacks on new computers.
NoneRain - 1 year ago
Bypass the requirements using Rufus, or:
https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-windows-11-tpm-check-bypass-for-unsupported-pcs/
https://www.bleepingcomputer.com/news/microsoft/how-to-bypass-the-windows-11-tpm-20-requirement/
xafase - 1 year ago
I wouldn't hold on to this as a long term solution. M$ will get around to closing that loophole.
A walled garden is more valuable to them then you having a functional PC.
SoftwareEngineer248 - 1 year ago
I don't think they care if people install Windows 11 on unsupported hardware. Microsoft typically tells people if they have problems on unsupported hardware, they are on their own.
xafase - 1 year ago
Why you are being forced to buy a new computer, is because the computer makers were mad that people weren't buying computers anymore.
That is all that sysreq is for. Forcing people to pay for new systems and new licenses of Windows.
stryqx - 1 year ago
I suspect we'll see more models added to the safeguard hold through this process as there's still too many devices with firmware and drivers not compatible with Memory Integrity being enabled, which is now the default in 22H2. What's worse is that a pre-upgrade check isn't done, so the outcome is either complete lockup on first boot of the 22H2 kernel, or a BSoD resulting in a boot loop. With a bit of luck someone on the Windows devteam will clue on and hopefully come up with a robust fix - most likely being to leave Memory Integrity to whatever setting the 21H2 environment was using.
ThomasMann - 1 year ago
Tikibobo68 No one is forcing you....
Win7 still works perfectly fine. As long as you dont do anything stupid, it will be perfectly safe.
And if you insist on working with an OS than obviously can be accessed against your will, well then you deserve what you get.... If you use the Rufus way described here to install 22H2, you also do not have to buy anything. I have the latest version of 11 on and old laptop install. It has an i7 of the THIRD generation as CPU...
SoftwareEngineer248 - 1 year ago
Windows 7 is not perfectly fine. A Windows 7 computer cannot be safely connected to a network because it does not receive security updates.
b1k3rdude - 1 year ago
Am I missing something here, why are some of talking about Rufus and using it to bypass Arbvitrary M$ b$ restrictions. Users on older machines that used rufus to get Win11 installed will NOT be getting 22H2, so the discussion is moot.
The issue is M$ are yet again, forcing an update on machines without user consent. Its why I am glad I have an enterprise licence (thank you previous manager) for my windows so if and when I choose to upgrade to 11 I wont have to deal with forced upgrades.
h_b_s - 1 year ago
You consented when you installed Windows 11 and agreed to its license. If you don't like it, stop using Windows.
ThomasMann - 1 year ago
b1k3rdude
That is simply not true, I have just installed two 22H2 from a rufus USB stick on two old computers. Do some research... and simply ignore the gangsters at M$