Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minecraft: Bedrock Edition fails to back up when moved to a secondary drive on Windows 11 Pro. #460

Open
RuiNtD opened this issue Feb 18, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@RuiNtD
Copy link

RuiNtD commented Feb 18, 2025

Ludusavi version

v0.28.0

Operating system

Windows

Installation method

Scoop

Description

I love Windows. :D

When moved to a secondary drive, Minecraft: Bedrock Edition (and likely other Microsoft Store / Xbox games) create symlinks from the original directory (%LocalAppData%\Packages) to <drive>:\WpSystem\<UserSID>\AppData\Local\Packages.

Windows 11 Pro (and probably Win10 Pro) automatically set an advanced attribute to encrypt the files in the new directory, which causes Ludusavi to fail the backup for some reason.

This issue doesn't occur on Windows 11 Home because encryption requires Pro.

Logs

ludusavi_rCURRENT.log

Image

@RuiNtD RuiNtD added the bug Something isn't working label Feb 18, 2025
@mtkennerly
Copy link
Owner

mtkennerly commented Feb 18, 2025

Thanks for reporting this!

I just tested in a Windows 11 Pro virtual machine, where I manually set a folder as encrypted. I was able to back it up successfully in Ludusavi, and the backed up file retained its encrypted status inside of the backup folder. I also tried backing up a symlink to an encrypted folder (via mklink /J), and that worked as well (although the symlink itself can't be set to encrypted - Windows Explorer gives an error if you try).

However, I only tested this with a single drive. Having multiple drives may be an important part of the issue. For example, if I try to manually copy the encrypted folder from the VM into the host machine (via a VirtualBox shared folder), Windows Explorer shows me this:

Image

Granted, that could also be a limitation of how VirtualBox shared folders work, but perhaps there's a similar issue where the encrypted files aren't allowed to be backed up onto a different drive. It might also have something to do with your P drive, if it's using a different file system than your E drive or something (e.g., NTFS vs FAT32 - not sure if that's relevant to how Windows handles this encryption).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants