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.
I disagree because I doubt they did it on purpose so how could they “show contempt for the users”?
We can go back and forth about it all day but the fact is if you sign up for a beta you sign up for the chance that things will go wrong - and they did.
Fact is that this could also happen in release. The issue was that ‘something’ was pushed to the server and the installer reacted to that. Again… the installer is the same for everybody.
Sure - but it didn’t, it only happened to the beta signups. Perhaps if it was to the “stable” branch then the response might have been a bit more urgent…
I hope so! That would be a bigger issue then.
The problem with that is that the SU1 Beta was over when SU1 was released. That makes those affected by this issue ‘former’ SU1 Beta testers.
And SU2 Beta hasn’t been released yet. So no one is technically in the Beta test program. The update (whatever it was) was a update to the SU1 release version.
@Chewwy94 question: For those who are in MS Store and did not update what is the recommendation? Wait for further instructions? Orpting out the beta will prevent the issue?
The problem now is the double entry, it will almost certainly cause a new status update if this is changed (because it suggests two different versions, but they arn’t) and might repeat the reset.
Well that’s where it becomes a user issue because you then have to pull yourself out of the beta program by reversing the action you took to get into it.
For instance on Steam, I am responsible for deselecting the “beta participation” option, otherwise I see this and remain susceptible to any future beta failures.
Just FYI. I did not have auto-updates enabled in the XBox app. However, I received the update when normally launching the sim.
What is the default folder structure in Steams FS24? I dont have the Steam 24 version yet so can’t check. It looks like their default settings are better managed.