The extremely buggy 24H2 update for Windows 11 may just be slightly less buggy now. According to Microsoft, the issue of Ubisoft games becoming unresponsive or crashing has been marked as "Resolved" as of January 17, 2025.
Microsoft claims that some Ubisoft titles are no longer affected by issues from the 24H2 update after Ubisoft released several updates for their impacted titles. Those titles that have received updates by Ubisoft include: Star Wars Outlaws, Avatar: Frontiers of Pandora, Assassin's Creed: Odyssey, Assassin's Creed: Origins, and Assassin's Creed: Valhalla.
However, just quickly glancing through some of the Steam discussions on some of these titles, the updates did little to nothing to fix the crashing on 24H2. In the case of Assassin's Creed: Valhalla, the most recent update to the game may have actually made the crashing issue worse for players.
Given that there are still many reports of game crashes, I would continue to avoid this Windows 11 24H2 update for the foreseeable future. Even if these Ubisoft game issues were resolved, there is still a lengthy list of issues that Microsoft has still not fixed in 24H2. One of those issues being that some games using Easy Anti-Cheat will stop responding and show a blue screen of death. Given how many games use Easy Anti-Cheat, that's a risk I am not willing to take just yet.
Windows 11 24H2 also removes support for Windows Mixed Reality headsets. This is obviously something that impacts a small group but it is something to be aware of.
For some people, postponing the update to 24H2 may not be an option. Microsoft is apparently starting to force the 24H2 update on users as the gradual rollout phase is over. You can still attempt to avoid this update while still receiving regular security updates by using any of the methods described at the following sites:
I personally went for changing the Group Policy setting detailed in the first link. I have continued to receive the monthly security updates and patches without issue while staying on Windows 11 23H2. If you have the choice, change the Group Policy options first before you even consider touching the Registry.
