2 minutes ago, vonmar said:

Thanks for the reply.

I do that now only to verify this problem.

However, I normally never have to worry about the not fully shutting down problem because I reboot the PC after each test, flight or saved flight.

Note: I do the same reboot for FSX (steam), Xplane 11/12, P3D4,5,6 and MSFS2020.

 

If you are rebooting like that all the time, then obviously you are clearing out any such issues as a program not fully shutting down, not to mention lots of other troublesome temporary software issues going on in the background.

37 minutes ago, vonmar said:

Was this information from a MSFS2020 document?

You come on this thread asking for advice, people give you advice , and then you argue with the advice.  Oh well. 🤔

Let's put some pressure on ASOBO. Let's all send them the same report with links to all the threads on this issue. It's tiresome to constantly deal with issues introduced by these updates!

2 hours ago, Bobsk8 said:

2 hours ago, vonmar said:

What is X used for?

It is used for other programs, not recommended for MSFS,

You previous post:

"You come on this thread asking for advice, people give you advice , and then you argue with the advice.  Oh well. 🤔

Actually I asked/quoted you for a link to the information you posted.

So far I have not seen anything from MSFS2020 documentation.

 

Edited May 14, 20251 yr by vonmar

4 hours ago, sniper31 said:

Further, I am not experiencing this "failure to fully shut down" problem that many others are having. Why is that? I have no idea, other than my system seems not to be infected by the problem. 

You are probably a Steam user. This seems to be yet another Microsoft Store only problem.

1 hour ago, Alvega said:

You are probably a Steam user. This seems to be yet another Microsoft Store only problem.

Nope, not a Steam user. MSFS 2020 installed from the Microsoft Store since release. 

16 hours ago, CFIJose said:

Let's put some pressure on ASOBO. Let's all send them the same report with links to all the threads on this issue. It's tiresome to constantly deal with issues introduced by these updates!

Can I ask what they are supposed to do?

It's been proven that this is a MS issue that for some reason the latest version is causing MSFS and probably other games not to shut down as well.  Some of us that never updated don't have the issue.  

So it's not an Asobo issue, they are just affected by MS's update, what are they supposed to do other than lobby MS to fix whatever they broke.

The reports should be to MS though, it's really not an MSFS issue.  

This also explains why some of us aren't impacted.   

W10 and system auto updates off here. 

44 minutes ago, psolk said:

W10 and system auto updates off here. 

Mine are also set to off. I have not updated windows 10 Pro in a long time. This issue began right after the last system update. Therefore, I can only deduce that this is an issue that was caused by an ASOBO update. Let's hope that they can expedite a fix.

4 minutes ago, CFIJose said:

Mine are also set to off. I have not updated windows 10 Pro in a long time. This issue began right after the last system update. Therefore, I can only deduce that this is an issue that was caused by an ASOBO update. Let's hope that they can expedite a fix.

But It has been determined to be a Windows Gaming Services App issue, MSFS is just caught up in it as a result.  

We all got the Asobo update but not everyone had the issue which is why a number of us thought the issue was outside MSFS all along.

Well, the plit thockens. I'm an update or die man. Brought it on myself.

 

dabble with those ruddar usb cables 3 or 4 times.  The sim will then close down quicker than you can say "pay to beta"

dont all thank me at once. 

Some now say that it's working with the latest win 11 updates. I went ahead and updated win 10 pro and I still have the issue. Maybe it will be fixed down the road.

37 minutes ago, CFIJose said:

Some now say that it's working with the latest win 11 updates. I went ahead and updated win 10 pro and I still have the issue. Maybe it will be fixed down the road.

I just updated windows 11. It still is broken. 

 

Just to pour more oil on the fire: 

Beware of making Keyboard binding changes in Control Settings away from 'Default' setting. I tried to change the ESC function, which in Control Settings default are "Toggle Pause" and "Set Pause Off" - which have never functioned, so why they are there, who knows. In Control Settings there is no mention of the "Return to Higher Menu" function, which has worked up until now (as in previous versions of MS Flight Sim). If I alter any key bindings in Keyboard and then load aircreft/place, then I lose this ESC function.

If things get messed up (surely not?!) then return Keyboard to 'Default'. The ESC function then returns.

When setting up MSFS all windows show [ESC] (previous higher level menu item) at bottom left of lower 'in game' task bar. Repeated pressses lead to the 'safe' shutting down of MSFS2020 (and 2024). Do I need to know an original quote to further explain this functionality - no!

Edited June 4, 20251 yr by roadrabbit149
Additional info

Same issue here. I haven't played in 3-4 months. Game updates and then I notice this issue. 

Upon further use, I notice two things happening.  I have to shut down my computer completely (not restart), then start my computer, then launch MSFS2020 to see my game settings (2560 x 1440 display, DX 11, TAA, etc).

But if I just re-start my computer, after force-closing MSFS2020 via Task Manager, FlightSim will default to what appears as the "factory settings"(?) that default to DX12, 3840 x 2160, etc.

Guess I'll come back in another few months to wait on Asobo for a fix.

Incidentally, I still don't like 2024. I'm a low-altitude night flyer and the night lights in 2024 do not look real, are too bright, too white, and Saint Paul's Cathedral is washed out in super-bright lights.

Edited June 6, 2025Jun 6 by PacmanPilot