17 minutes ago, JaseMelbo said:

Turn on computer, get Microsoft Store update, Install Mandatory Update, Install World Update, Install Content Manager Updates, Restart Sim - DONE

Thats the way! (Only adding Rolling cache thing to be done if in use) Like Bert said the comm folder move or whatever is utterly nonsense. If you later run into problems with especially single mods, delete them and wait for mod update.

Cheers T.

3 hours ago, RaptyrOne said:

Once everything is done, close down the sim, and restart PC.

I'm on Steam as well and I've never done this and have never had issues. Just curious and wanted to know what the restarting does. Is it something to do with the Registry? Thanks for any info 🙂

2 hours ago, Fielder said:

I never delete all the files in community, I just rename the community folder instead. And the create another new folder named community which is empty of course, and then do the update. Then delete the new empty community folder and rename the full one back to Community.

This the same way I always do it …

2 minutes ago, GSalden said:

This the same way I always do it …

Why? 😉

3 minutes ago, Bert Pieke said:

Why? 😉

Beside the Addons Linker links I have several scenery continuesly in there, so this is the easiest approach for me.

2 minutes ago, GSalden said:

Beside the Addons Linker links I have several scenery continuesly in there, so this is the easiest approach for me.

Why do it at all? 

With Steam, this update was no different than the predecessors. Launching the sim from the desktop screen, approving the mandatory part, fetching the optional part in the Market Place. No sweat.

The only thing is that MS should have instructed clearly that the content manager had some older Asobo’s airports and sceneries to update.

And, it would be nice if the download didn’t bring with it all their liveries yet again : waste of a capped bandwidth, waste of SSD space.

Left Community as it was but I have few addons.

Edited September 8, 20214 yr by Dominique_K

I haven't touched the community folder for the last few updates, and it hasn't been a problem for me, and mine is 26 gigabytes. 
I had a few CTD's with the original SU5, but all of these stopped after the last sim hotfix, and the update to the G1000NXi.  Both of these were fixes for the known CTD issues; I never had to touch the Community folder at all, and I was stable afterwards, and still am today after WU6.

If there is a known issue with an addon, I delete it and wait for the update - simple as that. 

I really dislike this mythology that is put out there with no logic - it just wastes people time.  It is like the people reinstalling windows and the whole sim all of the time to fix something that is normally a simple config error - crazy!

1 minute ago, bobcat999 said:

. 

I really dislike this mythology that is put out there with no logic - it just wastes people time.  It is like the people reinstalling windows and the whole sim all of the time to fix something that is normally a simple config error - crazy!

Voodoo computing

The time it wastes for me is roughly 10 seconds. 30 seconds for someone not used to doing the folder/file rename thing for years in different verfsions FS, I would suppose. Only one CTD here in 6 months (over 1000 hours flying).

5 hours ago, RaptyrOne said:

I am curious about this, what does this do?

Snake oil.

57 minutes ago, Bert Pieke said:

Why do it at all? 

Bert, this step was introduced in order to prevent CTD after installing an update, as we all know, our Asobo friends like to surprise us with unpredictable changes that will upset some of our add-ons, I too did not empty my Community folder the first updates and it worked fine, I was only lucky.

I am using Add-On Linker and all it takes is ONE click to remove all the links from my Community folder, that way MSFS can start without any excuses for a CTD. 

To re-activate the links as we all know, ONE click in AddOn Linker and you are done for your second MSFS start, if anything goes wrong (CTD) the Add-On culprit chase starts!

1 hour ago, Bert Pieke said:

Why? 😉

 

Don't bother, Bert,

humans need myths - you are right - the updates do not care about the contents of the Community folder and are not influenced by them - the contents is not even loaded during the update, because the update is executed before the first load of the sim.

There is a warning by Microsoft that certain addons in the community folder could fail after the update because they might be no longer compatible with the game - and that is commonly misunderstood so that there is this narrative now in the world to clean the community folder before the update.

But : It does not harm. So let them keep on renaming the community folder. 

 

Edited September 8, 20214 yr by PTI139

1 hour ago, Fielder said:

The time it wastes for me is roughly 10 seconds. 30 seconds for someone not used to doing the folder/file rename thing for years in different verfsions FS, I would suppose. Only one CTD here in 6 months (over 1000 hours flying).

Some people just don't see it logically.  I used to do it (rename the community folder), then I thought it through.

MSFS doesn't touch the Community folder during an update.

If you have an incompatible item in your community folder, the first time you go to fly after the update, it may cause an issue.

If you rename your community folder to start with, you have to name it back at some stage, and then you will have the same issue anyhow, just later. 

However at this stage, you will now know what that is, because it is the third party aircraft or airport you selected at that stage etc. 

The messing about renaming / deleting the community folder before the update achieves nothing, and most of the issues with third party stuff in the community folder are just non-functional or incorrectly functional issues after an update, not complete CTD's.

 

Edited September 8, 20214 yr by bobcat999

5 hours ago, RaptyrOne said:

I’m on Steam but for me the process was:

Ran Windows Update. There was an update, can’t recall details. Updated and PC asked for restart. Did that.

Read the release notes… go into Community folder and delete all flightsim.to add on airports that were listed in the release notes as having been updated in some way. I had 3 or 4. I did NOT delete anything else in Community. I don’t think it is necessary.

Next, run Steam, let it do the small update there which happens automatically and so fast you can miss it.

Then, run the Sim and do the core update.

Once in the sim, update first Content Manager, then the new World Update stuff in the Marketplace. (Asobo have not specified which should be done first so I don’t think it really makes a difference but this order makes sense to me).

Once everything is done, close down the sim, and restart PC.

On restart, did an update to Navigraph and A32NX, checked Orbx and PMDG operation centres for any updates (there were none).

Loaded up the sim, checked through all settings options, cleared Rolling Cache and….

Happy days!😃

 

I agree 100% with your schedule, but have highlighted what I believe to be the most important stage of all 🙂   Read all the info BEFORE you start the update and then validate any add-ons you may have that conflict BEFORE starting the update.

I didn't need the windows update, but for me exactly the same procedure,  and it was smooth and fast this time.

Graham