FreeFileSync Forum

Well, I was talking about this workaround , and that has very little, or nothing to do with PortableApps.
It's a simple trick volpoca posted to the PortableApps.com forums back in January 2015. And that pudah already posted within this thread in April of 2015 . It's an old approach that doesn't ...

For completeness, it should be called volpoca's solution since he posted it here in January 2015: http://portableapps.com/comment/220608#comment-220608

Not sure why others are taking credit for the approach.

This may or may not be a contributing factor to the longstanding bug preventing FreeFileSync from being launched from other processes that remain running: BUG: Starting FreeFileSync.exe from another process yields Error Code 32 (07 Mar 2014)

In additional testing, it seems that it is indeed the FreeFileSync.exe and FreeFileSync_x86/x64.exe processes that are stepping on each other with locking the options file. This continues to happen when launched from a parent process that remains running (portable menu, portable file manager, 3rd ...

When FreeFileSync is run in portable mode and moved from one location to another, the setting to automatically check for updates under the Help menu is reset to the default: Check Weekly. If you uncheck Check Weekly and then move paths, it is reset to Check Weekly and a check for a new version is ...

Wylie: We tried that method at PortableApps.com soon after the bug presented 2 years ago. The standard ways to break out of process are either `start "" "FreeFileSync.exe"` or `cmd /c start "" "FreeFileSync.exe"`. We've found this technique to be only partially effective in neutralizing the bug. On ...

FreeFileSync 7.9 is still affected by this bug. The location of this bug report is now directly linked from the app pages for FreeFileSync on PortableApps.com and PortableFreeware.com.

This bug still persists in FreeFileSync 7.8. The bug is now 22 months old. Complete details on how to reproduce it along with source code and a stub launcher to do so were provided 11 months ago.

If you'd like to use FreeFileSync with a start menu of your choice, a file manager of your choice, or ...

This bug still persists in 7.6. I have complete details to reproduce in the report from 9 months ago: https://freefilesync.org/forum/viewtopic.php?t=1716&p=6995#p6995

This bug is now 20 months old and still doesn't allow FreeFileSync to be launched from 3rd party file managers, menus, and other ...

Attempting to run FreeFileSync.exe from another process on Windows yields the following error:

---------------------------
FreeFileSync - An exception occurred
---------------------------
Cannot open file "GlobalSettings.xml".

Error Code 32: The process cannot access the file because it is being ...

Do the programs you are starting ffs from allow to provide a working folder?
Maybe thats a difference?echtatze

Setting a working folder has no affect.

As a random C programmer: it sounds like FreeFileSync.exe is keeping the file handle open while launching the bin/FreeFileSync_Win32.exe / bin/FreeFileSync_x64.exe. If the launcher manages to quit before the main exe accesses the file, it works, otherwise not.

It sounds a bit wonky that how the ...

The bug is still present in FreeFileSync 7.0.

Regarding your statement: "The bug seems to occur when the Windows process that runs FreeFileSync.exe remains running. If the process exits immediately after running FreeFileSync.exe, the bug does not seem to occur occur."

I presume you've tried creating an exe that launches FFS then exits ...

so far it seems this problem is only occurring in the context of PortableApps and not when starting normally from Windows Explorer. Most likely it is caused by some conflict with the PA configuration handling on startup that makes applications portable.Zenju

so far it seems this problem is only occurring in the context of PortableApps and not when starting normally from Windows Explorer. Most likely it is caused by some conflict with the PA configuration handling on startup that makes applications portable.
Hi Zenju. I've been looking at this bug for ...

FreeFileSync 6.11 fails about 1/2 the time when launched from another EXE. There doesn't appear to be any rhyme or reason to why it fails some times but not others.

Yes, this affects the app in 'installed' mode as well as portable. So, you can't run it from anything else except Explorer or the Windows Start/Tile Menu.

If it helps at all, the error is occurring within freefilesync.exe. Substituting that file from 6.2 into 6.3 fixes the error. So the error is in the code of this 'shortcut' exe instead of within the main EXEs that it calls within Bin.

This bug is still present in FreeFileSync 6.9. Anyone more versed in C++ than me care to take a stab at examining the DIFF between FFS 6.2 and 6.3 and determine how the bug was introduced?

I did a quick skim of the diff between 6.2 and 6.3 and nothing jumped out at me. Granted, I haven't determined where in the code this error is being thrown incorrectly. Perhaps someone with better C++ chops could take a look or the author could point us to where this invalid error is being thrown ...

This bug is still present in FreeFileSync 6.7. The app simply can not be run from other menus, scheduling apps, etc.

The issue persists in FFS 6.6. Starting FreeFileSync.exe via another process still produces the above error, so it can only be started via Windows Explorer, a shortcut, command line, or a batch file.

This issue persists in FreeFileSync 6.5. Downloading the official Windows installer from here and installing in portable mode. When attempting to run it from the PortableApps.com Menu, we still get Error Code 32. FFS in portable mode still can't be launched from an external EXE (an app launcher, a ...

The error still occurs in 6.5 beta when run within the FFS Portable PA.c Format package or when a standard portable install directly from the 6.5 beta installer is run from the PA.c Platform's menu. Same error as reported above.

This bug is still present in the 6.4 release.

Attempting to run FreeFileSync.exe from another process on Windows yields the following error:

---------------------------
FreeFileSync - An exception occurred
---------------------------
Cannot open file "GlobalSettings.xml".

Error Code 32: The process cannot access the file because it is being ...

FreeFileSync Forum

Search found 27 matches

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: FreeFileSync forgets automatic update setting on path change

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

BUG: FreeFileSync forgets automatic update setting on path change

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

FreeFileSync 7.9 Still Affected By This Bug

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

Re: BUG: Starting FreeFileSync.exe from another process yields Error Code 32

BUG: Starting FreeFileSync.exe from another process yields Error Code 32