I am so happy to report that the MSFS on both my machines have recovered from CTDs. One by reinstalling to a new folder. The other was by replacing the Community Folder with an empty one.
After I posted the CTDs on both my machines yesterday, Robert Temmerman suggested me to remove the Community folder to avoid any potential or tangible incompatibility among the addons in the folder with MSFS update. He said he ran into similar situations before and it took him a while to figure this out.
Jim Gerow also forwarded me an announcement from RealsimGear saying that their addons are temporarily incompatible with MSFS after France update and they are working onto fixing it.
Sadly, I didn’t receive any notice from RealsimGear nor I alerted enough to aware that the GNSs I recently added to my system would be the culprit causing the crash.
Unfortunately, by the time I got the suggestions from Jim and Robert, I had already uninstalled the game and started reinstalling it on machine one again. Since I didn’t want to stop the process (because I was curious to know what the status would be after reinstallation), I waited until the end of the installation to try Jim’s and Robert’s suggestions.
You know what: I couldn’t believe that the reinstallation even took lesser time than just carrying out the World Upate IV on the same machine before. It was because I had to reset my machine three times in order to fix the looping errors in different stages during the update. How hilarious.
Thanks goodness, the reinstallation went well and the MSFS on the first machine was up again.
After recovering the first one, I took the suggestions from Jim and Robert by renaming the Community folder and creating a new one on the second machine.
Bingo! It immediately fixed the CTD.
If I had known this earlier, I wouldn’t have to spend a night’s time reinstalling the first machine.
Again, MSFS is buggy. That’s undeniable.
Colin commented that Asobo should stop giving us the glam updates that often conflict with third party addons. I couldn’t agree with him more.
I believe many developers are pissed on these irresponsible results as well since they have to clean up after Asobo’s mess in order to have their products to be compatible with MSFS again and again after each update.
Anyway, my lesson learnt is:
It is better to backup and replace the Community folder first with an empty one just before carrying out any future update. That would save me a lot of troubles.
Rob Knott said Asobo should stop screwing people’s weekends up with their mess.
I am really glad that I don’t have to end up this way.
Lastly, thanks to all who gave a helping hand when I was so depressed yesterday.

I did download the latest MSFS update, re-installed the RealSimGear Windows driver and my RealSimGear G1000 suite is back functional again. (P.S. While I was at it, I also did the FSUIPC7 update as well.)
Hope this will get you back in the air!
LikeLike
Thanks very much, Jim.
I’ll reload again to see if the issue gone.
Tom
LikeLike
What I have been doing for updates is to rename the Community folder prior to update to Update.Community. MSFS then creates a blank community folder during the startup process. Once i have MSFS running with nothing in the Community folder i exit, delete the blank Community and rename the Update.Community folder back to Community. This way i have a good indication that if i have a problem it is an addon in the community folder.
LikeLike
Good idea, Ty. Then I don’t have to create the empty Community folder myself.
LikeLike
You can also install your add-ons into a different folder and use MSFS Addons Linker to create links in the Community folder. That makes it safe and easy to empty the Community folder anytime, since you can you always run MSFS Addons Linker again to recreate the links. Download: https://flightsim.to/file/1572/msfs-addons-linker
LikeLike
Thanks Demetrius.
Actually I’ve been using the utility for quite some time except that I continued keeping many addons, such as the RealSimGear’s in the Community folder. It’s time to change, for sure.
LikeLike