16 hours ago, psolk said:

Did you install the City Update?

Yes for MSFS2024. Don’t recall a City Update for 2020 though. Could be wrong.

Cheers,

David

So interesting tidbit.  After my flight yesterday in which 2020 shut down without issues I decided to update my drivers from the 572.16 train to 576 train.  Installing the drivers I got a black screen which was resolved with a reboot and the driver showed installed fine.  Went into MSFS and there was a microstutter so I exited out but noticed ASFS said "connected" after I shut down so opened task manager and there was MSFS at 27% CPU like others have pointed out.  

I shut it down, rebooted went into the Nvidia app and restored my prior driver version (a nice feature of the app is actually driver rollback)

I tested last night after reverting the driver and all was fine.  

I also did a flight today in 2020 with the 777 and again, it just shut down fine.  

Now I know people will say but I didn't change their driver which I understand I'm just pointing out I was able to replicate it with one driver version and eliminate it with another 572.16.  Maybe worth a try if you are having the issue.  

As always YMMV 

Take care everyone, be well.  

Edited May 3, 20251 yr by psolk

Well it has been over 2 weeks since this bug has been reported on the FS Forum, 450+ upvotes to fix it, over 400 posts with users having the same problem, and total silence from Asobo. And people expect them to fix 2024....LOL

2024 is solid now so maybe it's time to drop 2020 like a hot potato.

Besides 400 out of millons is tiny. IMO.

dd

2 hours ago, Sky_Pilot071 said:

2024 is solid now so maybe it's time to drop 2020 like a hot potato.

Besides 400 out of millons is tiny. IMO.

dd

Solid for you maybe

certainly not solid enough for me and others with our own specific use cases and requirements.
 

Yeah no thank you 

 

To each their own.  I would also suggest not to minimize each others issues. I’m sure you would not appreciate someone coming in and minimizing an issue important to you and having them tell you to just move on completely ignoring and dismissing the investment put into product that you were using.

Edited May 3, 20251 yr by Maxis

34 minutes ago, Maxis said:

Solid for you maybe

certainly not solid enough for me and others with our own specific use cases and requirements.
 

Yeah no thank you 

 

To each their own.  I would also suggest not to minimize each others issues. I’m sure you would not appreciate someone coming in and minimizing an issue important to you and having them tell you to just move on completely ignoring and dismissing the investment put into product that you were using.

A few people have had all their settings wiped out when shutting down MSFS using task manager. 

35 minutes ago, Bobsk8 said:

A few people have had all their settings wiped out when shutting down MSFS using task manager. 

Bob, I know you don't like new drivers and I also know you didn't change your drivers to cause this issue but if you would be willing to try the 572.16 there is a "chance" it may resolve the issue.  As I mentioned above, I was able to repro the issue with the 576 drivers and reverting to 572.16 the issue immediately went away again.

Just a thought if you wanted to try and see if it shuts down with a different driver. 

22 minutes ago, psolk said:

Bob, I know you don't like new drivers and I also know you didn't change your drivers to cause this issue but if you would be willing to try the 572.16 there is a "chance" it may resolve the issue.  As I mentioned above, I was able to repro the issue with the 576 drivers and reverting to 572.16 the issue immediately went away again.

Just a thought if you wanted to try and see if it shuts down with a different driver. 

At least half a dozen people have tried changing drivers, but it has no effect. I use the windows 11 shutdown method  now which works with one click, so I will stick with that for another 6 months or however long it takes Asobo to fix this issue. 

1 hour ago, psolk said:

Bob, I know you don't like new drivers and I also know you didn't change your drivers to cause this issue but if you would be willing to try the 572.16 there is a "chance" it may resolve the issue.  As I mentioned above, I was able to repro the issue with the 576 drivers and reverting to 572.16 the issue immediately went away again.

Just a thought if you wanted to try and see if it shuts down with a different driver. 

I doubt that a driver change will resolve this issue. This was introduced by the last mandatory update. We need to wait for a fix by ASOBO.

Just now, CFIJose said:

I doubt that a driver change will resolve this issue. This was introduced by the last mandatory update. We need to wait for a fix by ASOBO.

Driver change doesn't solve anything, and the bug was there episodically, unsolved for the last 2 years at least, Asobo was unable to reproduce it.

17 minutes ago, CFIJose said:

I doubt that a driver change will resolve this issue. This was introduced by the last mandatory update. We need to wait for a fix by ASOBO.

interesting i might check my drivers then, im on 572.16 and ive getting the issues.  First time ive had it.  Its only since i either updated the sim or updated the driver,  i did them all in the same week. 

Edited May 3, 20251 yr by fluffyflops

1 hour ago, Bobsk8 said:

I use the windows 11 shutdown method  now which works with one click

as in your shut down windows from the start menu right ?

Ive only just started having this issue since the last update, its a horrible bug. 

out of interest are you using the google map enhancement tool ? 

Edited May 3, 20251 yr by fluffyflops

11 minutes ago, Claudius_ said:

Asobo was unable to reproduce it.

what absolute tosh.  if 400 plus people are raising it then its an issue.

software programmers really baffle me sometimes. 

I doubt that there are resources to change a font color currently

Don't forget I had problems that 2024 can't reproduce.

dd

Edited May 3, 20251 yr by Sky_Pilot071

53 minutes ago, fluffyflops said:

interesting i might check my drivers then, im on 572.16 and ive getting the issues.  First time ive had it.  Its only since i either updated the sim or updated the driver,  i did them all in the same week. 

It's not the driver. If you want a stable driver try 566.14. For me it's been very good.

Win 10 user but it should work well with win 11.