FreeFileSync Forum

VMWare workstation 16.2.3 no longer has this issue.

Thank you for your support.

Unchecking the Read-Only attributes on these files allows FFS to sync without failures when syncing from the VM client to the host.

Note that the read only attribute on the NAS, to which syncing proceeded without failures is also checked.

So, somehow, with the change of VM (possibly 12.0 to 12.1 ...

Of course, an attribute that gets copied. Makes sense. So FFS has a file to delete. It has to flip it's RO attribute and then delete it. Does the log show what is the reason for denying access to the file? Is it the RO attribute?

Tools -> Options show:
[x] file-safe file copy
[ ] Copy locked files
[ ] Copy DACL, SACL, Owner Group

... looking at the last sync read-only is checked on the pack-... file that causes access-denied.

So it looks like the permissions do get copied, right?

I looked at Options, Sync Options (F8), and web Manual -- could you please point me to where I can see this 'preserve permissions' option?

The files that fail to synchronize are marked as Read Only on the source side. Once synchronized to a new target, these files still are marked read only. On a sync that attempts to delete such files, FFS reports 'Access Denied'. After closing FFS, opening it and selecting 'Show in Explorer' a file ...

- I do not see this issue when synching onto a Synology NAS.
- I still see this issue when syncing from a VMWARE Workstation to the host (Windows 10).
- I am fairly confident that the issue, which I reported on December 21, did not exist before October 2021.
- So, if this issue is due to a ...

search for my\ the repo is in my\solution. same issue. but focusing on a single repo hopefully making this easier. thanks you!

zipped file too big to upload. I posted it on Google Drive; https://drive.google.com/file/d/1TQTFT1-wlyITJ2U-J4DALosou_oDjSIl/view?usp=sharing

I synced as follows:
(1) commit;
(2) waited about 30 minutes;
(3) ran a sync on a subfolder (e.g., trash) of the main folder (c:\my) to test a sync using the same top folder; success;
(4) ran a second sync on the same folder for deleting some files on the target folder; success;
(5) ran a sync of c ...

I too was wondering about the timing issue and tried to wait a bit before syncing. Waiting did not seem to make a difference. I also ran the successful second attempt to commit almost immediately, which seems to suggest looking at FFS rather than GIT. I am still not fully committed (pan not intended ...

Sure. I can do that. What do u suggest?

For example, say I have committed some files to the repo. Now I have some data to sync, which include, among others, some files from the .git\objects folder that cause the Access Denied failure. When I sync, all files sync, including copy and delete, except ...

I am not seeing any Windows events that I can relate to this behavior.

I am now on version 11.15 (donation edition). This report was generated with version 11.14. The issue is still present in version 11.15.

I am seeing access deny errors with FFS.

I attached a series of screen shots that I hope show how this manifests itself when synching with Free File Sync (FFS ...