2 minutes ago, captain420 said:

So I do not need to reinstall MSFS at all then? I really hope it's as easy as that! That will save me so much time and trouble!

No you do not.

I edited the reply to show a possible way to change the location "in game" though I have not tried doing it that way.

Thanks for that! You saved me from having to reinstall the entire game!

Thinking "aloud" and sharing this with more knowledgeable simmers: when we install MSFS on a drive different to "C", say "E", MSFS will anyway automatically create a set of folders on "C" under: User>Name>AppData>Local>Packages>MicrosoftFlightSimulator_8wekybxxxxx>LocalCache>Packages>Community which are duplicates (with links not the actual files) to those installed on the "E" drive with MSFS which is as follows:

E:\WpSystem\S-1-5-21-2664669059-4195190780-4106683977-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages

Would it be possible to make use of this Community folder located on "C" rather than the one on "E", in other words point AddOn Linker to this "C" community folder instead?

The advantage would be that in some rare cases, add-ons would refuse to install on the "E" Community folder because the path is too long (180 characters), whereas the "C" Community path would be shorter. For example the PMDG livery installer refuses to work with my "E" Community folder for that very reason and no DC6 liveries would install.

What are your thoughts?

Edited August 18, 20214 yr by Bernard Ducret

1 hour ago, Bernard Ducret said:

Thinking "aloud" and sharing this with more knowledgeable simmers: when we install MSFS on a drive different to "C", say "E", MSFS will anyway automatically create a set of folders on "C" under: User>Name>AppData>Local>Packages>MicrosoftFlightSimulator_8wekybxxxxx>LocalCache>Packages>Community which are duplicates (with links not the actual files) to those installed on the "E" drive with MSFS which is as follows:

E:\WpSystem\S-1-5-21-2664669059-4195190780-4106683977-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages

Would it be possible to make use of this Community folder located on "C" rather than the one on "E", in other words point AddOn Linker to this "C" community folder instead?

The advantage would be that in some rare cases, add-ons would refuse to install on the "E" Community folder because the path is too long (180 characters), whereas the "C" Community path would be shorter. For example the PMDG livery installer refuses to work with my "E" Community folder for that very reason and no DC6 liveries would install.

What are your thoughts?

be  interesting  to  find  out  since i   did  just  that  with  steam  version installed  to  a  different  drive   now  i got  2  community folders  one  being  in c  drive under packages  which has  nothing in it  and  the  other  one  is  installed  on my  other  drive  which has msfs installed  has  all the  mods etc  pmdg  dc6  etc

I tried what I explained in my post above and everything seems to work properly.

I de-linked ALL my add-ons from the Community folder with Add-on Linker (only one click!), ignored the only remaining package (PMDG DC6) and left it there, opened and edited the last line of the UserCfg.opt file to create the path to the default C drive, changed the path to the Community folder on C in the settings of Add-on Linker, re-linked all my add-ons (one click!), and launched MSFS. Bottom line all my PMDG DC6 liveries can now be downloaded and installed and no more installation failure due to long paths. My MSFS remains installed on E and so does my Add-on folder, so C only has links in the "new" Community folder.