OK, I mark the topic as Solved and move it to the category Solved Detection Issues.

Today I installed an update for Enpass and again the version numbers are different. On my PC I am using the Windows Store Version, here the displayed version is 6.1.0 (408). On my VM I am using the Classic Windows Version, here the displayed version is 6.1.0 (407). But I see that in both exe files the version number is 6.1.0.0 is stored. So it is OK if you show 6.1.0 for both versions. Issue solved

The new icons are shown. I mark the topic as Solved and move it to the category Solved Detection Issues.

Total Commander is now detected by VulnDetect and the version number 9.22a is also correct.

@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.

OK, I mark the topic as Solved and move it to the category Solved Detection Issues.

OK, I mark the topic as Solved and move it to the category Solved Detection Issues.

You now show SUMo (Beta) Issue solved

The new icon is shown. Issue solved.

OK, master, I agree! OK, I mark the topic as Solved and move it to the category Solved Detection Issues.

GeForce Experience is no longer shown as Beta. So I mark the topic as Solved and move it to the category Solved Detection Issues.

OK, I mark the topic as Solved and move it to the category Solved Detection Issues.

Meantime you show the versions 4.3.1.492 and 4.3.1.493. So the issue is solved.

Currently Version 6.0.4 is detected, it is OK when you don't show the 128413 Issue is solved.

In my list of applications the status for GetAppDetails for VulnDetect is now EoL Issue solved.

Version 72.0.3626.121 is now shown as Google Chrome Issue is fixed!

@Tom This is the reason why my suggestion Explain the Labels in the List of Applications is so important!

The version number 1.13 is now displayed correctly. Thank you for fixing this!

The version number 6.8.2 is now displayed correctly. Thank you for fixing this!

@OLLI_S Yes, that was a nasty one. Luckily it affected a simple Rule set....