Okay not sure what happened here but after a update to MSFS today, It is not starting for me. It keeps on crashing on start-up. On start up I am getting small icon which when I click ok - The sim crashes. I think it is something to do with fsuipc, because initial sim load is fine - when it gets to loading fsuipc that is when I get that icon.
I tried starting sim in safe mode and there was no problem there so it is definitely something to do with fsuipc or GSX perhaps.
This is exactly the reason why I hate MS/Asobo’s mandatory update policy - they change something in background and my sim refuses to start.
Apparently I removed fsuipc then tried again, still getting same pop up and crash so it is not fsuipc, something to do with msfs.
Removed everything from community folder and tried again - still same thing. graphics drivers are up to date.
Every thing was working fine last week, till I did that stupid mandatory update earlier this morning since then my sim is not starting.
Unbelievable!
Anyone else having similar issues?
1 Like
Looking into event viewer I get this:
Faulting application name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x65a6e79d
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process ID: 0x1e94
Faulting application start time: 0x01da68bfbc7839e1
Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 9b5fb778-823a-49be-a211-c57d7a75a1c0
Faulting package full name:
Faulting package-relative application ID:
Anything?
It is getting very frustrating now.
How about checking the integrity of that DLL? I’d try the usual Windows utilities:
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
It’s fairly easy to eliminate system file integrity as the issue.
Bill
Thanks - I found the culprit. out of date livery folder apparently. I had to go through my community folder addons 1 by 1.