CTD when connected to internet - Delete cloud data - this fixed it for me

I have tried the steps. I have tried clearing via PC and Xbox. I know the wipe worked because it asked for me to set up the options on next start. Still crashes.

Remember to start a flight

CTD after the launcher video of MSFS Steam version

Formatting, reinstalling the whole computer (Win 10 etc…) same problem: CTD after the launcher video and impossible to reinstall MSFS.

The failure was due to corrupted data on the Steam Cloud

The solution:
-Desinstall, Reinstall Steam

Steam Menu > Settings >Cloud >Uncheck Enable Steam Cloud Sync

-On the game > Properties>General> Uncheck Save saves… in the Steam Cloud

Loading the Launcher

Everything is ok

yep.. related to steam exist (e.g.) this topic about :

On steam the solution is easy…I had the same problem on store…and I became crazy to resolve it…

I Updated my FSim Today because im on Vacation and have some tme to spare. The Sim Crashes in the Menu, cant even Load a flight, so i decided to Reinstall the whole Game. Unfortunately then it crashed on Startup, directly after the Splash Screens. I fresh installed Windows, doesnt solve my Problem. Then i look at your Forum, try to delete my cloud save, but it didn´t help. So, now im locked out of one of the most expensive Games i have ever bought. Is there hope for a official Fix in near Future? I wanted to get warm for PMDGs 738, but cant use the Software in any manner because its crashing to Desktop without any error message.

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.22.2.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.22.2.0, Zeitstempel: 0x00000000
Ausnahmecode: 0x80000003
Fehleroffset: 0x00000000006ece01
ID des fehlerhaften Prozesses: 0x271c
Startzeit der fehlerhaften Anwendung: 0x01d8243704770c69
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 5fbb71da-97b7-4ea1-9883-90932a3533e0
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Its hard to think that one of the biggest Companies in the World isn´t capable of doing a “normal operation” Game. The whole Installation Process is a Pain, no matter how fast your network is, you cant just delete your cloud save, updates are over complicated, i just want to play my 130 Bucks Game and it just wont let me…

To fix this issue, you need to delete your cloud save on your PC.

This will delete your Microsoft Flight Simulator save data.

Please do the following:

  1. Open the Microsoft Store.
  2. Click on the Three Dots menu and then click Settings.
  3. Make sure your Offline Permissions is set to ON
  4. Start Microsoft Flight Simulator, once you’re on the main menu, quit the game
    5.(they told me in a second email to skip this step, because, obviously, I couldn’t get to the main menu)*
  5. Disconnect your PC from the internet
  6. Quit Microsoft Flight Simulator
  7. Copy and paste your LocalCache and LocalState folders on your Desktop (for example), located by default here:C:\Users\your_username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
    C:\Users\your_username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState
  8. Then head to your Windows 10 SettingsStorageApps & gamesMicrosoft Flight SimulatorAdvanced Options -->Select the Reset button.
  9. Once done, move the saved folders from your Desktop to C:\Users\your_username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\
  10. Launch Microsoft Flight Simulator
  11. Follow the onboarding and launch a flight
  12. Reconnect your PC to the internet
  13. Connect back to the internet.
  14. On connected in-game, quit Microsoft Flight Simulator
  15. Launch Microsoft Flight Simulator again
  • If you are prompted to pick a save, you need to pick “LOCAL” for this time only. Moving forward, you will want to pick “Cloud”

if you know that already, then you are may be in wrong topic here. In special 0x80000003 can point to other reasons too.

The game crashes when it re-connects at step 13 while in-flight, just like it crashes when it makes a connection on launch. I’ve been in contact with support who only repeat these steps at me, I sent them video proof of me following these steps and they replied 5-days later with the same copy+paste “follow these steps” email that they had sent twice before ;-;

These steps do not fix the issue for all of us and the official support team isn’t giving any personalised help.

The odd thing is on step 15 the local save is clearly newer then the cloud save, and after choosing it and letting the game crash, trying again several days later, the cloud save is dated to the new local save from the previous attempt.

Offline the game works fluently with no issue, the only persistent thing that leads to a crash is an internet connection. I’ve tried this game/account from three different networks and over three fresh/clean installs of windows 10/11 (Drive wiped and all), there is nowhere else to point blame but the handling of cloud saves.

I must start a flight without reconnection…when you relaunch the sim it ask the cloud

I figured out how to get a crash dump using Collecting User-Mode Dumps - Win32 apps | Microsoft Docs and analyzing it with windbg.exe clearly shows this is an issue in their code when trying to grab a String value from the GetUserData response.

GetUserData is a call to grab data from Microsoft servers that we as users dont have access to ( PlayFab/XPlatCppSdk · GitHub ). and Looking at the docs for that JSON library (Function asCString - Jsoncpp) and the associated code, looks like they’re trying to get a string when the value is not a string. JSON_ASSERT_MESSAGE(type() == stringValue, "in Json::Value::asCString(): requires stringValue");

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000007

STACK_TEXT:  
00000029`ecb7db30 00007ffc`8e501f9f     : 00000029`00000003 00000000`00000003 00000040`00001000 00000000`01000000 : ucrtbase!abort+0x4e
00000029`ecb7db60 00007ff6`d1e18bfa     : 00000000`176de000 00000000`176de000 00000000`00000000 00000000`ffffffff : ucrtbase!terminate+0x1f
00000029`ecb7db90 00007ffc`8e95b857     : 00000000`00000000 00007ff6`d1e18ba0 00000000`00000000 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0x171a10a
00000029`ecb7dbc0 00007ffc`90d751b0     : 00000029`ecb7de00 00007ffc`90e1662c 00000000`00000000 00000029`ecb7dd98 : KERNELBASE!UnhandledExceptionFilter+0x1e7
00000029`ecb7dce0 00007ffc`90d5c766     : 00007ffc`90e42a24 00007ffc`90cd0000 00000029`ecb7de00 00007ffc`90d00e7b : ntdll!RtlUserThreadStart$filt$0+0xa2
00000029`ecb7dd20 00007ffc`90d720cf     : 00000000`00000000 00000029`ecb7e300 00000029`ecb7f3a0 00000000`00000000 : ntdll!_C_specific_handler+0x96
00000029`ecb7dd90 00007ffc`90d21454     : 00000000`00000000 00000029`ecb7e300 00000029`ecb7f3a0 00000000`00000001 : ntdll!RtlpExecuteHandlerForException+0xf
00000029`ecb7ddc0 00007ffc`90d211a5     : 00000000`00000000 00000029`ecb7f240 00000000`00000000 00000029`ecb7e510 : ntdll!RtlDispatchException+0x244
00000029`ecb7e4d0 00007ffc`8e884f69     : 00000198`48df0000 00007ffc`6fbfa508 00000029`ecb7f4e0 00007ffc`71d77a85 : ntdll!RtlRaiseException+0x185
00000029`ecb7f380 00007ffc`724c64c0     : 00000000`0000003f 00007ffc`6fbf09b7 00000000`00000040 00007ffc`724d6280 : KERNELBASE!RaiseException+0x69
00000029`ecb7f460 00007ffc`6fbe0b02     : 00000029`ecb7f4e0 00000199`ea1f7eb4 00000198`53ca4028 00000000`00000000 : VCRUNTIME140!_CxxThrowException+0x90
00000029`ecb7f4c0 00007ffc`6fbe1a74     : 00000029`ecb7f550 00000198`53ca4028 00000029`00000000 00000198`53ca4028 : lib_json!Json::LogicError::LogicError+0x92
00000029`ecb7f530 00007ff6`d178edd1     : 00000198`53ca4028 00000198`53ca4028 00000000`00000000 00000000`00000001 : lib_json!Json::Value::asCString+0xa4
00000029`ecb7f680 00007ffb`f3c2e347     : 00000199`e999b960 00000198`53ca32a0 0000019a`05c2cfd0 00000000`ffffffff : FlightSimulator!FlightSimGetProcessId+0x10902e1
00000029`ecb7f800 00007ffb`f3de4f08     : 00000000`00000000 00000000`00000000 00000000`00000000 00510001`0000002f : XPlatCppWindows!PlayFab::PlayFabAdminInstanceAPI::GetUserData+0x400cf7
00000029`ecb7f920 00007ffb`f3de5f2a     : 00000199`d6241af0 00000000`00000001 0000019a`05c2cfd0 00000199`d6241b08 : XPlatCppWindows!PlayFab::PlayFabAdminInstanceAPI::GetUserData+0x5b78b8
00000029`ecb7fa50 00007ff6`d13703f8     : 00000000`0000000a 00000000`0000000a 00000000`00000000 00000000`00000011 : XPlatCppWindows!PlayFab::PlayFabAdminInstanceAPI::GetUserData+0x5b88da
00000029`ecb7fac0 00007ff6`d166764f     : 00000003`a6ad95ed 00000198`4c5310a0 00000000`00000000 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xc71908
00000029`ecb7fc40 00007ff6`d1666b5e     : 00000000`00000000 00007ff6`d3d254b0 00000000`00000001 00000000`00000007 : FlightSimulator!FlightSimGetProcessId+0xf68b5f
00000029`ecb7fc90 00007ff6`d0f5e495     : af358769`00009fe0 af358769`e4469aa8 00007ff6`d0f60130 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0xf6806e
00000029`ecb7fcc0 00007ff6`d1e18702     : 00000000`00000005 00000000`00000000 00000000`00000000 01d826fd`fc432913 : FlightSimulator!FlightSimGetProcessId+0x85f9a5
00000029`ecb7fd00 00007ffc`90967034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : FlightSimulator!FlightSimGetProcessId+0x1719c12
00000029`ecb7fd40 00007ffc`90d22651     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000029`ecb7fd70 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
2 Likes

I have the same problem can update the Microsoft store part but as soon as I try to load the sim CTD. Have to admit I gave up with it and went over to Steam where I have no problems. Just wasted money on the market store so won’t be buying anything through Microsoft again

Good news! they finally figured out the issue for me! my new ticket said they ran a script over the weekend that fixed the issue on affected profiles and will have the causing bug patched next sim update. So if anyone was in the same boat as me should try it again today. I was able to load the game and get in without issue this morning. I really hope they do something to better detect issues like this in the future!

2 Likes

Yes! It works again for me as well.

1 Like

Apparently with SU9 there is now the ability to delete the cloud profile.
I don’t have all the details.
However, reference as to what it may be doing can be found here:
https://forums.flightsimulator.com/t/caution-advised-with-clearing-cloud-saves/513814

Ok I have tried all of the steps. I got into the sim when I reset it. The only way was to not allow it to sync after I reset it. Once in the game I ran a flight set back up my control options saved them flew the flight and then closed the sim. When I started it back up it crashed again as soon as it tries to sync the data. Why can’t I get the new data to save and clear out the cloud version? What am I doing wrong?

I just want my cloud data cleared is there a way to do it now? The command prompt script that Microsoft has is nonsense and does nothing.

@Whombuz Have you tried the steps that Zendesk are recommending in this article?
https://flightsimulator.zendesk.com/hc/en-us/articles/4409228619538-All-versions-How-to-delete-your-cloud-save

If that is not working then I would suggest creating a ticket with zendesk requesting technical support from the drop down menu:

If you receive useful information that may benefit others then please do share the information here as well.

Smth is wrong with ms services, cloud etc so try again later.