Assigned to Beta - then complete MSFS Installation deleted

Dear FS Team,

one hour ago, I joined XBox Insider Beta for the upcoming PerformancePlus run.

Now, I wanted to start MSFS and I was immediately redirected to Microsoft store to download an Content Update. After loading the 1.65GB ( listed as 1.17.3.0), I realized that my complete Installation has been removed, including community folder, everything.

Now, starting MSFS prompts again for the full installation.

Same happened to me after World Update 4 Beta. That time I had to reinstall Windows 10 from scratch, my system only has MSFS installed + PMDG DC-6 as the only add-on.

This is really shocking. I am such a MSFS supporter. I love it, but you can’t just wipe your customers installations without any notice. What is going on here…

Best Regards,
Heiko

Make sure the folder is directed to the correct drive where you originally installed it

1 Like

The Beta hasn’t started yet. The sign-up process simply records who will get the Beta assuming they were selected, no downloads related to PerformancePLUS are yet available.

5 Likes

I installed fresh to Drive E:

It doesn’t matter if I select the softlinked folder on c drive or physical installation folder e drive, it wants to install the 90 GB again…

C:\Users\broek\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages
E:\WpSystem\S-1-5-21-2887339021-243759426-3046539486-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\

Everything is gone, again…

Thanks for this information. Better tell the fantastic update procedure to stop wiping my installation for no reason.

1 Like

Interesting, it’s what happened to me during the mini update last week. I didn’t pay attention to the folder and said it wanted to download and install 95GB then I looked at the folder selection it showed what you showed in the pic above then I browsed and pointed to the correct folder of mine which is C:/MSFS20 and all was ok

The issue has nothing to do with you applying to the beta.
I’ve seen other people with the same issue and indeed they had to reselect the folder and it worked.
Some like you had to re d/l everything.

There is an issue for sure but it is not related to your beta subscription.

do not move msfs launcher!
Next time install launcher on C and Packages (official. community) on E.

Your problem is not related to beta
https://forums.flightsimulator.com/t/forced-erroneous-reinstallations-and-deleted-content/412888/13

1 Like

I moved it, I’ve nothing left on C and have no problem apart from the fact that… well, I had to redownload everything :sweat_smile:

Better configure Windows and change where you want uwp apps to be installed by default before downloading anything.

I did not move anything. In a fresh installation it is asking for a drive, I say “E” that’s all. Just looking at the folder structure shows me that it goes physically there.

I assume it is a known bug to only install on Drive C ?
And I may understand that the system may not find the packages anymore, but wiping everything ???

In some cases.

Yep.

Install launcher (1.6GB) and MSFS on C
After that

1 create new folder named MSFS 2020 on for e.g. E drive
2 copy official and community folders from
C:\Users\YourUsername\\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages

to E:\MSFS 2020
3 after that go to
C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
4 In notepad open file named UserCfg.opt
scroll down to the bottom and edit last line
e.g.
InstalledPackagesPath "C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages"

change
InstalledPackagesPath "C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages"

to for e.g.
InstalledPackagesPath "E:\MSFS 2020"

save changes

After that go to

C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore

and delete all files and folders

I’m never changing the default 1.6GB core install on C:
It’s basically only the ~78GB official folder that I’m choosing to install on a different drive.

there is something total wrong with “Microsoft.GamingApp” . It seems it can’t be properly started under my local admin user…

Durch die Berechtigungseinstellungen für “Anwendungsspezifisch” wird dem Benutzer “DESKTOP-5BRH77U\broek” (SID: S-1-5-21-2887339021-243759426-3046539486-1001) unter der Adresse “LocalHost (unter Verwendung von LRPC)” keine Berechtigung vom Typ “Lokal Aktivierung” für die COM-Serveranwendung mit der CLSID
{37399C92-DC3F-4B55-AE5B-811EE82398AD}
und der APPID
{37399C92-DC3F-4B55-AE5B-811EE82398AD}
im Anwendungscontainer “Microsoft.GamingApp_2107.1000.30.0_x64__8wekyb3d8bbwe” (SID: S-1-15-2-1723189366-2159580849-2248400763-1481059666-1951766778-2756563051-3565589001) gewährt. Die Sicherheitsberechtigung kann mit dem Verwaltungstool für Komponentendienste geändert werden.

Edited
Read again please :wink:

Also he can stop download process (big files) and point to new folder named for e.g. MSFS 2020

Thanks for your support. It is the third time after World Update 4 to install from scratch, each time +130 GB. I can manage it, but hopefully Asobo gets this under control soon. I would have doomed every other game forever…

All this XBox Gaming Service, is not ready yet…

You’re welcome

SU4 (sim update4) :wink:

Maybe because you forgot to leave preview SU4?

Leave the SU4 insider preview in the Insider Hub. Chances are you’ll need to reinstall again. Every time the windows store update service is run, it is prioritizing the insider beta as a mandatory update, which will immediately overwrite whatever you have installed. Three reinstalls later I’ve done some digging and managed to understand that much is going on.

1 Like

I was not in SU 4 Insider Preview anymore. Just after joining todays Beta it occured again. But of course this could never be correlated as your moderator colleague pointed out…
What shall I say, the Store Updater, Gaming Service and Insider Preview System seem to be from outer space…

Yeah, so what I believe happens is as soon as you join an Insider beta, this is synced to your MSA (Microsoft account). Your MSA data is also loaded when launching the game, and once there is a conflict between your Insider beta version and what is currently the retail/live version there is either no system to verify your files, or a very poor one. So even though the beta isn’t live, the Insider data correlating with your access is still attached to your account, which I believe is what is prompting these reinstalls/conflicts.

1 Like