Click on "Fly Now" locks MSFS up

All has been fine since installation. Bought MS (not Steam) version. Flew just fine yesterday. Have made no changes to computer or MSFS. Started up this morning and all looks normal until I reach the point of “Fly Now” and as soon as I click it, the blue bar comes on and immediately hangs. I must end task in task manager to get out of it. Tried challenges, training, all do the same thing. Did a “Repair”, tried to run as administrator, re-booted the computer, all to no avail. Everything else runs fine on the computer. Tried loading with different aircraft, turned off internet access, nothing makes a difference . . . any ideas? This is a new high-end system and MSFS has worked perfectly until now.

Nvidia control panel
Switch off multithread.
Adjust global settings to performance if that doesn’t work.Mine set in the middle ground.
How long do you leave it when it looks like it’s hung up?
Have you changed something since your last good flying session?eg any overclocking going on for example.Set defaults if you have any boosted GPU,ram or CPU.
Anything running in background in Windows that it suddenly doesn’t like? Disable anything except afterburner if you’ve a fan curve set,in taskmaster.
Unplug your controller in Windows and reconnect it once you’ve loaded up the SIM.
Any updates needed to install windows or store?
Temperature good with CPU/GPU?
Go into content manager and remove the aircraft you’re trying to fly and reinstall it.
General settings change one thing and save corrupted configuration should get re written.
Msfs ,if you don’t click fly can you exit normally?
Not seen it hang for more than a few seconds while it loads up to fly.
Lastly anything in the community folder, that’s gone out of date with the current build.
I really do hope Asobo get on with stability issues in the next update.
Hopefully someone with the issue has a solution.
Just a few things to try, you may not have already tried.For me the simulation doesn’t work as well since the latest patch.So for some of us, things have gone backwards.
Reinstall core in content manager if all else fails.

Do you have facetracknoir or equivalent installed? That’s one issue that will cause this.

https://forums.flightsimulator.com/t/game-crashes-after-clicking-fly/301717

Search for Services App in the Windows Search. Make sure all Xbox Services shown at the bottom are set to “Automatic”. There should be four of them.

All were set to “manual”, changed to “automatic” then re-booted. MSFS locked in exactly the same spot. Thanks for the suggestion!

**SUCCESS AT LAST!!! ** After trying almost all the suggestions given to me, I had a dream last night that a corrupt log file could cause this problem. Searched for “corrupt log file” and saw posts that said FSX would lock up immediately after the splash screen if it couldn’t access the log file. Searched for how to edit the log file in MSFS and saw a post that said “Developer Mode” doesn’t use the log file. I did see what I thought was an anomaly in my log file for the last flight I made. It showed the proper departure and arrival airports, flight time of 01:19:08, but showed zero take-offs and landings. So, this morning I fired up the computer, loaded MSFS, set it to “Developer Mode”, set up a flight, crossed my fingers and hit “Fly” . . . BINGO!! Loaded just like normal, I took a short flight, landed and looked at my log file, the flight was not there. Shut down the computer, re-started it, loaded MSFS, set it back to normal mode, set up a flight – perfect! Have made two more flights in different aircraft and different parts of the world . . . all have worked perfectly! Thanks to all who gave their time to help me! I guess sometimes you just have to think outside the box!!!

It’s surprising the same problem occurs to so many individuals with so different and apparent “solutions”. I’m a Steam user and I frequently have those blue bar lockups after the welcome screen. What I found useful in my case is to kill MSFS through the Task Manager after the sim gets locked-up (in the TM shows MSFS process as “Not responding”), to log-off from Steam and log-in again on Steam and firing up the sim one more time. It’s annoying and certainly Asobo/MS should be placing close attention to it. Hopefully one day…