Hello,
As everybody I dropped mod folders into the Community folder.
Problem : when I want to move them back to another disk, I get a message saying that I am not authorized to put this file here !
How can I do it anyway ? (It is MY FILES I dropped in Community !!!)
Thanks in advance ...
Jacky
 

Did you do an install to custom location? Steam or Store install? I installed store edition to a separate drive, not the system drive, and have no problems moving.

Edited November 1, 20205 yr by desbean

Try:

- booting in save mode (press F8 key when booting and select save mode), until now I didn`t have restrictions when running in that mode

- if the first one is not preferred, open Microsoft Power-Shell and copy the items by using the Move-Item command. It`s pretty easy:

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/move-item?view=powershell-6

altough the latter is not guaranteed to work.

Answer for desbean :
- It is a "Store install"
- I installed to a non-system drive "E:"
But on 😄 I get
C:\Users\<my name>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community with files and folders in GREEN
and on E:\ I get
E:\WpSystem\S-1-5-21-673290489-719407897-4158732954-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community in GREEN as well
 

Answer for BigDee :
Thanks, I'll try this.
I will tell You what hapened 😉
 

@BigDee :
 

Move-Item -Path E:\WpSystem\S-1-5-21-673290489-719407897-4158732954-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\aircraft-dr400-140b -Destination C:\dr400

Only copied forlders without files.
Message for each file :

Move-Item : Le fichier spécifié n’a pas pu être chiffré.
(which means :The file could not be encrypted)
Au caractère Ligne:1 : 1
+ Move-Item -Path E:\WpSystem\S-1-5-21-673290489-719407897-4158732954-1 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (thumbnail_small.JPG:FileInfo) [Move-Item], IOException
    + FullyQualifiedErrorId : MoveFileInfoItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand

Sorry, I have to leave now. I'll be back tuesday morning ...
Jacky

And once you find success I highly recommend you begin to use the freeware "MSFS Add on Linker".  It allows you to save your mods, liveries, and sceneries wherever you want to store them.  It then allows you to manage them, selectively moving only shortcuts to your selections in and out your Community folder.  Works like a charm for me (MS Store MSFS installation) and has enabled me to kiss goodbye the error about file/path names being too long to move or copy.

School may still be out on whether too many Community folder items eat up valuable MSFS memory resources.  With the Linker it is easy to move those folder items in and out at will before a particular flight, moving into Community just those (as shortcuts) you need for the flight.

Seems like encrypted files don`t work. I didn`t knew that. You can add a -Force to the command, like:

"Move-Item -Path E:\WpSystem\S-1-5-21-673290489-719407897-4158732954-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\aircraft-dr400-140b -Destination C:\dr400 -Force"

but the MFS Add-on Linker seems likely a better solution.

11 minutes ago, BigDee said:

but the MFS Add-on Linker seems likely a better solution.

Important to point out after my post above that I do not know if the Add-on Linker can manage the problematic files that are already in the Community folder.  They may first have to be successfully moved to another location.  It is then from those that the linker writes the shortcuts to the Community folder.

You can add or delete the files in the community folder but you cannot copy or move them. The easiest way I use is to simply ZIP or RAR them to a file outside of the folder. Then after verifying that they are there, delete them from Community. Obviously adding them back is no problem

I use Total Commander.

3 minutes ago, vgbaron said:

The easiest way I use is to simply ZIP or RAR them to a file outside of the folder. Then after verifying that they are there, delete them from Community.

Due to the long file/pathname issue with my MS Store installation, I made it a habit to download the addon .zip files to another drive and copy them into Community from there.  That way I always had a backup from the start.  Now with the Add-on LInker I have that folder set and the original downloads both to fall back on.

I believe I had issues attempting to delete a Community folder add on or two when I set up the linker.  So it may not always just be Move or Copy commands that fall under the permissions issues.

Hello everybody !
I'm back home and will study all your answers 🙂
Thanks a lot for these numerous help messages 🙂 !
I'll come back soon to give feedback !
Jacky
 

On 11/1/2020 at 11:15 AM, vgbaron said:

You can add or delete the files in the community folder but you cannot copy or move them. The easiest way I use is to simply ZIP or RAR them to a file outside of the folder. Then after verifying that they are there, delete them from Community. Obviously adding them back is no problem

As an FYI, I've tried that too, but did not work.  I end up with a new folder that's empty.  Strange.  I don't use a lot of mods, so any moving around is minimal, so it's not a huge issue.  It does irritate me that I put a folder somewhere, then my computer decides for me if I can move it or not.....LOL

The actual game program files need to be in E:\wpsystem but your community folder does not.  If you move it somewhere else you can access it easier.

To move your community folder:

1. make a copy of your current packages folder (the one containing your community and official folders) - zip it if encrypted.

2, paste it somewhere else

3. open the following file

C:\Users\YOUR-USER_NAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt in a text editor like notepad.

(do save a backup copy just in case)

4. scroll to the very end and  change InstalledPackagesPath to match the location of the new package directory you copied your files to.

For example the last line of my userCfg.opt now reads:

InstalledPackagesPath "D:\Games\Microsoft\fs2020\localcache\packages" which is the path to the folder my community and official packages live in on my 😧

Edited November 3, 20205 yr by Glenn Fitzpatrick