microsoft / microsoft/STL

<winver.h>: Missing symbols in Version.lib

Open
#2,153 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

external
Dominant language
C++
Stars
11.1k
Forks
1.7k
Avg merge
4d 15h
Merged PRs (30d)
22

Description

Background:
First I'd like to preface this that I've tried for over a year to get this fixed, and I understand this is not part of the STL implementation - however there is nowhere else to report this. Visual Studio Helpdesk told me to go to Feedback Hub, everything dies in the Feedback Hub, the Microsoft Reddit is also useless.

Previous submissions:
Feedback Hub (over a year ago): https://aka.ms/AAdkzh2
Visual Studio Ticket: https://developercommunity.visualstudio.com/t/Versionlib-missing-symbols-proof-with/1510348

Problem:
GetFileVersionInfoSizeExA and GetFileVersionInfoExA are missing from Version.lib, I have to manually call them by loading Version.dll. Below is a screenshot showing an attempt to compile with the missing symbols, and a DUMPBIN of Version.lib. This issue has persisted for at least a year (according to my ticket history), I believe it spans back three years.

B40d6401ffd1443d8b3378701ae47b0a4637651582563700148_20210821-115736-image

Of course, Version.dll has the symbols:
image

So this means for those two missing symbols I have to manually load them from Version.dll:

image

Like I said, not part of STL but there's nowhere else to post this. I've tried for over a year through helpdesk hell.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report concerns missing symbols in Windows Version.lib and references Version.dll, Feedback Hub, and a Visual Studio ticket, but names no STL file, test, or entry point. First confirm whether this repository owns the import library issue; the report is complete when ownership and a concrete change location are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.