0

While trying to resolve dynamic DLLs (api-ms*, ext-ms*), I face a problem with an undefined reference from kernel32.AddDllDirectory: api-ms-win-core-libraryloader-l1-1-0.AddDllDirectory, but there is no such entry in the apisetschema.dll. Only those entries related to the "libraryloader" are presented:

api-ms-win-core-libraryloader-l1-1-1
api-ms-win-core-libraryloader-l1-2-3
api-ms-win-core-libraryloader-l2-1-0
api-ms-win-core-libraryloader-private-l1-1-0

What should I do to get api-ms-win-core-libraryloader-l1-1-0? Why does the kernel refer to it? How do I handle it?

I am using Windows 11, API_SET_NAMESPACE's version is 6.

Improve this question
8
  • 1
    Have you read up about Windows API sets yet? It's an implementation detail of how the DLL Loader handles OS APIs across different device types. You shouldn't be dealing with the API sets directly yourself. Commented Oct 27 at 17:09
  • @RemyLebeau, I have reasons to handle them manually Commented Oct 27 at 19:58
  • @DenDon - ok, what if windows find last - symbol in name, and search (by hash )only "api-ms-win-core-libraryloader-l1-1-" ? Commented Oct 27 at 21:35
  • "I have reasons to handle them manually" - possible better describe this reason at first Commented Oct 27 at 21:36
  • @RbMm, Does Windows do it this way? Commented Oct 28 at 13:03
Related questions
2775
How do I install pip on Windows?
1654
Filename too long in Git for Windows
1592
Ignoring directories in Git repositories on Windows
Load 5 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.