[Solved] FreeCommander XE - Wrong Version detected after Update to 2019 release 790 Donor

OLLI_S

Today I installed an update for FreeCommander XE (new version 2019 release 790 donor) but VulnDetect does not detect the installed version (version 2019 release 790 public is shown)!
So you detect public although I have donor installed.
In the Configuration of VulnDetect I see: Last Inspection 35 minutes ago.

Here the information extracted from the EXE file:

File name and path:     C:\Program Files\FreeCommander XE\FreeCommander.exe
Product Name:           FreeCommander XE
Internal Name:          
Original Filename:      

File Description:       FreeCommander (x64) - file manager for Windows
Company:                Marek Jasinski
Legal Copyright:        www.freecommander.com
Legal Trademarks:       
Comments:               

File Version String:    2019.0.0.790
File Version:           2019.0.0.790
Product Version String: 2019.0.0.790
Product Version:        2019.0.0.790

Tom

See my response here:
https://vulndetect.org/topic/552/freecommander-version-number

I'm afraid we can't do much, unless you can suggest an alternative way of detecting the difference.

OLLI_S

If you can detect x64 then you have the difference.
On the official download page: https://freecommander.com/en/downloads/
It says: FreeCommander XE 64-bit is currently available as bonus for the donors.

OLLI_S

@Tom How are you going to fix this issue?
Are you waiting for the Registry detection?

Tom

@OLLI_S There is no useful information in the Uninstall in the registry.
So we will continue to detect in the usual manner, except, a 64bit executable is assumed to be Donor and the 64bit will now bundle the 32bit.

OLLI_S

@Tom said in FreeCommander XE - Wrong Version detected after Update to 2019 release 790 Donor:

a 64bit executable is assumed to be Donor

This is the correct way.
So I mark the issue as solved.