Revisting a previous topic: $VERSIONINFO not working as expected

[hanness]

This is something I had posted about some months ago, I simply thought that I would bring it up once more just to make sure it was on the radar. Consider it a low priority issue (at least from my standpoint).

Sample Code:
---------------
$VERSIONINFO:FILEVERSION#=2,0,0,0
$VERSIONINFO:PRODUCTVERSION#=2,0,0,0
$VERSIONINFO:ProductName=My Product
$VERSIONINFO:LegalCopyright=Copyright
$VERSIONINFO:FileDescription=Description

PRINT "This program serves no purpose other than a test of the #VERSIONINFO metacommand"
SLEEP
----------------

Of the above items, the only one that seems to work is "FILEVERSION#".

If you compile the above, then, right-click on the resulting .exe file, and go to the Details tab, the only one of these items that will show a value is "File version".

NOTES: I realize that there are other fields, but I've not tested those. Might be worth looking at all of them.

Also, I don't suspect that this has anything to do with any changes made by Microsoft. I have an executable from 2004 in which all of these fields show up just fine, so if there were any changes made by Microsoft, they are not affecting even those very old files.

Tested on Windows 10 Pro 1903 and 1909.

[FellippeHeitor]

Well, it is something changed by MS after all, since all $VERSIONINFO fields show up from Windows XP to Windows 7 (last I checked).

The thing is: we use an official method for embedding the meta data. Something in Windows 8 and up doesn't like that method anymore... Thanks for pointing it out though. I might be able to tackle it before we release another build.

[hanness]

Thanks. I had assumed that it was not some change in Windows since 15 year old executables that I have still display those details fine. So I guess it's a weird issue that only affects some files.

I hate that type of problem. Makes tracking the source of the problem a lot more difficult.