Has cured the problem for me consistently for two weeks running now. Ironically, the very tool that might actually pinpoint what is hanging at the file system or registry entry level, seems to serve as a consistent workaround by prohibiting whatever race condition or other error or timeout is occuring. The only thing that has worked for me to consistently avoid these hangs is to run Microsoft's Process Monitor tool right before loading a flight. This known problem *may* be resolved in upcoming SU6 update although it is not explicitly listed in the SU6 Beta change log. Healthier option for your system is likely to cancel the task via task manager as opposed to waiting for extensive periods to no avail while GPU heat rises. Waiting for the hang to recover has never worked for me - have waited up to 30 minutes but task manager still showed FlightSimulator.exe as 'Not Responding' while GPU fan was blowing full tilt (since MSFS does not seem to cap frame rates until flight has started).

Its not rolling or manual cache files - resetting or deleting will cure for a few flights then problem returns.ĭoes not seem to be related to disk performance, fragmentation or access speed problems - occurs on my healthy system with MSFS installed on a 1TB SSD drive that is less than 50% full. Its not conflicting BGL files in add on scenery - used the tools in Add on Linker to find and rename duplicate BGL file entries and problem persists. can be replicated with an empty community folder. Its not incompatible add on scenery - can easily happen with stock airports etc. Known bug per posts in other thread that is linked above.

Procmon64 exe