So, I fired up MSFS2024 last night. It took quite a bit of time to get to the main menu.  I attempted a quick flight in the stock A320 out of KJFK and it took multiple shutdowns and restarts and it still didn't work right.  Engine covers not showing but also not removable, missing nav data, and inability to enter into managed modes.

I then realized that MSFS2024 had automatically updated itself (it's an MS Store install, streaming rather than completely downloaded) to 1.6.34.0 (SU4).

I've seen some recommendations to move community folder content before updating. How do I do that if I don't know if an update is going to occur until I run MSFS2024?  Only things I have installed in community folder are the Navigraph hub contents including the PMDG planes, as well as a downloaded install of the Aerosoft Paderborn airport since it was the only way I could get the VDGS to work.

Do I just need to move the content to a backup folder, rerun, shut down, and move the content back?  So I just need to uninstall and then reinstall everything in Navigraph Hub?

Thanks, 

John Powers

None of what you’re describing should be caused by an update (default planes should just work)

You don’t need to empty the community folder before an update.

You only need to do that if you update and start having issues - some addons need updates as well, but most of the time it just works. Given that you have very few items in your community folder, I would simply update with OC3 and Navigraph and continue. 
 

if you are still having issues, it’s likely something else. 

8 hours ago, 3catcircus said:

I've seen some recommendations to move community folder content before updating.

Sounds like the beta update instructions. Doesn't apply to non-beta updates.

8 hours ago, JonathanC said:

...

You don’t need to empty the community folder before an update.

You only need to do that if you update and start having issues - some addons need updates as well, but most of the time it just works. ...

Yes, the advice to move the community folder has never made any sense, it just adds extra steps to the update process. If you move the community folder and update, then you will just need to put your content back eventually, which may or may not cause issues. Just leaving it there removes these unproductive move/put back steps. If you update and have issues, the next step would be to shift the community folder out, and see if that helps, which would pinpoint a problem with an addon.

Probably still makes sense to backup your community folder, though.

Thanks for the advice.  It seems like every time there is any update, I've got to reload at least twice. I'm wondering if it's just because it's a streaming install and stuff takes a while to finish streaming.  Like, even the airports sometimes take a while for the jetways and pushback tug to appear.

Firstly, there is no need to do this unless you encounter trouble.

Secondly, if you really need to do this (I never have in five years of MSFS) why keep moving the Community folder about when you can just rename it something like xCommunity the rename it back at any time?

MSFS will create a new empty Community folder on startup when it doesn't find one, but when you want to put it all back to how it was, you simply delete that new empty one and rename xCommumnity back to Community.  Job done, no moving or copying.

Edited April 13Apr 13 by bobcat999