Ms store version: non-default CF untouched; graphics settings changed: CF location had to re-entered in usercfg.opt; backup exe.xml restored to Local Cache; rolling cache reconfigured as it was reset.
I was affected by that issue, but it’s also important to mention something:
- only people that were in the beta were affected
- people don’t read the official microsoft releases
What I can understand from this is that some form of update was done inside the Insider Hub to prepare for the launch of SU2 beta, and what happened was that it triggered a reinstall…I work in IT (not for MS at all…) and it’s very normal for things to go wrong even though you did everything you could to prevent it…in IT Murphy’s law happens all the time…people plan for all contingencies, but then things happen that you didn’t expect, and it’s not a lack of professionalism or something…lots and lots of things can go wrong nowadays… give them a break please
12 Likes
• Remained in Beta preview post SU1 release
• Entire \…Limitless…\ directory fully wiped clean by automatic update process
• Community folder in custom location untouched
• Able to re-enable content via Library
• Noted Zinertek Enhanced Airport Graphics (2024 version), one Savoia (not the other in the pack) and one Junkers Ju 52 livery (no other part of the Junkers Ju 52 pack) were automatically enabled with the sim’s creation of a fresh Content.xml file. This seems pretty odd, given one is a 3rd party add-on and the other just a livery. With prior fresh creations of Content.xml the sim would never enable 3rd party content by default nor would it enable any part of the Aviator Edition content.
• Cloud saved settings were successfully restored upon initial launch of sim
Yes, I was still in the SU1 Beta.
Automatic update has deleted my community folder and LocalState and LocalCache.
I retrieve all my addons in the community folder with MSFS_AddonsLinker tool.
LocalState and LocalCache was recreated at the first launch.
- Remained in Beta preview
- Community folder in default location completely wiped
- No problems re-enabling content
- Cloud sync successful so controller profiles were not lost
- Graphic settings reset
I was opted into beta, community folder was long since changed to another location. I tried to get out of beta by first starting the PC without network connection and disabling the automatic update in the Xbox app, but after restoring network and opting out of beta the program folder was still deleted and reinstalled twice. The community folder survived and only had to be set in the MSFS options again. Activation of library content works.
Same problem here. MS Store version & Beta. I understand it just reset the community folder location, because my custom folder is there untouched. I don’t know for poeple with default folder.
I don’t know if this is relevant or not.
I was in the beta but left immediately prior to SU1 rollout.
I always launch MSFS using fast launch using addon linker and have flown at least four times over the weekend.
I have never had the issue but believe I came close on one occasion as I opened up the xbox app to double check that I was opted out of beta. Immediately the xbox app opened I got a message that there was an update. Not likely I thought and exited the app PDQ.
I also work in IT, and while agree with you for the most part, this is not the first time this has happened. It happened multiple times in the 2020 Beta’s, and you would think a thorough investigation of what happened on those occasions would have been done, and then a plan to either mitigate or avoid it entirely, or at the very least a comprehensive report of what happened, so that manual intervention on the part of the users could happen should it be avoidable.
No official warning was put out, and I don’t consider “could be as early as today” counts for that, plus if you work in IT would you not agree that pushing out an update like this on a Friday is one of the worst decisions they could make?
When you schedule an update, you say this WILL be happening on such, and such a day, not it might, hold you finger up in to the wind etc.
12 Likes
Was anyone affected who was NOT on the beta branch?
If so this is an entirely different issue because by signing up to the beta you sign up on the basis that things might go wrong at any time and it probably shouldn’t be a surprise when it does.
1 Like
MSFS 24 purchased through MS store/Xbox App
Remained signed into Beta program after SU1
Xbox App is set to not auto start and not to auto update programs
2024 installed in non default location
Was in the sim when the update happened and saw this post while I was in cruise
After completing flight I immediately shut down my PC and left it all night.
In the morning I first checked if my Community folder was intact. It was.
I then went into the Xbox Insider Hub. I had two instances of the beta program as shown in others screenshots in this thread.
I selected one instance and left the beta.
Restarted PC twice. Checked insider hub again and it showed I was removed from the beta.
Started Xbox app. No update was presented.
Was able to start the sim with no issues.
No other issues have presented themselves since.
This narrative needs to stop.
This issue is regarding how an Installation/Update is deployed, which is an MS Store function and has nothing to do with the actual content of what was deployed — which in this case was the exact same version of what we all already have for the retail release.
It further highlights deficiencies in the decision to put non-replaceable user-data in a known hostile environment. That same non-replaceable data is being stored for non-beta users in the same hostile environment. This data needs to be stored outside of the \…Limitless…\ directory structure.
This same issue could occur via an update to the retail release.
Rubbing people’s noses in the “you signed on for this” isn’t helpful nor accurate in this case.
25 Likes
I have tracked back to try and find the post i saw but going through that many i couldn’t find it. Sorry, it was a needle in a haystack of ms store users. I may have interpreted what i read incorrectly at the time, its a possibility 
.
2 Likes
Not a problem at all, it allowed me an opportunity just to double check! 
2 Likes
Yes I was on the beta branch, but got kicked from it some time ago after su1 officially released.
PC, Xbox store.
I was in the beta originally, once su1 officially released, I noticed I had been kicked from the beta.
I received this rogue update.
PC / Xbox store.
Can’t comment on the latter not tested that.
As the team gets their arms around what happened with this incident, please let us know if anything needs to be done to “stabilize” our installations.
I think I have restored everything that needed restoring—had a couple of great flights yesterday—but, that double enrollment in Insiders Hub does not seem right. How should we correct that if we see it? Or, is ok to just ignore?
Thanks.
Are you able to send a screenshot of this double enrolment within the Xbox Insiders Hub if possible? I’ve personally opted out of the beta via the Xbox Insider Hub, and now in the “Available” tab under “Previews” I only one option for MSFS 2024.
Thanks so much
I was still in the beta. xbox store version. Update ran without my knowledge as well as not having xbox start up upon boot, or running the sim at all. Entire /LocalCache directory empty. Went to inside hub and “switched” to the other beta entry that was available.
(image from the above thread, but i saw the same thing)
xbox proceeded to install the 8gb update, and the contents of LocalCache returned.
AddonLinker content relinked to Community folder.
Sim started fine, Albeit window and graphics settings seemed default, Marketplace items that were enabled, stayed enabled.
Insider hub currently shows one entry again. I’m still on the beta I assume.
2 Likes
Yep, was still in the insider preview and got the 9gb update.
Everything reset/reinstalled but my community folder is on d: drive (custom path) so it was fine. Several others got their entire folders wiped out tho (default path I assume).
For the most part, all windows store/xbox users impacted. No steam users it seems.
All settings reset, all enabled or disabled content reset, etc. It was a full reinstall. Reported to seedy on Friday.
I decided on Saturday to leave preview and just deal with the reset.