Crash on initial loading (Checking For Updates screen)

[weok]

Hi. 2 days ago my sim won't start anymore. It was already at Simupdate 5 and it was running Ok before. Now when i launch MSFS2020 it crashes at screen "Checking For Updates" (before main menu)

Tried reinstall and integrity check, updated OS and NVIDIA drivers - not working still.

[Sim_Pilot E]

I had the same problem until I uninstalled all non asobo dlc...waiting for next update to reinstall them

[fostex]

i have same problem, happend with update 5

[Stenleh44]

Me too haven’t found a fix. I think I’ll clean out my community folder and try again.

[weok]

Publicado originalmente por SimPilot_E:

I had the same problem until I uninstalled all non asobo dlc...waiting for next update to reinstall them

You mean you cleaned Community folder?

[Sim_Pilot E]

no, not the community folder...in the content manager in the full content page

[Sim_Pilot E]

sorry,, full catalog screen

[Boomer]

With the drivers, give DDU a go, i did multiple gpu driver 'clean' reinstalls and it was always crashing. Now granted, this is the first time ive ever had to use ddu, and ive been swapping nvidia cards since changing out my old 3dfx card for geforce.

For some reason, the launcher taxes the gpu hard, so it might look like its doing nothing but stuff is going on in the background. (like seriously, i play games that don't push my card as hard as the launcher does).

[HannesM]

Publicado originalmente por HannesM:

First - sorry for my english :)
i fly over 50 hours without any crash or other problems. Yesterday i start a flight and after 5 min. my first crash. The point - i don`t see there was a update for the new Gamrin and one Airport. After Update crash again!!!! i think the first crash kill some files in my windows 10!

The one and only that help:
1. Type "cmd" into the main search box.
2. click on "Run as Administrator" - than "yes
3. now you can see a dos-window
c:\Windows\system32>
type
sfc/scannow (that it looks)
c:\Windows\system32>sfc/scannow

ENTER

The scan will take a while; it should fix any corrupted files it finds.

Restart your Computer - for me now - no CRASHES

hope it helps for you too

this can help - maybe

[Judith]

i have same peoblem

[OneCovid]

Mircosoft is trash it crashed when on a loading but the screen is blank with a loading bottom right , i decide to refund .

[bigbadvuk]

Faulting application name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001cd6425
Faulting process id: 0x4828
Faulting application start time: 0x01d791ca73c0c328
Faulting application path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 72468cc9-03ba-43ad-b236-c0712b239e51
Faulting package full name:
Faulting package-relative application ID:

and again:
Faulting application name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001cd6425
Faulting process id: 0x4e4
Faulting application start time: 0x01d791caaeaec54c
Faulting application path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: f2f8e6f7-c2c9-4fcd-8fca-070fb1fb25b9
Faulting package full name:
Faulting package-relative application ID:

and next start:
Faulting application name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001cd6425
Faulting process id: 0x4654
Faulting application start time: 0x01d791cae9746222
Faulting application path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 2721eff4-8821-4059-9cac-e0722b61eadd
Faulting package full name:
Faulting package-relative application ID:

and then next one:
Faulting application name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.18.15.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001cd6425
Faulting process id: 0x30cc
Faulting application start time: 0x01d791cb251ee9e3
Faulting application path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: F:\games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: c0270309-51c8-4987-9ece-b20205a00083
Faulting package full name:
Faulting package-relative application ID:

VANILLA instalation, all drivers are up to date, all games ewxcept this crap run perfectly...So can Asebo please either roll this back to state before SU 5 or refund us all.. I dont give a flying ♥♥♥♥ about Xbox crap!!!!

[Ozzy OzBorn]

Did you do your initial install from Steam to your OS drive ? I've had endless problems until I found this tip on the web yesterday. When I hit "install" on Steam the first time I installed I chose my bigger SSD drive which my Windows 10 ISN'T installed on and it would crash as soon as I hit the FLY button. Well, I read yesterday that the initial install on Steam has to be on your OS drive. Then when you launch the game and MSFS itself comes up that is when you select your other drive. It actually works fine now after all this time.

[bigbadvuk]

Hmmm, ok.. Ill try to stay calm so that i dont trigger you
This is THE SAME installation which had worked for the previous year until Asobo deicided to screw up something in order to make it compatible with XboX!
(┛ಠ_ಠ)┛彡┻━┻

So all your ideas are not gonna work - i have zero intentions to even start fiddling with a sim which was working perfectly until the last update.

[SavageRhino]

For anyone it might help i had the same CTD yesterday mutiple times at the update screen.

I did a steam validate files check, & also deleted the content I had manually placed in the community folder in the past. After that the update screen was stable- it patched to the main menu then i updated again from content manager.

[ZombieHunter]

You don't have to delete the game or anything. Just make sure after every update there are no pending updates in your content manager. If you are having issues with a specific update in the manager then delete that on your drive and it will re-download the whole thing. I had this issue with the MB 339A. It kept getting in a bad update cycle so I just deleted the folder and let it re-download and now it works fine.

This exception: 0xc0000005 just means bad stuff happened within the program. It is the most generic exception in the event viewer. It can be caused by about a million different things.