Hi Zenju,
Sorry, I may be misleading you...the "xxx" in the Lock Owner is my login account.
Anyway, after stopping the schedule and killing all FreeFileSync services with sysinternal's procexp and restarting the schedule it seems to be running fine.
--
Just a note on what I'm doing which is using ...
Search found 2 matches
- 02 Jul 2018, 08:35
- Forum: Help
- Topic: sync.ffs_lock being created despite <LockDirectoriesDuringSync Enabled="false"/>
- Replies: 5
- Views: 2150
- 02 Jul 2018, 03:55
- Forum: Help
- Topic: sync.ffs_lock being created despite <LockDirectoriesDuringSync Enabled="false"/>
- Replies: 5
- Views: 2150
Re: sync.ffs_lock being created despite <LockDirectoriesDuringSync Enabled="false"/>
Hello, I also have this problem now. All scheduled sync jobs hang (Windows 10) "Waiting while directory is locked:"directory path\sync.ffs.lock" | Lock owner: xxx
Hope someone can help us?
--
FreeFileSync 10.1 Build: 06/03/18 - Unicode x64
Hope someone can help us?
--
FreeFileSync 10.1 Build: 06/03/18 - Unicode x64