Microsoft.GamingServices version 35.112.24001.0 causes MSFS 2024 to crash on startup

User Support Hub Crashes (CTDs)
, ,
1

This may be related to the existing thread from July 2025 ( Updating Gaming Services in MS Store causes FS2024 to crash on Startup ), although I could not find other recent reports of this specific version causing issues. I am posting in case others are experiencing the same problem.

FREQUENCY OF ISSUE
Every time, as long as Gaming Services 35.112.24001.0 is installed.

REPRODUCTION STEPS

  1. Gaming Services 35.112.24001.0 installed via Microsoft Store (automatic update)
  2. Launch MSFS 2024
  3. Sim crashes during loading screen (~30-50 seconds after launch)

EVENT VIEWER - ERROR SEQUENCE
The following errors appear in sequence in Windows Event Viewer:

  1. AppModel-State (Event ID 4) — OpenState returns error -2147009196
  2. GamingServices.exe crashes — ucrtbase.dll, exception 0xC0000409 (stack corruption)
  3. FlightSimulator2024.exe crashes — ntdll.dll, exception 0xC0000005 (access violation)
  4. AppModel-State (Event ID 4) — QueryStateContainerItemInfo returns error -2147020584 (x23 occurrences)

GamingServices.exe version: 10.0.26100.7827
ucrtbase.dll version: 10.0.26100.8313
FlightSimulator2024.exe version: 1.6.34.0

WORKAROUNDS
Two workarounds confirmed working on my system, however the Microsoft Store
will automatically reinstall 35.112.24001.0 after some time, requiring the
workaround to be repeated. No reliable way to permanently block this update
has been found so far.

  1. Install via Xbox App:

    • Uninstall Gaming Services via Windows Settings → Apps
    • Open Xbox App → it installs version 34.111.20001.0 automatically
    • MSFS 2024 launches successfully

  2. Install via https://store.rg-adguard.net (Retail channel):

    • ProductId: 9MWPM2CQNLHN, channel: Retail
    • Version 35.112.23002.0 is available and works correctly

SYSTEM SPECS
GPU: NVIDIA RTX 5080 (Game Ready Driver 596.21)
OS: Windows 11 (build 26100)
MSFS version: 1.6.34.0 (Microsoft Store)
Gaming Services (broken): 35.112.24001.0
Gaming Services (working): 34.111.20001.0 / 35.112.23002.0

2

This is probably the cause of the 2047 error, and why some can’t start the sim.

3

@Zephwind

  1. Open Xbox Insider Hub app
  2. Previews > PC Gaming > Leave
  3. Restart PC
  4. Uninstall Gaming Services
  5. Uninstall Xbox app
  6. Restart PC
  7. Download and install Xbox app - restart PC
  8. Launch MSFS.

^^^^^^^^^^^^^^^
FYI, PC Gaming Preview forces the new version of Gaming Services and the Xbox app.

EDIT

That driver is pretty buggy. Me and a lot of other people rolled back to version 595.97.

4

I had the 2047 error all day Saturday on PC. Logged out of the xbox app, logged out of Windows Store, logged back in again on both. Miraculously on Sunday it started working again without the error.

5

Exactly the same issue it just came out of left field
No issues before

6

@TenPatrol Thanks for the detailed steps. Regarding the PC Gaming Preview theory: I initially checked Xbox Insider Hub and confirmed I was never enrolled in the PC Gaming Preview program. However, I just realized I am enrolled in the Windows Insider Program on the Release Preview channel. This likely explains why I received the 35.112.24001.0 update without being in the Xbox PC Gaming Preview — the Windows Insider Release Preview channel appears to push Gaming Services updates ahead of the standard Retail channel. So your theory holds, just through a different Insider path.

Regarding the 596.21 driver: in my case the driver was not the root cause. Once Gaming Services was downgraded, MSFS launched and ran without issues on 596.21.

@XR219 Interesting that your 2047 error resolved itself over the weekend — suggests there may also be a server-side component to this, not purely a local Gaming Services version issue.

7

Yeah, I forgot to mention that it also installs newer versions. Good thing you remembered.

image
image1643×646 45.7 KB

Anyway, Windows Insider Program and/or PC Gaming preview isn’t really suitable for gamers - now you know that :smiley:

8

It also happened to me during weekend.

I got nearly the same setup with you:

Win11 insider 26220, 5080 with 596.21, msfs2024 su4, xbox insider with gaming services updated to 35.112.24001.0 on weekend.

MSFS CTD every time when loading world data at around 90%.

Using windbg to check the mini dump:

SYMBOL_NAME: ntdll!RtlpxVirtualUnwind+5c

MODULE_NAME: ntdll

IMAGE_NAME: ntdll.dll

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_ntdll.dll!RtlpxVirtualUnwind

I found two workarounds:

  1. Roll back Gaming Services to the previous public release version, as you did.

  2. Update to the SU5 beta.

Since this is a Microsoft title, I suspect SU5 depends on newer Xbox Gaming Services APIs. However, because the official SU5 release has been delayed, the updated Gaming Services shipped ahead of it via the external beta channel is breaking compatibility with SU4.

Let’s see what will happen after SU5 public release.

9

I’ve no beta’s or insider updates etc. The PC hadn’t been on in 2 weeks so did the Windows updates and Store updates then restarted. Every time i launched FS24 I had the error. Tbh, i gave up after about an hour and left it until Sunday (UK time) and it just worked. Very strange.

10

Moved to User Support Hub since a solution has been marked.