FreeCommander XE - Alter Version Number

[OLLI_S]

FreeCommander XE is detected correctly on my system, but the displayed version number should be altered.
In the application the displayed version number is FreeCommander XE 2018 Build 786 64-bit donor.
In VulnDetect the displayed version number is 2018 release 786 donor.
So you should show the same version number that is shown in the app (just replace the word release with Build).

Tell me if you need a screen shot of the Help -> About window.

---

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:    2018.0.0.786
File Version:           2018.0.0.786
Product Version String: 2018.0.0.780
Product Version:        2018.0.0.780

[Tom]

I believe this is more or less the same issue we talked about before:
https://vulndetect.org/topic/377/

The version information we use in the Rules are based on the changelog / release postings in the FreeCommand forum.

[OLLI_S]

@Tom
In the linked post you refer to https://freecommander.com/en/downloads/
There I see often the word Build but not even once the word "release".

So I suggested to replace the word release with Build (just the wording).
Then it would be consistent to the version info in Help -> About:

FreeCommander XE 2018 Build 786 64-bit donor

[Tom]

This is the ones we look at:
https://freecommander.com/forum/viewtopic.php?f=6&t=775&start=225#p28468

[OLLI_S]

Hmmm.....
Users see in the App the word Build so I thought it might be a good idea to use the same wording (increase the user friendliness)
@Tom, it is up to you!

[OLLI_S]

@Tom
Should we use the word Build (that is what users see in the app).
Or should we use release (like in the release notes, but this might confuse the user)