Hi,

my last session ended normally, but today I ran into problems. First, MSFS crashed while half way through loading the initial screen. When I tried again, I got the Blue Screen Of Death, telling me that "something went wrong": After restart, MSFS wants to re-install itself, all 130GB of it! 

My Steam installation is in D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator but for MSFS installatin path I chose D:\FS2020 - all stuff is in there, the Community and Official folders among other stuff. But now MSFS wants to install "packages" in C:\Users\MyUserName\AppData\Roaming\Microsoft Flight Simulator\Packages

Is this correct or should I change it to D:\FS2020? I'd say change it, but just to be sure.... what are "packages" anyway?

Thank you in advance! 🙂

Jure

I am quite sure you should point that to D:\FS2020. MSFS should then detect that it doesn't need to download those 130GB's.
If possible it might not hurt to make a copy of that folder and keep it safe in case something gets corrupted in there. It might save you future downloads.

This is now a post SU13 issue for me, randomly at launch the sim will want to install packages as if there's an update.

Pushing install will simply do a query to the patch/dlc servers and carry on with launching the sim normally....BUT BE PREPARED TO HAVE YOUR GRAPHICS SETTINGS ERASED AND RESET EVERY TIME THIS HAPPENS!!!!!😡

Luckily it's only the graphics tab that gets reset to default for me and not everything in options.

Edited October 22, 20232 yr by blueshark747

1 hour ago, orchestra_nl said:

I am quite sure you should point that to D:\FS2020. MSFS should then detect that it doesn't need to download those 130GB's.
If possible it might not hurt to make a copy of that folder and keep it safe in case something gets corrupted in there. It might save you future downloads.

Agree. 🙂

Thank you all for responding!

I noticed that in userCfg.opt the path was changed to C:\Users\MyUserName\AppData\Roaming\Microsoft Flight Simulator\Packages and after changing it back to d:\FS2020 sim started without updating. And crashed.

I have a much bigger problem, after all sorts of checks and head banging I am now running MemTest86 and it turns out I have either bad RAM or motherboard. Half way through the test already over 8000 errors reported. The PC is not even one year old! Happy days ahead... 😒

Are you using 4 sticks of RAM? Although most motherboards have 4 memory slots it is often less stable than using just 2 slots.
Also, if you have turned on XMP try it with it turned off and/or use more relaxed memory timings. It could be your RAM is pushed beyond stable settings. To get the memory running stable ad advertised speeds often requires a bit of tweaking, and sometimes it just won't work at those speeds on a specific hardware combination.

Especially if the memory modules are not on the QVL on the motherboard's manufacturers website it can be a hit or miss.

No, two 16Gb Kingston Fury DDR5 sticks on a MAG B650 Tomahawk, no XMP. Seated in slots 2 and 4 as recommended. I resolved the issue yesterday late in the evening after testing each stick separately for most of the day. Successfully, too. It turned out that one of the sticks was not seated properly! How is that possible is beyond me, really. I just hope this was the real cause and there isn't something else lurking in the shadows! 🤨

MSFS settings were reset, path was changed in UserCfg.opt as I wrote before but that can all be set up again. I'll test run the sim today and push it a bit. So far, so good.

I assume I can now delete the few downloaded Gb in C:\Users\MyUserName\AppData\Roaming\Microsoft Flight Simulator\Packages?

 

51 minutes ago, Jure said:

I assume I can now delete the few downloaded Gb in C:\Users\MyUserName\AppData\Roaming\Microsoft Flight Simulator\Packages?

After you get it to start up correctly... yes.

Reminds me. I bought two 16GB sticks of ram to replace my two 8GB sticks. When I put them in only one stick was seen by windows. I had to keep removing and putting those same two new sticks back in. Eventually all was well and correct.

So I guess sometimes its hard to get the RAM sticks in just exactly right. (I had to hold the sticks with 3 fingers to apply pressure on the sticks in 3 places to get them to seat correctly where windows could see them). That was 2 or 3 weeks ago and all has been well since.