Marketplace Scenery | CTD

I installed the packages in F:\MSFS which is a non standard location. Now, I first bought Vienna from marketplace, it did not work and then I bought Cologne-Bonn, that also did not work. Both followed exact same pattern, is it because packages are at a non standard location instead of usual C:{$User}\AppData…

Pattern:

  1. purchased scenery download completes
  2. Decompression starts and
    a. Vienna - CTD after a couple of minutes post start of decompression
    b. Cologn-Bonn - decompression ends, sim freezes and then CTD
  3. After this, when sim is started, it doesn’t even reach the part where it checks for updates and results in CTD

Sim starts only after the packages are removed from OneStore under F:\MSFS\Offocial\OneStore along with the relevant entry from F:\WpSystem\S-1-5-21-3071305499-118537375-3585845107-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\KHE

Created a zendesk almost 10 days back but havent really got a response other than they asking me for my system details.

Hi @xisumervoid,
I’ll give you some advice about how you installed it. When it works, it works. But when it doesn’t it’s difficult.

When you tell the MS Store where to install apps to another location, as you see it creates a system file on that location drive. It puts more files there than if you let it go to C:

I would recommend letting the MS Store use it’s default location on the C: drive and tell the MSFS installer where to put the core files - in your case F:\MSFS This makes a “cleaner install”. The data that will be on C: will be about 8-10GB with the rest in F:\MSFS

It’s also difficult to remove all that WpSystem off your F: without doing an FDISK and then format.

If you want to take that plunge, make sure you first fully uninstall MSFS then change the MS Store back to it’s default. Then format that F: drive to prepare it again for F:\MSFS

@Hester40MT - many thanks, this is the first tangible lead I’ve got after doing tons of things and researching it as well.

So, if I understand correctly, this is what I need to do

  1. Completely uninstall MSFS
  2. Format F drive that holds current packages for removing all WpSystem files
  3. Change the location of Windows store back to C drive
  4. Reinstall MSFS - this time still selecting F:\MSFS for core packages install (Community & Official folders)

And hope it works :slightly_smiling_face:

Hi @xisumervoid!

Before you do the below, make sure MSFS is uninstalled and then change the MS Store back to it’s default location. Then restart your PC.

A little more on the WpSystem folder that is NOT on the C: drive. See this - only follow the instructions for this folder not on the C drive:

1 Like

Will moving the installation to C drive do the trick? Moving via the method provided by Windows going to Add remove programs and taking this as an example, I will obviously move the MFS:
image

You can try that, yes. If it gives a problem, then best to do what I mentioned about uninstalling and reinstalling - using MSFS installer to point to another drive.

You don’t have to install the main core files of MSFS on C: - but the “app” part of it should be on C:. If you have enough space on C: - then go for it! :slight_smile:

Question:
Did you setup MS Store to have ALL apps go to a different drive? If so, change that back to the C: drive.

Yes, I made the MS store install to other drive as my C drive is small 100 Gig SSD and was running out of space due to FSX installation; F drive though is 500 Gig SSD. I guess it is time to remove FSX now that I am fully with MFS :slightly_smiling_face:.

I will point the Windows store back to C along with moving the sim to C via the Add Remove program feature. Thanks!

While researching this, another point that I noted is that a lot of people get CTDs after adding a new scenery from marketplace if that scenery is already in rolling cache. For marketplace downloads it should be possible to clear the downloaded scenery from rolling cache after the new scenery for same region/airport is downloaded and that will probably avoid a lot of CTDs. No?

if you have a line with Asobo, probably this can be highlighted to them. Chances are, they already know this and are working to fix it.

This is actually a Windows issue for some who change the location of the MS Store to go to another location.

What I would do if I were you, since your C: drive is limited space:

Scenario One:

  1. You will need to move all apps the Store has installed to your F: - back to C:
  2. Change the MS Store app to point back to C:
  3. Uninstall MSFS
  4. Difficult one… make sure all apps/programs are off of you F: - then format that one
    (If you don’t get every MS Store app moved from there, Windows will give an error on next restart)

Scenario Two:

  1. Leave all your existing MS Store apps on F:
  2. Change the MS Store app to point back to C: (for new apps)
  3. Uninstall MSFS

To have MSFS installed on your F:

  1. Download from MS Store as usual - this time it should go to C: as you’ve changed the MS Store location.
  2. Launch MSFS and the installer will give an option where to put the files. This time choose F:\MSFS (create this folder before you launch)

To have MSFS installed on your C (default):

  1. Download from MS Store as usual - this time it should go to C: as you’ve changed the MS Store location.
  2. Launch MSFS and the installer will default to the C: drive

There will be files on your C: (about 8-10GB) but the rest of MSFS will be on F: (including the Community folder which now not have all that Windows 10 app permissions).

Am I now really confusing you? :crazy_face:

So not uninstalling is not an option? :neutral_face:

it is an agonizing 3-4 hour process for me and was hoping that I didn’t have to do it. I have 2-3 3p addons as well that will have to be reinstalled and one of them is almost 5 Gb install that downloads content at the time of installation :frowning:

Am I now really confusing you?

Not at all - this is by far the best leads I’ve got; keep it coming :slight_smile:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.