I'm running the latest released version of FreeFileSync x64 ver 8.0 in Windows 7 x64 Home. Every time I log into my normal non-admin user, I get an error message that FreeFileSync can't find a particular file. Using Task Manager I find this error popup window is being generated by csrss.exe, not freefilesync.exe. There is no file by the name of the one listed, but there is a directory by that name. Looking in the Windows Event logs I find an Information event in the Windows-System log that corresponds to the popup window. It contains the following information.
Application popup: FreeFileSync - Error : Cannot find file "F:\Downloads\1Terry\Mozilla".
Log Name: System
Source: Application Popup
Event ID: 26
Level: Information
User: N/A
OpCode:
I only have one FreeFileSync batch that is being run by Task Manager using several triggers, but the files and filters in that batch make no reference to the drive/file/directory as named in the error. This batch file runs fine in Task Manager or when run manually through FreeFileSync and the FreeFileSync log shows successful completion with no errors.
This error started showing right after I upgraded to version 8.0. I've tried uninstalling, rebooting and re-installing FreeFileSync 8.0, but the error hasn't gone away. Any help with this would certainly be appreciated !
Strange FreeFileSync Error Message
- Posts: 2
- Joined: 13 Apr 2016
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
The error message indicates that "F:\Downloads\1Terry\Mozilla" is passed as a command line argument to FreeFileSync.exe.
- Posts: 2
- Joined: 13 Apr 2016
I understand that, but there is absolutely no FreeFileSync task running when this error is generated. That's why it's so puzzling when this phantom error shows up each day at exactly 08:00:00.
I used to have a FreeFileSync batch file that did reference this location, but it was deleted last month when the HDD, where it and the referenced location in the error was located, died. After I replaced the HDD (which I foolishly hadn't backed up), I reorganized all my storage and added a NAS w/RAID to keep everything backed up. I had to build new FreeFileSync batch files from scratch using the newly organized and renamed directories and locations. I also had to delete the old FreeFileSync task from Task Manager and build a new one using the newly created FreeFileSync batch file. Using Windows Explorer search field, I've searched every HDD and the only FreeFileSync batch files are the newly created ones. I've also carefully looked at every task in Task Manager, but the only ones involving FreeFileSync are the two newly created ones and they both reference only the newly created batch files.
This is like 'Groundhog Day', where no matter what I do, I get the same error at the same time every day.
I used to have a FreeFileSync batch file that did reference this location, but it was deleted last month when the HDD, where it and the referenced location in the error was located, died. After I replaced the HDD (which I foolishly hadn't backed up), I reorganized all my storage and added a NAS w/RAID to keep everything backed up. I had to build new FreeFileSync batch files from scratch using the newly organized and renamed directories and locations. I also had to delete the old FreeFileSync task from Task Manager and build a new one using the newly created FreeFileSync batch file. Using Windows Explorer search field, I've searched every HDD and the only FreeFileSync batch files are the newly created ones. I've also carefully looked at every task in Task Manager, but the only ones involving FreeFileSync are the two newly created ones and they both reference only the newly created batch files.
This is like 'Groundhog Day', where no matter what I do, I get the same error at the same time every day.
- Site Admin
- Posts: 7282
- Joined: 9 Dec 2007
There is verly likely some remnant task scheduler entry somewhere that is starting FreeFileSync, so I'd start investigation in this area. Next time the error message comes up have a look at all currently running tasks.