Yesterday I had another CTD during a flight of over 2.5 hours. I would have needed another 0.5 hours to land and got a CTD.
Afterwards Windows reported a successful update of the game service.
That doesn’t exactly give me happy feelings.
I used to have this problem several times in the past and actually thought that it had been fixed.
The FS should therefore ignore an update and restart of the gameservice,
Or NO game service updates when games are running.
Regards
Ralf
I had this exact same thing happened to me like 3 or 4 times on short final.
Really annoying indeed to say the least.
+1 from me.
Game services is probably the bug that’s causing checking for updates and load hangs too. Even if I load addon linker items, I’ve been starting from the Xbox app but first running the support repair tool. Practically every other time I run it it’s finding something to fix or update. Past two or three weeks it’s been a headache. Something is moofed.
I had this some time ago, what fixed it for me was turning off auto-updates in the Microsoft store app. I run FS separately from the Xbox app.
I just load the store, and check for any updates before running FS. Not had a CTD since, and I’m too scared to go back to the normal way. 
If updating the game service app it should be no problem for the developers to add a logical function to the app that no game is interrupted.
The whole world is speaking of AI and automatism, but I should do this manually?
Well then, I’ve seen software growing up from the beginning and then I can say: the good times are gone. 
For me Microsoft Flight Simulator 2020 is game of the year.
I would not agree to this, but since the 4 years there are some, let’s say little problems, that could be fixed very easily. But they didn’t do it. So I’m asking, why not? It could save our nerves very well and my frustrations would be reduced to 50%.
Remember when it took 60-120 seconds after clicking the MSFS icon before the window showed up? They eventually added a splash screen that comes up within a couple seconds so you can tell whether or not you clicked the button yet during that ssllooww loading of the window.
Even these tiny things make a huge improvement to the experience using the game.
Had a similar issue the other day, but I have a potential workaround.
Essentially you have a script that stops both the BITS & Windows update services as the sim loads. This script is executed by elevated Task Scheduler tasks, and the tasks themselves called by the MSFS start-up script. Takes 5 minutes to set up, and should stop things like this from happening in future.