I have never ever faced with CTD in MFS before, and MFS worked normally on my PC.
But 2 days ago I updated Win10 to 21H2 and MS Gaming services was updated too.
After that I got CTD in 20-30 seconds after each attempt to launch MFS, and I got CTD even in Safe Mode of MFS.
I cleared Community folder and uninstall all third-party software which may interreferences to MFS: FSRealistic, Simlink, Navigraph, etc.) - but I still wasn’t able to launch MFS without CTD (in Safe Mode too).
I uninstall MFS from PC and tried to install it again via MS Store and XBOX app. And after loading MFS to PC (about 1,5Gb) I got CTD in the same point during first MFS launch (see attached video).
I checked all apps in MS Store were up to date.
I did reset Microsoft Store cache.
I did reset Microsoft Store.
I deleted all temp files in Windows.
I restarted Gaming Service and tried to restart Microsoft Store Installer Service, but there wasn’t Microsoft Store Installer Service on my PC.
I did reset Microsoft Gaming Services.
And of course, I rebooted PC after each step.
But after all steps I still get CTD after installing MFS from XBOX app or MS Store during first launch of MFS (see video from the link below).
I have no ideas what I could do else to solve the problem. May be somebody has faced the same and fix it. Please, advise me your ideas.
Win10 21H2
Build 19044.1415
Windows Feature Experience Pack 120.2212.3920.0
Do you have an Nvidia graphics card? If so, the latest driver version (497.09) is known to cause issues with MSFS. For now, the suggestion would be to roll back to the previous driver version until a fix is released.
Welcome to the group. I have been for a complete week with the same issue. The only pending is to format the computer and see if it resolve the problem. Something that I will not do.
Having the same issue as Dmitry. I’ve tried everything he’s done, what you recommended and it still crashed to desktop just like in his video.
Reinstalled the game and it loaded up once and then back to the same issue, almost reinstalled Windows but decided to play other games instead until a resolution comes out.
I think I have the same problem not just in MSFS but other games as well (eg. Assassins Creed Odyssey).
Both of them I am now getting regular CTD’s in-game where I never did before and only thing I can put it down to is the Dec 14th update to 21H1 (which I am running) and presumably 21H2.
I’m not sure about Dmitry but I had rolled back the drivers and last night I did a clean install of the newest ones with some MSFS fixes and neither fixed the issue.
Good info, I had the same issue with the latest NVIDIA driver update. The one thing that stood out the most was in the NVDIA 3D settings for program settings there was no entry for Microsoft Flight Simulator. I had to go to NVIDIA web site to the previous version that worked fine prior to the NVIDA update.
I wished I read your post before spending so much time researching the problem before figuring it out.
Duh !!
I’m having CTD before the game even gets to the first splash screen. The game “launches” and terminates with no error message after a black screen and loading wheel for about 3-4 seconds. I tried everything on the basic and advanced troubleshooting checklists - fresh game reinstall, reinstall gaming services, visual c++ packages, etc… I’ve tried many combos of windows builds and recent nvidia drivers with absolutely no change to the CTD point. The game was working fine last week on the previous nvidia game ready driver and 21H1, which I reverted to thinking that would do the trick but no luck.
Yesterday I reinstalled Windows10 21H2 from USB-stick to clean PC (after format C drive) and tried install MFS to empty PC. But I got CTD at exactly the same point like in my video attached to my first post.
Therefore, the problem definitely not in NVidia drivers and not in conflict with third-party drivers.
The problem looks like MFS is not compatible with Windows10 21H2 or are some conflicts between MS Gaming Services, Xbox apps, etc.
I’m having the exact same problem on an AMD Ryzen 7 2900X, 64 GB, RTX 2080 Super.
Runs in ‘Safe Mode’, but crashes when selecting ‘Start Normally’.
My Community folder is empty, and the only additional content installed is from the Marketplace.
The same exact configuration runs flawlessly on an AMD Ryzen 9 3900X, 64GB, 3080 Ti.
I did the same as you with a clean Windows 10 install, Clean MSFS 2020 install, but still have CTD in same spot.
(Edit: Correction, the Ryzen 9 3080 rig is running 21H1)
I just verified that FS 2020 will run under 21H1, but not 21H2 on my Ryzen 7 rig.
I installed a fresh 21H1 image to the machine and ran 2020 for 2 solid hours with no issue.
Reformatted and installed a clean 21H2 image, 2020 would CTD shortly after the update screen, but run well in ‘Safe Mode’.
All machine & O.S. settings were identical on both instances.
Reverted back to 21H1 image until Microsoft get’s this resolved.
Just earler had 2 CTD in the menu/s with latest MSFS version. Made check of the apps within MS store and ‘Gaming services’ updated. No more CTDs after updating it and rebooting PC. This is under 21H2 19044.1526
Make sure that Windows is also current (above is latest version #)
Fortunately, I’ve could solve this problem and I would like to share the solution with you.
In my case the problem was in synchronization of joystick settings located in “wgs” folder (C:\Users****\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs) between MSFS and its cloud in Game services. As it shown in my video in the first message CTD happened just in the moment of synchronization game data with cloud.
For me the solution was in 3 steps:
Delete everything from “wgs” folder (C:\Users*\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs***)
After that launch MSFS in offline mode (it needs to avoid synchronization) and reconnect to Internet after pop-up message
After that MSFS starts normally and you need to configure joystick again via “control” menu and save these settings.
Restart MSFS in online mode and choose “local” when MSFS asks during synchronization: “keep the cloud or local profile”
After that no CTD.
Special thanks for Microsoft for spoil MSFS by their glitched Game services which unnecessary for most users.
… a good steam discussion thread for this: