Windows 11 suffered from an unfortunate bug back in November that caused certain games to have unstable framerates with the 22H2 update, as you probably know, but Microsoft has now fully fixed the issue (implemented in tests last month after finding the solution).
Apparently, everything went well with the test, because Beep computer (opens in a new tab) Said that a full fix is now being rolled out to all affected Windows 11 users. So anyone who was previously affected by Microsoft’s blocking of the 22H2 update (or protection as the software giant likes to call it) can install the upgrade.
Microsoft observe (opens in a new tab): “This issue was resolved in KB5020044 and security measures have been removed as of December 14, 2022. Note that if there are no other security measures affecting your device, it may take up to 48 hours to update to Windows 11 , providing 22H2 version.”
So while some may have to wait a few extra days for the 22H2 update to be delivered to their blocked PCs, by the time you read this, it should already be available — or installed if you check it out on Windows update.
Analytics: Full steam ahead with security tweaks and UI optimizations
Obviously, it’s good news that the full fix has been implemented without a hitch, and now the 22H2 update is being delivered to gamers affected by this critical bug (it also affected some apps, which we shouldn’t forget, though Microsoft never really clarified which ones).
Those folks can now benefit from the interface improvements that 22H2 brings, including in the latter case some important smoothing and changes to core elements of the UI. Not to mention some work on the security side, such as enhancing Microsoft Defender SmartScreen’s phishing protection.
From the reports we’ve seen on various online forums, there seem to be satisfied customers noticing that the fix does work for them as the stuttering no longer occurs after the 22H2 update, and these seem to be the majority (strange complaints still Open, though it’s possible that this is caused by other issues than this specific bug).
