ERROR_ACCESS_DENIED: Access is denied. [CreateFile]

[TonyK1321]

Hello - When I run FFS, at the end when it tries to write the log file to:
C:\Program Files\FreeFileSync
I get this message:
ERROR_ACCESS_DENIED: Access is denied. [CreateFile]
I'm running FFS as a user not as an admin. What can I do to allow FFS to write the log file to that location?
Thanks,

[xCSxXenon]

Run as admin or change permissions to that location
Log files don't usually write there though, are you sure you want that?

[TonyK1321]

Thanks. I decided to change the location of the logs to a different sub-dir. It works now.

[Plerry]

By default, the FFS save-location for log-files is C:\Users\[UserName]\AppData\Roaming\FreeFileSync\Logs
So, you must have changed that previously.

[Zenju]

He probably extracted the "portable" installation into C:\Program Files\FreeFileSync

[Pinciano]

Problem solved:

I run my FreeFileSync in a Windows 11 machine and I´ve been dealing with this ERROR_ACCESS_DENIED problem bc i changed the letter of the disk where FFS was installed.

Long story short: Don´t open the FreeFileSync.exe file: instead go to the bin directory and execute FreeFileSync_x64.exe.

[therube]

@P, while that may have worked around your issue, I would think that is not the correct way to go around it.

Also thinking that your issue was not ? dealing with the writing of the .log file?
If it did, that would mean that \Program Files\FreeFileSync\ was a "protected" place, where \Program Files\FreeFileSync\bin\ was not - which wouldn't make sense (IMO).

(There could ? also be other potential gotcha's to running x64.exe directly ?)


So if FFS were installed into C:\Program Files\FreeFileSync, & you thru a new "C:" drive in there, & moved/renamed the old to D: (or whatever), & changed your desktop shortcut to point to D:\Program Files\FreeFileSync... not sure why that should affect things, necessarily? (Anything that dealt with the Windows Registry, sure.)

[Pinciano]

That was not the issue. If FFS is installed into C:\Program Files\FreeFileSync, and I executed the direct access from the desktop (I suppose it is the 32 version) , ffs can’t create any file in my computer. I checked it and only if I run the 64 version I don’t have any problem.