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.
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 
.
Not a problem at all, it allowed me an opportunity just to double check! 
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.
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.
Remained in beta (same as I always do) default install paths 
I dont have much disabled other then default liveries and double airports (MS store and 3rd party bought) but seems to be fine with enabling.
There are still two duplicate entries in the Insider Hub Preview. Might be better to fix the installer from wiping before changing that. ^^
Do we have any info on when the su2 beta is actually releasing?
Thank you all so much for providing further information as well as answering any questions I’ve asked this morning, it’s all hugely appreciated in order for me to fully understand how this is presenting to you all and then to pass that information onto the development team.
From comments I have seen so far it appears that specifically PC users on the MS Store Platform, who remained enrolled in the SU1 Beta branch via the Xbox Insider Hub, and who also had “enable automatic updates” via the Xbox App are the userbase affected by this update. Should you have faced this update and subsequent data wipe and are still facing issues, it has been recommended to try the “verify and repair” option in the Xbox App, or alternatively a fresh reinstall of the sim.
Whilst I understand this isn’t an optimal solution, and I can understand everyone’s frustrations with the problems faced, we are continuing to provide the details of your reports to the development team, and if we have any further recommendations or information to give, we will do so as soon as possible.
I’d like to thank members of the community who have not only been specific and detailed in their reporting to us so that we can provide as much information as possible to the development team, but to those who have also helped each other in order to mitigate any issues and backup data.
The MSFS Team
I doubt they’ll release anything until this weekend’s mess is sorted out 
This is a very tricky thing to do, because it could also wipe your data. So, it’s better to move data before doing this.
Any company that would show that level of contempt for it’s voluntary beta testers will not have many voluntary beta testers in the future. That attitude is just not how we do it in the industry. So blaming somebody who gave their time to help beta test a release saying that they shouldn’t be surprised if it re-installs everything is not really helpful and just being a bit of a ‘Richard’s Nickname’. Something went wrong and an explanation would help and lessons learnt should stop it happening again, but let’s not try to make out the people on the beta programme should just suck it up, while those not on the beta benefit from the time and effort given freely.
I have that double SU1 Beta entry as well, and I’m still enrolled in it.
Narrative? Please. It’s a beta, meaning it’s a test or unstable release. Things go wrong.
You willingly check a box to accept the terms that things may go wrong and it’s a risk you take if you want the latest advancements that may not be ready for primetime - otherwise you stay with the stable release and wait until all testing is completed.
That’s not to say what happened is not an inconvenience and it shouldn’t have happened, but the fact is people signed up for the beta and got the results of a deployment failure.