FreeFileSync Forum

I don't know the specifics of DFS related aspects.
But if using \\mediabase\data\media\video\education\ as your (left or right) root folder is a problem, how about defining \\mediabase\data\media\video\ as your root folder, and use an Include Filter of \education\* (everything in \education ...

> folder's root imposes folder's rights that are not compliant to my use.
What exactly is the issue here?

> Is it possible to 1)
Wouldn't make much sense to store the lock file in any other place: the file
needs to be found by any FFS instance no matter how it is configured.


I'm reviving ...

I have no issue with the way it is being handled. You previously synced Charlie, now you are excluding it, so it doesn't care whether it exists or where it is/isn't. The process you are running looks to be unnecessary


I'm glad you have no issue. This isn't about you. This is about reporting ...

If you exclude "Charlie", it is no longer part of the sync, so it will also not be deleted from your righ side.
This is very useful in cases in which you have (right-side) pre-existing folders that you don't want included in the sync, but don't want to be deleted.
But, in your use-case, if you do ...

Further info:

The only way I know how to solve this is to manually remove "Charlie" from the destination location.
This is easy enough in the above scenario, but can be cumbersome when removing many folders (or nested locations).

Perhaps there is another way in the app to perform what I want that ...

When doing a mirror operation I would expect exclude filter options to "clean-up" the mirrored copy.
For example:

Let's say at Location A, I have the following folders:
- Alpha
- Beta
- Charlie
- Delta

I do a full mirror operation with no exclusions so this structure now exists at Location B.
I ...

Just as a follow-up. This does not appear to be a FFS error, as I continued to get this error on copying outside of FFS. If anyone sees similar you can look at my posts on MS here .

It would have been nice if FFS could have passed along the actual error code of 0x80090006 with the error message as ...

The other problem with this error is that when it pops up, it doesn't bring FFS to the forefront or otherwise notify me of an error. So I think FFS is just working fine in the background copying. It isn't until I toggle over to it that I realize it is hung up for I don't know how many minutes.

Getting this error when copying about 175GB from network to local SD card.
When I click "Retry" the file appears to complete transfer and then I'll get it again on another file within 5-20 minutes.

My guess is either some network transfer issue or my SD card going bad, but I've been doing similar ...