Share via

kernel32.dll dependenci ext-ms-win-oobe-query-l1-1-0.dll missing from Windows 10

Elimar 0 Reputation points
2023-04-02T05:44:44.7666667+00:00

I am not able to call my own C+ DLL from Excel VBA using Windows 10.
I get the message DLL not found.

Using Lucasg Dependencies I can see that Kernel32.dll is missing ext-ms-win-oobe-query-l1-1-0.dll.

Dependencies

I have been looking at several computers with the same results.

I have tested OK with Windows 7 for the same DLL, working correctly.

I think that this can cause trouble for many applications that call DLLs as Kernel32.dll is used widely.

This problem previously has been reported with no answer.

ext-ms-win-oobe-query-l1-1-0.dll missing dependency - Microsoft Community

Thanks!

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,901 questions
Office Development
Office Development
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Development: The process of researching, productizing, and refining new or existing technologies.
3,624 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. RLWA32 41,696 Reputation points
    2023-04-08T22:10:49.6+00:00

    I think the focus on ext-ms-win-oobe-query-l1-1-0.dll is a red herring. This is an API set and according to Microsoft's documentation at API set contract names "Names that begin with ext- represent APIs that may not exist on all Windows versions." Furthermore, on my Windows 10 this Api set is indicated as delay load for kernel32 - kernel32delayload

    This means that the system will not attempt to resolve this at load-time, and its absence should not prevent a dll that depends on kernel32.dll from being loaded. If you think about it, if this was a real problem NOTHING would load in Windows because almost everything has a dependency on kernel32.dll. Consequently, I believe that the problem with your C++ dll is elsewhere.

    0 comments