MSFS is far too wobbly when it comes to bad data. If someone installs a hook into the code (can Simconnect do this ?) and stuffs that up, there’s not much they can do. Bad data structures should crash the sim with an error that gives some clue what the problem is.
Three things are desperately required.
Logging on setup activities, loading stuff in from storage or the internet, plug in events etc. Like the X-Plane log. If stuff is loaded in a known sequence on start up, then if you know the last thing that was started it helps identify what isn’t working.
A method of verifying the files that are loaded, something that checks .fspackages are installed and optionally verifies them. At the moment if your install is stuffed up there is no way of knowing. Hopefully MSFS is less of the intertwined mess that Windows is.
A way of temporary disabling if possible, clearing if not, stored data so if that gets corrupt it won’t crash stuff, and if it is a way of clearing cloud MSFS data,.
Like Windows, it relies on installs working and nothing ever getting corrupted at present (technically known as “being with the fairies”).
Such would reduce support demands significantly as it would make it possible to diagnose without guessing.