For my part, this annoying problem began nearly one year ago, same modus operandi as reported. It seems to be linked to the plane I used for this session, I noticed that it happens frequently with the BS TBM 850 or some jet fighters lurching in my hangar.
It’s the same kind of bug than the inability to return to the main menu leading to CTD after some flights, one out of ten.
My version is the DVD release of MSFS 2020, my rig is an old 2017 PC with an I7 7700 Kaby Lake CPU and an outdated RTX 2070.
When MSFS doesn’t shutdown properly, the VRAM usage is stuck at 45% until the moment when I terminate the process using the task manager, thus returning to 5% as normal.
Until this thread was posted, I really thought I was the only one to meet this bug so I didn’t mind calling for help urbi et orbi.
Well, finally, there’s probably something behind this!
Me too, cannot shut down fully since saturday, DVD version, and empty community folder.
I think you might be onto something there 
The only time I had this shutdown problem was when I had bought a new aircraft. Since then I’ve flown different aircraft and then gone back to the new one MS2020 has shut down properly.
Edit. My community folder was full too!
Count me in too
I hardly fly in MSFS 2020 these days but I remeber that, when I had problems having the sim shutdown properly, it was due to another third-party add-on that was preventing it from closing. FSRealistic was an example, sometimes I had to shut it down and then MSFS 2020 would close down as well.
Interesting! Mine started today, doing the same thing. MSFS icon stays in the task bar, ‘running’ in the ‘background’ using 21% CPU and 2+GB memory. Have to kill it manually everytime.
I am having the same issue. Tried clicking on repair which did not work then did a reset and still did not help. Problem started after the recent update.
Same here too…
Same here.
Ms Store, having to manually force close 2020. Started after the update on 4/17 for Navdata.
Seem to remember this happening once or twice before on Navdata update day.
Same issue for me…MS Store version have to force shut down from task manager
It’s a slight annoyance but better than not being able to start the sim!
I’m in the same boat since last 18/04… MS Store version!
Thank god I’ve found this thread! I’ve started suffering this problem too. Thought it was just my system playing up - have been needlessly messing with drivers and all sorts to try and fix it.
Running MS Store version, Win 11 Pro, i7-13850 HX, RTX 4090 Mobile, 64GB RAM.
Same here, two weeks, microsoft store, answer from support, my system account is corrupted, I must create an admin acount in W10 and reinstall with that account, if this work, I must have 2 admin account for live, one to all services, other only to play msfs2020.
To troubleshoot crashes, sometimes there is a direct cause and effect fix which makes things easy. In your case, there are NO crashes or errors related to MSFS. Something else on the PC itself is causing the problem. Creating a local profile and installing / launching MSFS from this account will help us rule out any profile corruption related causes. We can assist you in troubleshooting the causes of the crashes, but ultimately any suggestions that we make will need to carried out by you on your end of things.
@CasualClick Can you give my ticket number? if this help to fix the bug, contain logs and videos about the issue Request #249175
From a related thread, in case this is useful:
Same Same problem here, arrived after the last update, also because I have not put anything new and the sim I have to close it every time by force, regardless of the type of plane or scenario I used in the flight before ending the sim. A real nuisance!
This is happening to me too.
I had no idea that there was a monthly update to MSFS for the AIRAC cycle. If this is true then why would I want to subscribe to Simbrief? Also if it really does update the AIRAC cycle why then does the PMDG B738 FMC display that the airac is out of date?
have something to do with the last patch a few days ago? I just use control alt delete, but this should not be happening.