MSFS 2020 CTD after todays AIRAC update

User Support Hub Crashes (CTDs)
,
1

Started MSFS 2020 today and it wanted to update the AIRAC date. Once completed the sim started without issue and went to game menu. While sitting in the menu is CTD. Afterwards I’m unable to get the sim to go into the menu. Sim is running in DirectX 12 mode.

I’ve renamed the Community folder and attempted to start 2020 but have the same results. The sim was running just fine yesterday.

MSFS 2024 starts and runs without issue.

I’ve also ran the following DISM commands with success.

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTARTED computer as the last step.

2

I have the same results when attempting to start the sim from within the XBOX app as well. Sim will CTD when at the screen where sim checks for update.

Windows event log shows after each CTD the following:

Log Name: Application
Source: Windows Error Reporting
Date: 11/28/2025 4:48:49 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: DESKTOP-AFGL0LD\usnao
Computer: DESKTOP-AFGL0LD
Description:
Fault bucket 1258236763487827865, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.39.9.0
P4: 00000000
P5: ntdll.dll
P6: 10.0.26100.7019
P7: 9c8f8241
P8: c0000005
P9: 000000000000aa83
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.53ac2a7c-128d-4798-acbf-284e3a13003e.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.13b735a1-e93f-4c4d-9c6c-7d575e3cefad.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20251126_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7249725c-eb40-4873-89c1-d4656b3c7c6d.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9b1ce1a3-1d0b-471c-883a-dc8ff8afe71f.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a67a1b64-4a06-419c-a9a5-b4519eed049e.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bfd1a2ce-4fca-494f-892c-49c852dfd267.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d0bc3cbf-7bf7-47ec-b5c0-0a9dea9bd2b8.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_255b8f4bfdd1d2851306f4d7ac942fe7f38d59_586ca05b_f7d5adb3-099f-47ec-9ecd-d4e93a143ad2

Analysis symbol:
Rechecking for solution: 0
Report Id: 1a26c906-c89b-4fa2-bf21-97cda8bdbd17
Report Status: 2147487744
Hashed bucket: 69990366a4b109dec17627ab83077799
Cab Guid: 0
Event Xml:

1001
0
4
0
0
0x8000000000000000

87200

Application
DESKTOP-AFGL0LD

1258236763487827865
5
MoAppCrash
Not available
0
Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
praid:App
1.39.9.0
00000000
ntdll.dll
10.0.26100.7019
9c8f8241
c0000005
000000000000aa83

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.53ac2a7c-128d-4798-acbf-284e3a13003e.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.13b735a1-e93f-4c4d-9c6c-7d575e3cefad.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20251126_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7249725c-eb40-4873-89c1-d4656b3c7c6d.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9b1ce1a3-1d0b-471c-883a-dc8ff8afe71f.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a67a1b64-4a06-419c-a9a5-b4519eed049e.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bfd1a2ce-4fca-494f-892c-49c852dfd267.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d0bc3cbf-7bf7-47ec-b5c0-0a9dea9bd2b8.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_255b8f4bfdd1d2851306f4d7ac942fe7f38d59_586ca05b_f7d5adb3-099f-47ec-9ecd-d4e93a143ad2

0
1a26c906-c89b-4fa2-bf21-97cda8bdbd17
2147487744
69990366a4b109dec17627ab83077799
0

Log Name: Application
Source: Application Error
Date: 11/28/2025 4:48:47 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: DESKTOP-AFGL0LD\usnao
Computer: DESKTOP-AFGL0LD
Description:
Faulting application name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.26100.7019, time stamp: 0x9c8f8241
Exception code: 0xc0000005
Fault offset: 0x000000000000aa83
Faulting process id: 0xA00
Faulting application start time: 0x1DC60C9C814E124
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 1a26c906-c89b-4fa2-bf21-97cda8bdbd17
Faulting package full name: Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:

1000
0
2
100
0
0x8000000000000000

87199

Application
DESKTOP-AFGL0LD

FlightSimulator.exe
1.39.9.0
00000000
ntdll.dll
10.0.26100.7019
9c8f8241
c0000005
000000000000aa83
0xa00
0x1dc60c9c814e124
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
1a26c906-c89b-4fa2-bf21-97cda8bdbd17
Microsoft.FlightSimulator_1.39.9.0_x64__8wekyb3d8bbwe
App

3

FYI:

There have been no changes to the sim other than the sim update that was pushed when I started earlier. Also all the DISM commands ran with success. This is with Windows 11 Home 25H2 26200.7171

4

Update:

Came home from work and fired up MSFS 2020 and whatta you know…it works. LOL!

Not sure what the issue was.

1 Like
5

After some thought I believe the issue was related to sync issue online. I have another system (my sons) who occasionally will sign into my account. I noticed on his system when signed into my account he had a 3rd party airport (KSEA) that was installed on his profile but did not disable the Asobo one it when signed into my profile. It was after disabling (signed into my account) the Asobo KSEA that I was able to get mine to not CTD.