A little over a week ago we told you that Windows 11 22H2, the most recent update to Microsoft’s operating system, had a problem that was affecting players and that, in an immediate response until we found out more, those in Redmond had decided to pause the deployment of the update, thus preventing users from making this leap. Personally, it seemed to me the most sensible reaction, since it prevented the problem from spreading and affecting more users who were not aware of its existence and decided to update their operating system.
It was not really a surprise (I mean the bug), which actually started to be detected by users in September, coinciding with the release of the update. What’s more, at the time NVIDIA already pointed to this problem, blaming Redmond for it, but it wasn’t until the middle of this month that Microsoft admitted the problem and acted accordingly, stating the following: “Some Games and applications may experience lower performance than expected or suffer from stuttering (momentary freezes or image stutters) in Windows 11 22H2″.
At that time, Microsoft also recommended updating the games and applications update to their most recent versions, given the possibility that the problem was found, totally or partially, in them, and not only in the operating system update. However, the fact that in parallel it stopped the distribution of Windows 11 22H2 already pointed, at the time, to the suspicion that something had happened in the guts of the operating system, causing this problem.
And today we know, through an incident update, that Microsoft has reactivated the deployment of Windows 11 22H2, after having identified the software with which this conflict occurs. Thus, the Windows installation wizard will first check if any of the affected games or applications are installed on that system and, if so, it will prevent the update. If not, and if the device is among those eligible for the update, it can be installed. Of course, the update can take up to 48 hours to be available for these users.
As we can read in the update of the problem, Microsoft affirms that its reason for being is that “LAffected games and applications are inadvertently enabling GPU performance debugging features that are not intended for use by consumers“, which makes us think that developers who may have used such features during the development and testing of their software, should have disabled them before packaging and distributing the final versions.
However, it is also true that these applications worked correctly before Windows 11 22H2 arrived, so something must have changed in the operating system so that they now have these effects. However, and for affected users, Microsoft states that it is working on a solution that will be published in a future update (no date, at the moment).
