flexy123

I spent several days restoring my apps and even a Windows repair install didn't get my apps back. Only short before an entirely new Windows install I was able to restore my apps and MSFS, more or less by coincedence. DO NOT, EVER mess with the WindowsApps folder.Trust me. There is no "kosher" way to get to the "folder" of MSFS with the store version, and even if you can (with permission hacks) it's pointless as the filesystem is virtual/encrypted and you cannot edit, not even actually read the files. Saying the files "appear" in this folder but in reality they are on a hidden encrypted volume. Start MSFS the recommended way, eg. with the Icon for the app. The only folder where it's making sense that you want to access it is the package folder (where the content is), which is usually C:\Users\[USERNAME]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages However this can vary, ie. if you install somewhere else. Find your Package folder in MSFS ---> start up Developer mode ---> Tools -> "Virtual filesystem and then check the "Watched Bases", this shows you where you Package folder with the Community/Official etc. folders is.

I never used this setting you are mentioning there. I just looked, even if I would for some reason need these settings, it does show my SSD K:\ <-- is it possible that your SSD has no Volume created on it yet? (Eg it is not formatted?) Anyway, this is what I did, and the question of the sim installing somewhere I don't want to never even came up: I have the Xbox PC Game pass (BETA) app for PC, which is required. I purchased the game pass. I logged out from that Xbox PC app and back in, and now Flight Sim in the app offered the option "Install". I clicked on the install button, and I don't remember the exact wording, but it asked me where I wanted the sim installed.I specified my SSD, which (Volume name) is K:\ Make sure that the drive/SSD you install has 150GB (AFAIK) free space. If your SSD is new and just installed (?), you need to format it first as this creates a Volume name. (Eg. C:, D, whatever). Otherwise a drive isn't visible in Windows. >Will it download to d: which is where Apps are specified to be saved, but then allow me to actually install it to E: ? Even if it would d/l to D:\ it would just download about 900MB (the installer and the exe) on D:\, plus it will ask you where you want to install the packages (the 90GB). Even if the installer app would have downloaded/installed on D:\ there should also be a way afterwards to move the app to another location.

I think that people are getting several things confused here, re: MSFS possibly installing itself on drives where it shouldn't, and also (and in particular) about the Windowsapps folder on C:\ I got the Game Pass version and the game installed as I directed it on my gaming SSD, which is K:\ The game (the installer/launcher, as well as the content) are NOT on C:\Program Files\WindowsApps <---- which is the default folder for WindowsApps. It only appears so. Instead, there are links/junctions in it which are pointing to the actual install, which in my case is K:\WindowsApps. (Saying, MSFS made a copy of WindowsApps on the SSD, and the OS is pointing to it) I don't see any parts of the game on drives where it shouldn't be, but I see links/junctions pointing to the game on SSD. The FlightSim folder in C:\Program Files\WindowsApps is a junction that in reality is pointing to the SSD. With special tools (WizTree etc.) one can see where the game really is. ** Some people, here and elsewhere, are "recommending" taking ownership of the C:\Program Files\WindowsApps folder "to see files". DON'T! I once messed with permissions on this folder, and it will absolutely hose all your apps in the best case and your Windows install in the worst. (Getting original Windows permissions back is a nightmare, there are only two tools I know of which are capable to do this). It is also pointless to take ownership of the C:\Program Files\WindowsApps folder because as already mentioned, THE GAME IS NOT IN THERE if installed elsewhere, there is only links in there. Whether changing permissions/ownership of the WindowsApps folder *copy* on the SSD (where the game has installed itself) would break the game, I do not know. But it's not just a permission issue to get "access to the FlightSimulator. exe", eg. for AV programs and similar. The thing is that the sim is also using an encrypted file system/folder, with some saying that the files "don' t really physically exist as they appear" but that they are mounted on a virtual, non-accessible file system. This would mean one can play with permissions until blue in the face, it won't work. For example I can change ownership/permission of this folder to see the files, but they still can't be read or modified. HOWEVER, you don't need to as all actual content, the 90GB game data with "Official" and "Community" content are accessible like normal. There are only a few cases where one might need access to the actual *.exe, for whatever reasons. Even if in theory it would be possible to somehow turn the game install into a normal game install with all files accessible, I'd bet it would break all kinds of things such as DRM. TLDR: If you tell the game to install on your SSD drive, which say is K:\, and you also specify that your game packages should be on SSD, eg. K:\MSF Packages (like I did), the game should absolutely be on your SSD and not somewhere else, even if it may not appear so.Don't let filenames/hardlinks/junctions confuse you.