FFS failing to copy locked files (ie. NTUSER.DAT)

Get help for specific problems
Posts: 17
Joined: 30 Mar 2011

drivetheory

Volume Shadow Copy is set to manual and does start when FFS is launched.
also tested with VSS set to auto start, yielded same results
both user1 and user2 are in Administrators security group
User Account control is disabled
OS is Windows 7 Pro SP1 (x64)
FFS -> Options -> "Copy locked files" is checkmarked
FFS in use is 7.7 beta found in another topic when searching for a solution to errors encountered using 7.6



when user1 is logged in, and user2 account is used to backup user1's ntuser.dat FFS log shows the following:
[2:46:18 PM] Error: Cannot read file "C:\Users\user1\NTUSER.DAT".
                    The file is locked by another process:
                    System
when user1 is logged in, and SYSTEM account is used to backup user1's ntuser.dat FFS log shows the following:

[2:48:32 PM] Error: Cannot read file "C:\Users\user1\NTUSER.DAT".
                    The file is locked by another process:
                    System
when user1 is logged in, and user1 account is used to backup user1's ntuser.dat FFS log shows the following:

[2:52:14 PM] Info: Creating file "C:\bkp\2015-11-28 145214\Users\user1\NTUSER.DAT"
any ideas?





also it would be great for the use of %timestamp% in target destination to not generate the error which makes every log file resemble "test-backup 2015-11-28 145214 [Error].log" even if the only error was caused by the %timestamp% variable. (maybe call it a warning instead of an error and remove [Error] from the filename?)
User avatar
Site Admin
Posts: 7170
Joined: 9 Dec 2007

Zenju

Use of VSS by FFS must be activated in global settings first:
https://freefilesync.org/manual.php?topic=volume-shadow-copy
Posts: 17
Joined: 30 Mar 2011

drivetheory

as i stated in my first post, it already is

> FFS -> Options -> "Copy locked files" is checkmarked

EDIT:
however it seems you're not using the system wide %programdata% but instead using the user specific %appdata% path for storing "GlobalSettings.xml". is this going to be corrected in a future release?