Using getfileversioninfo and verqueryvalue

Question

0.00/5 (No votes)

See more:

I am trying to use these two functions in my application and I have had nothing but headaches. I finally figured out what to do to get it to link. Now I have a problem getting it to run. I get an error message that states, "api-ms-win-core-version-l1-1-1.dll is missing from your computer..."

Does anyone know of a work-around for this?

What I have tried:

I did some searches and, yes, it is missing. This is a W7 box and it's not on this one and it's not on my W10 box either. The really annoying thing about this is I used dumpbin to list the imports of the program and it says it is importing that DLL for the functions GetFileVersionInfoW and GetFileVersionInfoSizeW but according to the documentation it uses "api-ms-win-core-version-l1-1-0.dll" and that does exist on both machines.

An update for this - the program will work on the W10 box now BUT I can't find that DLL on the machine anywhere - the l1-1-1.dll file I mean. I searched the registry and I find no mention of it anywhere.

This brings up another question - how can the loader utilize a DLL that is nowhere to be found on this machine? It seems we have gone from DLL hell to DLL sorcery.

Another update : I think I see what is going on now. The DLL file that exists (api-ms-win-core-version-l1-1-0.dll) exports all four of the Version functions. Incidentally, only the wide character versions, and the MBCS versions are nowhere to be found. I think what is happening is the loader finds the functions in question in the ...l1-1-0.dll so it links with them and ignores the fact that ...l1-1-1.dll is not present. Now, it seems this is how it works on W10 but it is NOT working like this in W7. I think the root of the problem is there is a bug in whatever specifies the DLL for those functions in the file mincore.lib. I would guess it is a .DEF file but I don't know.

Posted 23-Oct-18 11:49am

Rick York

Updated 24-Oct-18 0:41am

v4

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2018-10-24T00:42:00

Solution 1

Sometimes different windows version are tricky. Are both at actual update levels and same "flavor"? Interesting is also an answer at stackoverflow. I understand it so, that the "l1-1-1" dll isnt available on W7. Not sure about it.

Try to fix component store as described in that article.

Posted 24-Oct-18 0:42am

KarstenK

Comments

Rick York 24-Oct-18 10:40am

That might be a work-around for this. I will give it a try. I still think there is a bug because their library is specifying a DLL that they are not distributing. In fact, it doesn't exist on my machine but somehow the program is still loading. I think the W10 loader has been changed to behave differently than the W7 loader.

Rick York 24-Oct-18 11:47am

I appreciate the suggestion Karsten and I tried it. I re-targeted the EXE for XP using the v1.41 XP toolset and now it won't even link. I can't believe this is broken so badly. Until now, everything I have tried has worked with W7 but this certainly does not. I have contrived a very hackish work-around but I find this very, very annoying.