Thursday, August 20th 2026
Windows 11 August Update is Breaking Games, Microsoft Investigates
According to an updated Microsoft support document, the Windows 11 August update is causing problems with games, and the company has officially confirmed that an investigation is underway. The document states that games like ARC Raiders, MARVEL Tōkon: Fighting Souls, and The Finals are experiencing forced crashes, random freezing, errors, and unexpected device restarts due to the update. After receiving complaints from internal testing and gamers, gaming studios have started to acknowledge the issue and report that the Windows 11 August update is causing applications to crash. Microsoft has confirmed the problem and is actively investigating its cause.
Sources:
Microsoft, via Windows Latest
MicrosoftFollowing the release of Windows updates on August 11, 2026 (KB5121003) and later, Microsoft received reports of issues involving inability to run games as expected. This issue has been reported for a limited number of games, including ARC Raiders, MARVEL Tōkon: Fighting Souls, and The Finals... If you are experiencing this issue, or a similar issue, please use Feedback Hub to file a reportOfficial symptoms include:
- the game application becomes unresponsive
- the game application closes without notice
- the error "EXCEPTION_ACCESS_VIOLATION" is displayed
- the device restarting without warning

69 Comments on Windows 11 August Update is Breaking Games, Microsoft Investigates
Good!
The fun just never stops with MSWhy the fck are you even rolling forward to begin with?
I'm still rocking the 24H2 LTSC and its glorious. Nothing crashes, everything works, no CoPilot shite anywhere, just W11.
if you unpack the .msix surprise (since reclaiming ACLs to the Administrator group or SYSTEM breaks the M$ **i*show of a cosplayed distribution,
you need to copy it off-systemdrive and purge ACLs that M$ enforces by NTFS impossible permissions (TrustedInstaller, the impossible yet owning files identity)
If you think you need M$ Store anything think twice, every single free msix/appx package from there can be installed in a way when no M$ Store is involved,
Most importantly, do not use M$ winget, it enforces 2 services, meaning - it will crap out if you use BFE, but the Firewall service is disabled (since its a joke,
that basically makes sure M$ rules are constantly reapplied and M$ can sent data home, it's not a firewall - a firewall asks users before it does something, not
if a host has been poked and then asks (if its outside its invisible defaults) if it can establish a connection, its like sending a query to a server, get a response,
meaning M$ already knows your client is online, and then asks the User - listen Pal, the server is up, so can i now upload my telemetry cause you changed the rules?
LoL, that M$ privacy 101. Again, test every claim I leave here because people assume a lot without checking it for themselves.
Second mandatory service is Appx inventory check, that winget somehow requires - even if you delete the ms-store it assumes you want by default, meaning,
winget tries to fetch packages from ms-store first (which it controls) and if its not there it will search the 2nd distriubtion channel (that is still controls, but not like the store)
Wireshark gives you a total overview what is going where- with the caveat that TLS encryption is handled by M$ reinvention - because if M$ would use opensource
libraries for that- they wont control it, so you have the SChannel s**t*show that has no way for a User to actually decrypt the traffic and see what is send where, but...
there are workarounds- and, you learn about how the tcpip stack runs- anyways, im half way through some enlightment writeup but I also have a job, anyways, whoever
understands stuff I write here about, PM me and I give you all the tools you can see it for yourselves.
Winget is M$ response to re-gain control over emerging alternatives to packaging without Redmond getting any data, scoop solves it perfectly, can be set to not use
powershell, and does not send your drive inventory to Redmond for indexing. Configuring 10 and 11 (allthough 11 is just more complex turd of a candy, 10 is easier to
bend into submission then 11 can be- since every major release - as in major builds, 22000 26000 28000 upgrades- M$ does its best to regain control and f**ck users
over - not to mention that background services needs with descritption that make 0 sense (feed it to llm and ask it about what it means, the llm craps out lol) - your system
increasingly has more data recording endpoints then the previous release, the insanity is obvious- just look how many background services are there between initial 11
release and canary, or current stable - i dont follow their confusion game of release naming, but if i recall the 28xxx build is going to be the next stable (or is?)
Follow the build overview not on M$ domains but, for example: changewindows.org/timeline/pc - and stop defending a corporation that doesn't give a s**t about
you, but wants your dataThat is not really the case, gpu scheduling and variable refresh rate, has been backported to Windows 10, what feature do you need explicitly or rely on that is not in Windows 10 vs 11?
:)
I wait for the day when someone finally discovers the mystery nagging at me since decades: what is causing the "something went wrong" error
Regards,
Fred.
It's so ridicules already that any other Software Company would just disintegrate from the amount of incompetency weight it generates.At least they managed to be consistent in one thing