That may even be a good thing, but, when installing these updates I’ve found they disturb random things like the size of the rolling cache, and key bindings. I’m not certain what is actually stored in the cloud, and/or whether it has any effect on reinstalling the local files. Also, if you look in the directory where aircraft and the “base packages” are installed, you’ll find a list of “leftovers” from the last update.
This is a wild guess on my part, but perhaps having packages installed all at the same time helps the bits and pieces work and play better together.
The only evidence I have that this may be the case, is that I have gone through this ritual after every update and it seems - more or less - to mitigate the CTD events. The list shown below was all dated 9 or 10 January. All other directories were dated 16 February.
Fortunately, I have fairly decent internet and a fairly high-speed connection, with no data cap. I should be back up and flying no later than 22:00 Zulu today.
I am finally succeeding in completing FS Economy jobs in MSFS. I had to disable the G1000 and G3000 mods to do it. And I discovered that a Windows update had set my USB ports to sleep and save energy. I had turned all that off a long time ago, but it got turned on again. So with those changes, I completed flights without CTDs. I was getting a CTD by touching buttons in the cockpit. My passengers didn’t appreciate it - nor did they care for my language!