<![CDATA[[Solved] FreeCommander XE 2018 - Alter Version Number]]>I installed an update for FreeCommander XE 2018 (new version Build 781) and VulnDetect detects this correctly.

But the installer of FreeCommander XE 2018 always creates a backup of the old version (in the folder C:\Program Files\FreeCommander XE\backup)
For the old version in that backup folder the version 2018.0.0.777 is shown.
But it should be Build 777.

Here the information extracted from the EXE file:

File name and path:     C:\Program Files\FreeCommander XE\backup\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:    2018.0.0.777
File Version:           2018.0.0.777
Product Version String: 2018.0.0.770
Product Version:        2018.0.0.770
]]>https://vulndetect.org/topic/375/solved-freecommander-xe-2018-alter-version-numberRSS for NodeTue, 12 May 2026 03:34:03 GMTFri, 07 Sep 2018 15:29:09 GMT60<![CDATA[Reply to [Solved] FreeCommander XE 2018 - Alter Version Number on Tue, 04 Dec 2018 20:31:17 GMT]]>For FreeCommander all versions are shown correctly (like "Version 2018 release 787 donor").
Issue solved!

]]>https://vulndetect.org/post/1900https://vulndetect.org/post/1900Tue, 04 Dec 2018 20:31:17 GMT<![CDATA[Reply to [Solved] FreeCommander XE 2018 - Alter Version Number on Fri, 07 Sep 2018 16:46:08 GMT]]>Yes, that will be fixed on the next review of the rules, but happy to see you agree with the new way of writing the version numbers for FreeCommander.

]]>https://vulndetect.org/post/1465https://vulndetect.org/post/1465Fri, 07 Sep 2018 16:46:08 GMT