About 9/10 when I attempt to start the sim, I get a crash at the launcher (activity monitor suggests this is gamingservicesui.exe), before the Microsoft Studios / Asobo logos show. On the task bar, the icon that shows when the crash occurs in the white tone background, as opposed to the blue color background which eventually shows when the app successfully starts.
This occurs even when community folder is empty.
If I keep trying, the sim eventually launches, but the success rate is < 10%, which is super frustrating. I think this issue started after sim update 11.
@HammerAce42 :
Well, in my experience, when other apps (i.e. NOT FS2020) on my PC have crashed with:
I’ve found that it is mostly triggered by system issues that prevent Windows from accessing the apps files and settings required for launching the app. These range from lack of the right permissions, missing files and/or folders, corrupted files and / or folders, etc.
Rolling cache is disabled, so it’s not that. Also tried restoring sim to vanilla state without luck.
I recently built a new PC for MSFS and this issue did not occur for a few days on the new PC. Today, it is back even on the new machine. To be clear, the crash happens when the launcher window with the Bora Bora back drop says “Launching game”.
The only thing that I can think of that has changed is that I tried loading the game on a 3rd PC that I very rarely use, and that PC always gives me a profile load error and forces me to play offline. I wonder if that PC corrupts my cloud profile somehow and causes other machines to no longer be able to reliably launch MSFS.
Having to try to launch the game 10 - 15 times to get it to load is super frustrating, especially since I just built a brand new PC specifically for it.
Download a utility from Microsoft called RAMMAP. It will show you allocated RAM. I found that once I cleared items in standby RAM, the CTD on startup resolved for me. Also a full reboot will do the same thing.
A full reboot was not fixing this for me, but I went through and disabled services one by one, and it appears MotionSystems AppWatcher64, which is associated with Next Level Racing’s Platform Manager for their Motion platform was responsible for this issue. I’ll contact their support to see how to get this fixed. Appreciate the responses!
