[WLX] fileinfo 2.23 x32/x64 (May 2017)

[grmmx]

1. There is a problem with displaying the FileInfo window if the target/checked file uses a Unicode path.

2. FileVersion and ProductVersion often show strange values that don't match the values shown by Windows.
For example, the properties of the same file:

*Windows:
File version : 8.8.172.35
Product version : 8.8.172.035

*FileInfo:
FileVersion : 8.0.10
ProductVersion: 8.8.172.035


PS: Unfortunately, the Author did not share the FileInfo sources.

[Gral]

Name of that file? Where is this file located? Maybe this is due system redirection?

[sqa_wizard]

Actually there are 2 different file versions and product versions for files.
FileInfo shows both, just windows 10+ shows one version only.

[grmmx]

Actually there are 2 different file versions and product versions for files.
FileInfo shows both, just windows 10+ shows one version only.

OK, but then which option is correct?
Here is another example of one and the same file:

* Windows:
File version : 1.2.0.0
Product version : 1.02

* FileInfo:
FileVersion : 1.02
ProductVersion : 1.02

[grmmx]

Name of that file?

WinDjView.exe
Foxit Reader.exe
...
Any name "fileName.exe"

Where is this file located?

On the local system, drive D:\

Maybe this is due system redirection?

Work in the usual, regular mode. Windows 10 x64, local system.

The problem occurs if the file path contains Unicode characters - the FileInfo window is not displayed.
And the second problem is that in many cases the versions of the file in FileInfo and Windows do not match.

[sqa_wizard]

OK, but then which option is correct?

Both versions are correct, because they are set by the compiler.
Just MS Windows hides the full truth (for your sake as usual).
FileInfo shows all available info though.

[nice]

for file 'ntfs.sys', fileinfo shows FileVersion 6.1.7600.16385 , ProductVersion : 6.1.7600.16385
Windows shows FileVersion 6.1.7601.24382 , ProductVersion : 6.1.7601.24382

and below in fileinfo there's
File/Product version : 6.1.7601.24382 / 6.1.7601.24382
which is correct (?)

so, fileinfo shows "FileVersion", "ProductVersion", and "File/Product version", which are different
but "File/Product version" is at the bottom and not noticeable

in resources of the file, there are 6.1.7601.24382
from where it takes the 6.1.7600.16385?

[Dalai]

2nice
You have to look very closely to see that the first set of information (6.1.7600.16385) doesn't ccome directly from ntfs.sys but ntfs.sys.mui, and also from the language specific version information block within that file. Both pieces of information are correct.

Also, there can be two version information block in any given PE file: a fixed one (VS_FIXEDFILEINFO) and a variable one (in StringFileInfo/VarFileInfo). These can contain different information, but both of them are correct. Some programs and TC plugins can show these, the PE Viewer Lister plugin is one of them, and FileInfo does indirectly (and automatically) as you can see.

Regards
Dalai

[Flint]

In Windows 10 the tree on the DLL Dependencies tab is displayed always collapsed. But on my Windows 7 machine it's shown expanded by default. The plugin version is identical, the configs are also identical; so is TC version and TC configuration files (I even copied the full TC folder and its configs to make sure).

Does anyone know what may cause this difference in behavior, and how to fix it, to show expanded tree on Win10 too?

[Dalai]

2Flint
For me, the DLL dependency tree has always been collapsed by default, on all systems ranging from Win2k to Win10. I also don't see any settings, neither in the plugin's Readme.txt nor the fileinfo.wlx itself, that could enable such feature. Did you try without a fileinfo.ini so that the plugin uses its default settings? If the tree is also expanded in this case, you might have something on your system that does this; no idea what that would be though.

Regards
Dalai

[Flint]

For me it's always been expanded (maybe not always, but as far as I remember), and it only changed since I started moving to Win10.

I tried it now on Win7 machine with removed fileinfo.ini, the dependency depth became 2 by default, the tree is shown expanded for one level and the second-level sub-trees are collapsed. The same copy of TC folder with fileinfo.ini removed, when started in Win10, also has max depth 2, but the full tree is completely collapsed instead of showing the first level.

[petermad]

I tried it now on Win7 machine with removed fileinfo.ini, the dependency depth became 2 by default, the tree is shown expanded for one level and the second-level sub-trees are collapsed. The same copy of TC folder with fileinfo.ini removed, when started in Win10, also has max depth 2, but the full tree is completely collapsed instead of showing the first level.

This is whar I see too.

[Flint]

An addition: I ran a MS Spy++ trace on both machines, and while I don't understand most of what's happening there (or rather, why it's happening exactly that way), but I can clearly see that on Win7, at the very end, there is a message TVM_EXPAND sent to the tree control, while on Win10 there is no such message. Unfortunately, it does not tell what the source of the message is…

[Dalai]

It looks like I may have been too fast to judge. This is what I see on Win7 (and all older Windows versions): https://abload.de/img/wlx_fileinfodai50.png. But weirdly enough, the dependency tree is indeed collapsed on Win10 (I just tested 1709, 1809 and 21H2). This is what I see on Win10: https://abload.de/img/wlx_fileinfo_win107jdx9.png

So, I can confirm what you see on your systems. Which makes me think that MS changed something in Windows 10 - just like they did with the cursor behavior in text edit fields in 1803/1809 (which annoys me big time every time I'm forced to use Win10).

Regards
Dalai