More than a week ago, we told you that Windows 11 22H2, the latest update of Microsoft’s operating system, had an issue that affected gamers and that in an immediate response, until we know more, those in Redmond have decided to pause the deployment of the update, which will prevent users from this jump. Personally, this seemed like the most reasonable response to me, as it prevented the problem from spreading and affecting more users who didn’t know it existed and decided to update their operating system.

It wasn’t really a surprise (bug, I mean) that users actually started to discover it in September, at the same time as the update was released. What’s more, at the time NVIDIA was already pointing out the issue and blaming it on Redmond, but it wasn’t until mid-month that Microsoft acknowledged the issue and acted on it, stating the following: “Some Games and applications may perform less than expected or suffer from stuttering (momentary freezing or choppy image) on Windows 11 22H2″.

At that time, Microsoft also recommended updating game and application updates to their latest versions, considering the possibility that the problem was found in whole or in part in them, and not only in the operating system update. However, the fact that it simultaneously stopped the distribution of Windows 11 22H2 already pointed to the suspicion that something had happened in the bowels of the operating system to cause this problem.

And today we know, via an incident update, that Microsoft has reactivated the Windows 11 22H2 deployment after identifying the software with which this conflict occurs. So the Windows Setup Wizard will first check if any of the affected games or apps are installed on the system and if so, prevent the update. If not and the device is among those eligible for the update, it can be installed. Of course, the update may take up to 48 hours to be available for these users.

As we can read in the issue update, Microsoft confirms that the reason for this is that “LThe affected games and apps inadvertently enable non-consumer GPU performance tuning features“, which makes us think that developers who may have used such features during the development and testing of their software should disable them before packaging and distributing the final versions.

But it’s also true that these apps worked properly before Windows 11 22H2 arrived, so something must have changed in the operating system to have these effects now. However, and for affected users, Microsoft says it is working on a solution that will be released in a future update (no date at this time).