8.10 doesn't work

[eswno]

Get an error:

freefilesync.PNG (51.23 KiB) Viewed 6131 times

Reinstall, reboot Windows doesn't solve the issue.
What's the problem?

[Zenju]

Are there any error messages during installation?

[eswno]

Are there any error messages during installation?

no error during installation.

[Zenju]

Did you confirm/close the installation dialog before starting FFS?

[eswno]

Did you confirm/close the installation dialog before starting FFS?

Yes

[Zenju]

Maybe some AV/firewall software is interfering with the installation or the start up?

[ahmad_511]

Maybe some AV/firewall software is interfering with the installation or the start up?

Hello there,
I also have problem with this version and I can confirm that Avira anti-virus suspected the installer and moved it to the quarantine folder

I hope you can find what causes this
Regards

[eswno]

Maybe some AV/firewall software is interfering with the installation or the start up?

The Windows default AV/firewall is used.
I uninstalled and re-install it, the error message became

1.PNG (34.66 KiB) Viewed 5940 times

There is no install.dat file in that folder, I copied a previous install.dat to the folder, the error is

2.PNG (12.45 KiB) Viewed 5940 times

Does it help you to figure our the issue? It seems with the install.dat file.

[Zenju]

The Windows default AV/firewall is used.

Good.

There is no install.dat file in that folder

In this case something went wrong during installation. If no error message is shown, can you send me a Process Monitor log of the installation procedure? That should allow to identify the problem.
https://freefilesync.org/faq.php#trace

[eswno]

There is no install.dat file in that folder

In this case something went wrong during installation. If no error message is shown, can you send me a Process Monitor log of the installation procedure? That should allow to identify the problem.
https://freefilesync.org/faq.php#trace
[/quote]

Sent, please check..

[Zenju]

The log is strange: After installation when you close the dialog, it starts up FreeFileSync_XP.exe, but it never terminates. Either your log is incomplete and you ended the logging before this process ran through, or perhaps the process crashed?

[eswno]

The log is strange: After installation when you close the dialog, it starts up FreeFileSync_XP.exe, but it never terminates. Either your log is incomplete and you ended the logging before this process ran through, or perhaps the process crashed?

I am not familiar with Process Monitor, just followed your steps, not sure what was wrong. I found another error message in several minutes after installation.

Capture.PNG (38.58 KiB) Viewed 5716 times

Is this the root cause?

[Zenju]

This is another symptom that probably has the same cause. I don't have an explanation for this error other than something is going wrong at the system level. I had another look at the trace file and noticed countless small invokations like:

\??\C:\Windows\system32\conhost.exe "41751736-1968510037-177866972610047163482351840481786327802-1791147722-1662454018"


This itself is very dubious. Further, matching these calls there are pairs of short "cmd.exe/text_extractor_host.exe" calls originating from Chrome:

C:\Windows\system32\cmd.exe /c "C:\Users\yinghx\AppData\Local\Youdao\Dict\Application\stable\text_extractor_host.exe" chrome-extension://aohddidmgooofkgohkbkaohadkolgejj/ --parent-window=0 < \\.\pipe\chrome.nativeMessaging.in.598325e9f3826423 > \\.\pipe\chrome.nativeMessaging.out.598325e9f3826423
Current directory:


One, maybe not too far-fetched theory is that this Chrome extension "Youdao" is messing with the OS in a way so that a basic system call like "Process32Next" would fail. Process32Next is listing processes and "Youdao" is creating a massive amount of them, so there seems to be the connection.
This would also explain why the FFS installation fails: One feature of the installer is to kill running FFS processes so that upgrading works while FFS is running. In your case however this kill processes is "delayed" so that it turns against the FFS routine itself, preventing the completion of the installation. From the trace I see that what should be a synchronous call, still continues to run, or more clearly hangs, although it (should have) already finished when the installer continues execution. This process internally also uses Process32Next-like calls, therefore both symptoms have the same cause. So let's test the theory:
Disable or uninstall/delete "Youdao" and see if FFS can then be installed correctly.

If this doesn't work, can you send me another trace file? Just start monitoring before starting the installer and end it after closing it in order to keep the trace size small.

[jake7]

I got same issue when instaling FFS 9.0 on windows 7 64bit.

FreeFileSync.png (24.19 KiB) Viewed 5099 times

Base on trace log on installation also FreeFileSync_XP.exe starts up.
Installation dialog says that process completed successfully but when I try to start FFS I got another error:

FreeFileSync1.png (10.24 KiB) Viewed 5099 times

I have same version on Windows 10 64bit and there was no issue.

[eswno]

Seems the error code 122 issue still not resolved. I will sent a new trace file.

[Zenju]

I assume the trace you sent me corresponds to viewtopic.php?t=4956
i.e. error 122 (ERROR_INSUFFICIENT_BUFFER) for Process32Next.
I'm seeing a second run of FreeFileSync.exe after installation, which I assume was just a manual test, even though installation clearly failed.

First, let's make sure the error is not caused by a general system corruption. From the command line run:

Dism /Online /Cleanup-Image /RestoreHealth


This one in addition won't hurt:

sfc /scannow


In the trace I'm seeing "Verdasys Dgagent" being injected into the FreeFileSync executable. Are you able to disable this program and see if installation works then?

[eswno]

I have run the commands, no issue found

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

I don't know what the 'Verdasys Dgagent' is, cannot find it from process list or hard drive. I tried to enter Windows safe mode and install the FressFileSync, the same error encountered.

[Zenju]

I don't know what the 'Verdasys Dgagent' is, cannot find it from process list or hard drive.

There are multiple entries:

Verdasys.png (13.57 KiB) Viewed 4297 times

[eswno]

Interesting! I don't see the DGAgent folder at all. I have set to show hidden and system items, still don't see this folder.

f.JPG (17.34 KiB) Viewed 4278 times

[Zenju]

The folder is probably hidden via NTFS permisisons. Dgagent is running on your system as a service.

[eswno]

I don't find DGAgent or Verdasys in the services list either, so I don't think I can do any with this service. But why the v9.6 was installed and worked well? The error occurred when it was upgraded to v9.7. I cannot uninstall FFS from my computer either, got following error when uninstall it.

FFS uninstall.JPG (28.37 KiB) Viewed 4262 times

[KC23]

I just want to uninstall 9.7 and I'm getting the same error.

FreeFile.jpg (290.95 KiB) Viewed 4223 times

The uninstall is effectively blocked.
Running Windows 10

[Zenju]

I just want to uninstall 9.7 and I'm getting the same error.

This has been fixed for the next version.

[eswno]

The version 9.8 has the same issue.

FreeFileSync.JPG (29.24 KiB) Viewed 4008 times

My harddrive is BitLocker encrypted, may this be the cause? I don't see my system has any other difference from a normal system.

[Zenju]

I would check if disabling the Dgagent service might fix this issue.