CTD even in Safe Mode

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons?

Yes

Brief description of the issue:

With no known issue, I get a notification, that MSFS was unexpectantly ended (can’t remember that) and it won’t start again. I get the choice of starting normally or in Safe Mode, but either way ends after about 80% of loading with no more information on the desktop. I have followed the advice of reinstalling a vanilla state, but it did not help.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Simply by starting MSFS

PC specs and peripheral set up:

Betriebsystemname Microsoft Windows 10 Pro
Version 10.0.17134 Build 17134

|Prozessor|Intel(R) Core™ i7-6700K CPU @ 4.00GHz, 4001 MHz, 4 Kern(e), 8 logische(r) Prozessor(en)||
16 GB RAM
|BIOS-Version/-Datum|American Megatrends Inc. F6, 14/03/2016||

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.31.22.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.31.22.0, Zeitstempel: 0x00000000
Ausnahmecode: 0x80000003
Fehleroffset: 0x0000000001e189d0
ID des fehlerhaften Prozesses: 0x3898
Startzeit der fehlerhaften Anwendung: 0x01d96876b3502f17
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 9d8c9d77-eb8d-4228-85e0-49bea367af89
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Build Version # when you first started experiencing this issue:


Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

[/wrap]

1 Like

Have you solved it? I have the same problem since the update

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.31.22.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.31.22.0, Zeitstempel: 0x00000000
Ausnahmecode: 0x80000003
Fehleroffset: 0x0000000001e189d0
ID des fehlerhaften Prozesses: 0x0x4C94
Startzeit der fehlerhaften Anwendung: 0x0x1D96BD1B6E259E4
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: f48629c7-c4d4-47d3-a3bc-f28b5744fe81
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Problem solved - by the most reliable method with Windows software: re-installation!

Hi,
Did you mean a re-installation of Windows or a re-installation of MSFS?

“Only” re-installation of MSFS. Took me almost a whole day, nevertheless, it worked.

Not for me. What can I be doing wrong!?

Please use #community-support:tech-support for assistance threads.

Also, marked the post by Topic Author as the solution.