-
Notifications
You must be signed in to change notification settings - Fork 281
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
Windows 11 - Folders created as Junction are not synced #1000
Comments
symlinks are intentionally ignored by megasync due to technical reasons (you can see discussions here #159)
the correct way of doing this is settings - sync - add - choose local folder as whatever destination need to be synced. |
Thank you @cihe13375
... see the screenshot, we can't choose (click & select) a Folder and we can't click the [OK] button. |
If a folder is gray (and cannot be selected) it means that folder is already connected to another local folder (it does not make sense to connect two different local folders to the same online folder). A new online folder is required for every "add" operation. If you still have issues, I suggest contact mega support in case you actually ran into bugs (I'm not mega stuff). |
Hi @cihe13375 The problem persists. |
oh I misread your image above. I think the problem is that you have a local folder connected to |
Hi,
I'm using MEGAsync ver. 5.4.1 on Windows 11 Pro 23H2 (64 bit).
There is no issue with syncing standard Folders and Files.
The issue is with Folders created as Junction with the command
mklink /J
- for examplemklink /J "C:\[DEST_Megasync_DIR]" "C:\[Source_Disk_DIR]"
- this kind of folder is not synced at all. (tested on 2 computers)
Other software works with this kind of Folders and are supported by the OS, too.
It is very important to allow syncyng this kind of folders, because it opens possibility to sync projects, drafts or config files that have hard-coded destination in other software.
Thank you Guys.
The text was updated successfully, but these errors were encountered: