I've used FFS Free until yesterday, when I updated from 9.1 to 9.5.
I received the following error:
FFS_1.jpg (28.4 KiB) Viewed 2847 times
A later start brings:
FFS_2.jpg (17.84 KiB) Viewed 2847 times
I've disabled the AVG Antivirus while the setup, but the error is the same.
Setup an old V9.4: Same problem.
And also my old setupfile V9.1, that works until the update yesterday, now shows the same error !
You simply could have right-clicked in Explorer, but sigcheck is fine. The signatures seem to be broken in your screenshots: They are not "verified" and do not show a "publisher".
Maybe the installer really *is* corrupt due to a download error? Can you post a checksum of the installer (whatever you can generate).
How are you downloading them? Are you using a 3rd party download tool? Did you try to download the installer using another browser? Chrome, IE, Edge or Firefox?
How are you downloading them? Are you using a 3rd party download tool? Did you try to download the installer using another browser? Chrome, IE, Edge or Firefox?
shai, 29 Nov 2017, 17:56
This could be worthwhile to check! Browsers have the tendency (especially IE) to add alternate data streams to downloaded executables in order to mark them as unsafe. Can you make a copy of the installer (= please preserve the test case) and then run "streams -d" on the copy (this is another Sysinternals tool) to remove the ADS.
It may be a bit of a long shot, but I see no reason why the 32-bit sigcheck should fail, unless the OS is damaged in some way. It would be worthwhile to check it for errors (and repair them) via
I can't help but go back to the OP's original post saying:
I've disabled the AVG Antivirus while the setup, but the error is the same.
Setup an old V9.4: Same problem.
And also my old setupfile V9.1, that works until the update yesterday, now shows the same error !
Which basically says, that even installers that used to work on his OS, now don't. I'm suggesting this could be an issue with the OS or another software that is causing this issue. Even AVG at disabled status, could still be causing issues.
Micha,
Would you be willing to remove temporally the AV or any 3rd party FW (no the Windows one) that you might have to for the sake of this test? Don't forget to restart Windows if you do before you try again.
Okay, so the fact that 32-bit sigcheck fails even for Microsoft-signed executables shows this issue is not related to FreeFileSync. In your "dism" screenshot I'm seeing you're running an older version of Windows 10. Try updating to the latest one, which should print "10.0.16299.64".
I'm sorry we weren't more of a help to you. At least you might have some direction and I would love it if you get a resolution, that you come back here and say what it was.
Also, I personally had an issue with downloading and applying the latest update to Windows 10. I hopped on their online chat and their tech. took control of the PC and went ahead and manually downloaded their update, and manually had it installed and that was the end of it. They were very technical and knew exactly what to do.
The latest Win10 is not distributed to my notebook via update. Maybe a hardware/driver incompatility.
I don't want to force the upgrade !
Micha_he, 29 Nov 2017, 22:36
Are you sure? Microsofts concept is to roll out major Windows 10 updates more often, thererby letting the old revisions to go out of support sooner. So if MS really decided to stop providing updates to your laptop, you'd be out of the official support cycle, mayber after a year already.
Perhaps this "hardware/driver incompatibility" is also related to the sigcheck issue.
Why not do it here and help to find the cause? The fact that the issue is not related to FreeFileSync does not imply that FFS will not or should not implement a work around if one exists. It all depends on what the actual culprit is. Currently if you're not able to update to the latest Win 10, this is an even bigger issue.
I'm not give up yet! But the Win10 notebook of my wife, is also a 1607 and there isn't a problem with SigCheck.exe. So the reason must be in my (pretty normal) installation.
Maybe a problem with the Windows "Certificate Root Store". But I didn't found a solution to check/repair it...
The function, which Windows is use to verify the signature, is a part from the 'WinTrust.dll'.
Thanks to autoitscript.com-forum for the info.
The registration of the dll was broken and I fixed him as follow:
- Open a commandline as admin
- Execute "C:\Windows\SysWOW64\regsvr32.exe /u wintrust.dll" (Path ...\SysWOW64\.. is important, because with me the x32-subsystem-dll is broken !)
- Reboot system
- Open the commandline as admin again
- Execute "C:\Windows\SysWOW64\regsvr32.exe wintrust.dll" (a second reboot was not necessary for me)
