Hi.
This is my first problem since I started using FFS many years ago - so it is my debut in this forum. I love the software and use it daily.
Out of nowhere, I suddenly get this message every time I want to syncronize:
"Waiting while directory is in use "U:\XXXXXX\sync.fss.lock" - Username: Franke - Lockfile apperantly abandoned.... 21 sec (and then it's counting down).
I have no idea what is happening - it is just pretty annoying.
I have a Desktop computer with these specs:
Motherboard: ASUS TUF GAMING X570-PLUS (WI-FI) ATX AM4 AM
ASUS GeForce RTX 4070 DUAL EVO D6 OC - 12GB GDDR6 RAM
AMD Ryzen 9 5950X CPU
1x 3200 128GB Kingston FURY Beast KIT (4x 32GB)
WD Black SN850 NVMe SSD SSD WDS100T1XHE 1TB
WD Black SN850 NVMe SSD SSD WDS200T1XHE 2TB
6 SATA IronWolf Pro discs
Operating system: Win11 - latest version.
I am not an IT professional, just saying ;-)
Help wanted! ('Waiting while directory is in use.....')
- Posts: 1
- Joined: 26 Jul 2025
- Attachments
-
- Freefile!.png (4.75 KiB) Viewed 261 times
-
- Posts: 2978
- Joined: 22 Aug 2012
By default, FFS writes a sync.ffs_lock file in each of the left and right base locations involved in a sync. Read why in the description for the LockDirectoriesDuringSync flag.
An FFS sync that closes in a regular fashion (is e.g. not killed by a restart or via the Task Manager) removes those sync.ffs_lock files, effectively releasing those locations for other FFS syncs.
Check if, as the "apparently abandoned" text suggests, there is no other FFS sync active involving one or more of base locations of your active sync (e.g. in your Task Manager). If there still is such an FFS job, kill it. There may be an FFS sync job, launched via the Task Scheduler or via the Autostart folder, still wating to be closed.
An FFS sync that closes in a regular fashion (is e.g. not killed by a restart or via the Task Manager) removes those sync.ffs_lock files, effectively releasing those locations for other FFS syncs.
Check if, as the "apparently abandoned" text suggests, there is no other FFS sync active involving one or more of base locations of your active sync (e.g. in your Task Manager). If there still is such an FFS job, kill it. There may be an FFS sync job, launched via the Task Scheduler or via the Autostart folder, still wating to be closed.
