If MSFS24 freezes on exit, this might be the solution for you!

Hey folks,

I don’t post much, but after fighting with the freeze on exit issue in MSFS 2024 — even after several clean installs (full NVMe format, fresh ISO boot install) — and spending weeks searching for a fix with zero results, I finally found something that worked for me. Hopefully it helps someone else too.

For context: I never had this problem before. But after a hardware failure forced me to rebuild my system from scratch, MSFS 2024 started freezing every single time I tried to quit.
Like many others, I first suspected a bad addon, but in my case MSFS 2024 was freezing with absolutely no addons installed, right after a clean install, and with no external peripherals connected (no pedals, no VR, no dual‑monitor setup — just keyboard + mouse).

I reinstalled Windows about eight times using a clean ISO + MSFS 2024 with no addons…
Nothing helped. Except one thing: switching Windows to a local account.

And suddenly: Eureka — no more freeze.
Startup time even dropped from 32s to 25s.
MSFS closed cleanly every time, no task hang, no deadlock — even after reinstalling VR, TDS, FSUIPC, SayIntentions, PMDG 737, Fenix A320, FSIPanel, Navigraph, SimInnovation, etc.

Once my full MSFS setup was done, I switched back to a Microsoft‑connected account…
and MSFS kept working perfectly.

So if you’re stuck with the freeze‑on‑exit bug, give this trick a try — it might save you a lot of headaches.

I ALWAYS use a local account at home. The only time I haven’t is at work where a network account is required. Just curious why you weren’t using a local account from the start?

the perfect example of the kind of reply that makes people not want to post anymore to help out.

it all depends on your workload and how the machine is used. A connected account unlocks features that a local account simply can’t provide — especially in environments that rely on Active Directory or similar identity services.

Especially since after a first launch on a local account and then switching back to a connected account, the issue disappears — which pretty much shows that MSFS 24 is still built the old‑school way, especially now that Windows 11 26H1 is rolling out.

Smart alec remarks like yours is a better reason.

If you see my last sentence you might realize it was a honest question. I also stated that the only time I use a networked account was on a work computer. I doubt he has MSFS on domain computer in a work environment running AD and requiring a secured logon. If he was I would wonder why. I was truly curious why he wouldn’t have a local account.

I purposely bypassed the requirement when installing windows and MSFS (which he did 8 times) and if he didn’t need the Microsoft connected account would have suggested the process to bypass the requirement for it when installing Windows 11.

Curious why you commented on my response as I couldn’t find your helpful suggestion.

Not looking to contribute to any arguments here, but I’ve always used a local account with Windows 11 and I’ve had this issue lately intermittently lately.

Hey folks,

I don’t post much, but after fighting with the freeze on exit issue in MSFS 2024 — even after several clean installs (full NVMe format, fresh ISO boot install) — and spending weeks searching for a fix with zero results, I finally found something that worked for me. Hopefully it helps someone else too.

For context: I never had this problem before. But after a hardware failure forced me to rebuild my system from scratch, MSFS 2024 started freezing every single time I tried to quit.
Like many others, I first suspected a bad addon, but in my case MSFS 2024 was freezing with absolutely no addons installed, right after a clean install, and with no external peripherals connected (no pedals, no VR, no dual‑monitor setup — just keyboard + mouse).

I reinstalled Windows about eight times using a clean ISO + MSFS 2024 with no addons…
Nothing helped. Except one thing: switching Windows to a local account.

And suddenly: Eureka — no more freeze.
Startup time even dropped from 32s to 25s.
MSFS closed cleanly every time, no task hang, no deadlock — even after reinstalling VR, TDS, FSUIPC, SayIntentions, PMDG 737, Fenix A320, FSIPanel, Navigraph, SimInnovation, etc.

Once my full MSFS setup was done, I switched back to a Microsoft‑connected account…
and MSFS kept working perfectly.

So if you’re stuck with the freeze‑on‑exit bug, give this trick a try — it might save you a lot of headaches.

That’s where you’re mistaken. I’m running it in a multi‑server environment (4 servers total) with an AD, and I really don’t want to switch the affected machine(s) to a local account every time I install something or run into an issue, then reconnect it to the AD afterward. Since FS2024 came out, I’ve never installed it under a local account, and I’ve never had any problems. Same story when reinstalling MSFS24 betas.

I stand corrected. I run a network at home also but my MSFS computers are not a member of the domain and are on a separate VLAN that is not a member of the domain. Again I assumed (my bad) that most MSFS installs are not going to be on a domain.

My sincere apologies.

No worries, and my apologies as welI reread your message properly and realized I had misunderstood it and reacted too fast. I’m running everything on a domain environment and the machines have to stay joined to it. I also operate several 6-DOF flight simulators and have reinstalled MSFS countless times on domain-joined systems without ever seeing this issue - not with MSFS 2020, 2024, X-Plane, P3D, or anything else, even going back to the early versions. I genuinely thought I could help, especially since it seemed to be a recurring issue for others. Wishing you smooth virtual flights.