A few weeks ago I noticed that if I closed down MSFS2020 then later tried to run it a window advised that it was already running - I had to use Task Manager to exit the task.

This morning when fired up MSFS2020 there was a mandatory update. Woohoo I thought, the closing problem has been addressed.

Sadly (on my PC) it has not and I still have to end the task with Task Manager should I dare to run MSFS after running in earlier and not shutting down my PC.

Does anyone else have this problem?

Could it be that Asobo are unaware of it or just want to concentrate on upgrades to 2024 and thus try to force 2020 user to fork out again?

 

That update was just the monthly Airac update. 

Looks like just a nav data update. I'm sure they are aware of the shutdown issue. It is hard to say if they will make any attempt to troubleshoot and fix it. I would imagine they are not at all happy about the number people staying with fs2020, so they may see such a bug as a positive thing.

I am Furious with these Devs, aborting all support for FS2020. And now, introducing a New issue, And leaving it there. 

Yes - I have the same problem - no matter how long I wait - so I just go to X box ap and start it from there

IMHO Asobo wants everyone to 'upgrade' to 2024 and so won't be in any hurry to fix anything. And why wouldn't they as they get income from those with 2020 who 'upgrade'.

Has Asobo advised of a date that they will stop releasing updates to 2020 (like Microsoft have with W10)?

Is 2024 relatively stable now (why would I fork out moola if there are existing 'issues'?).

It is done with SU2 update for MSFS2024 and i hope this "not support MSFS2020" is not the true so i assume for MSFS2020 it comes on a bit later..

cheers 😉

Yes - it’s been logged as a bug on the official forum for a while. It has 350 votes which is quite high as far as these things go. 

The link is here https://forums.flightsimulator.com/t/msfs-2020-will-not-shut-down-fully/717408/488

561 votes now…

Edited May 16, 20251 yr by AJZip2

7 hours ago, Bobsk8 said:

That update was just the monthly Airac update. 

Where is the Airac usable from within MSFS2020? I thought that the Airac cycle update was only for MSFS2024.

Sure they know about 2020 will not shut down fully, that goes to show what kind of company they are, that many votes on official MSFS website and they ignore it, hmmmm, shameful.

1 hour ago, Jarnie said:

Where is the Airac usable from within MSFS2020? I thought that the Airac cycle update was only for MSFS2024.

Where have you been the last 5 years? There has always been a monthly Airac Update. They were a bit behind and only since the release of 2024 they are on time with it and update it on the actual day the new cycle comes into effect.

6 hours ago, jaytee73 said:

Yes - I have the same problem - no matter how long I wait - so I just go to X box ap and start it from there

Did not work:

6 hours ago, Greazer said:

I am Furious with these Devs, aborting all support for FS2020. And now, introducing a New issue, And leaving it there. 

The problem with MSFS 2020 not fully shutting down on exit was not introduced by Asobo. It is a bug in the “Gaming Services” app that is produced by Microsoft itself. MSFS requires gaming services to run, but Asobo has no control over the programming of that app. They can report the problem to the XBox games division, and undoubtedly they have, but they can do nothing to fix it.

It would be like a refinery releasing a bad batch of gasoline that makes automobiles run poorly. You can’t demand that automakers “fix the problem” when the issue isn’t a problem in the car itself, and car manufacturers have no control over the gasoline supply.

It’s understandable that MSFS 2020 users would have initially assumed that the shutdown bug was caused by something that Asobo did, but it is quite clear now that the bug is caused by problem in the latest version of gaming services. Do you not read the official forums?

Speaking of which…

What do you mean “aborting all support for MSFS 2020”? It was just announced yesterday that beta testing for SU16 in MSFS 2020 will begin in just a few days. It has not been abandoned.

15 minutes ago, JRBarrett said:

The problem with MSFS 2020 not fully shutting down on exit was not introduced by Asobo. It is a bug in the “Gaming Services” app that is produced by Microsoft itself. MSFS requires gaming services to run, but Asobo has no control over the programming of that app. They can report the problem to the XBox games division, and undoubtedly they have, but they can do nothing to fix it.

 

Sorry, but all that I can find in the official forum is this:

 

 

Support (Microsoft Flight Simulator)

May 3, 2025, 20:50 GMT+2

Thank you for contacting Microsoft Flight Simulator Support today.

We are sorry to hear that you’re unable to close the Sim properly on your device. We understand how this can be inconvenient and how it can affect your gaming experience, so rest assured that we will look into it to find a resolution.

We have been trying to troubleshoot this issue on our end here at MSFS Support for the past 10+ days but have yet to find a solution for this “hang on exit” problem with MSFS. A bug report was created last week and has been sent to the QA and dev teams to see if they can determine a root cause of the matter.

This issue is logged into our internal bug tracker and is currently being investigated. We will contact you only if we require additional information. Unfortunately, there is not much that you can do on your end of things now as this will likely need to be addressed by the dev team. For now, I can just advise pressing CTRL+ALT+DEL to manually close out of MSFS and then to reboot the PC before launching it again. I do apologize for the inconvenience that this is causing you.

Perhaps I missed that announcement?    Anyhow, in IMHO, not good.