…or one of the base generic airports has some conflicting data?
Exactly the same here
Personal Comments and Observations
Ok - good news, at least from my view. I uninstalled Navigraph before ever running the sim today - in my case, Steam pushed a 99MB file out to the install path, then the MSFS Installer pushed a 600MB update (AAU3) out. I completed booting the sim, checked basic functionality, all OK. Shut down the sim, reinstalled the NG AIRAC, restarted the sim. Basic function check again including a flight, all is good
ah, so the sim does work after re-installing navigraph airac data?
no… for almost all
Not for me, tried a couple times.
Some folks that are in the Beta program have not yet received the update.
Those folks may be OK.
My sim updated, and launched without Navigraph. Re-installed Navigraph, and it crashed before the main menu.
Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000bf1e8e
Faulting process id: 0x0x2054
Faulting application start time: 0x0x1DB14298801E54D
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 68270811-f423-4ffd-9032-23f075838886
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
no, just remove the navigraph navdata folders
if it is an airport that has conflicting data, maybe those who it works for have a 3rd party addon for that airport?
if there’s a pot of straws, time for some clutching ![]()
Yes, if you don’t have or use Navigraph, there is no issue.
Yes, it’s working fine. I’m flying TommyMxrs JT-A as we speak.
I have confirmed after removing all the AIRAC through the Navigraph Hub MSFS2020 will start again.
Removing the items from the Community folder didn’t work for me. I did remove the Navigraph AIRAC with the Navigraph hub for each airplane and the sim launched.
Hi,
The vast majority of users can’t run the sim even after reinstalling Navigraph data. Can someone from the Forum Moderator team confirm if this has been raised internally with Microsoft or not? We are at loss at Navigraph here. Thousands of users uninstalling Navigraph navigation data is hardly a solution!
Kind regards,
Stephen
CTO
Navigraph
It’s been raised with CM team back to the Devs @Stephendoc9443.
As a mitigation to NG subscribers who haven’t installed AAU3 yet, it’s best to reiterate the advice NG has given over the years - temporarily REMOVE NG AIRAC before the AAU3 patch installs.
Do a function check. Shut the sim down, reinstall NG AIRAC, function check again.
It worked for me.
Is there a technical reason why this wouldn’t work for folks more generally by uninstalling Navigraph entirely and reinstalling it again? Some odd interaction with the update itself?
See post #35
Once I remove Navigraph CYCLE FROM COMMUNITY FOLDER it works great.
Reinstalling the cycle the sim will CRASH.
Version i have is 1.38.2.0 yes loads of stuff and updates I haven’t installed because either its an area I dont fly or not to intrested in.
Its not the update is appears to be Navigraph Cycle if you open SIMLINK you might see a RED entry against the date time .
I concur. Navigraph is the issue. Did you figure out a way to fix it?