Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. 3rd Party Software
  4. Qt 5.15.9, MinGW 32-bit compiler, "Application was unable to start correctly (0xc0000142)".
Forum Updated to NodeBB v4.3 + New Features

Qt 5.15.9, MinGW 32-bit compiler, "Application was unable to start correctly (0xc0000142)".

Scheduled Pinned Locked Moved Solved 3rd Party Software
30 Posts 4 Posters 7.5k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SGaistS SGaist

    It's indeed a C library which should be immune to the usually compatibility issues between MinGW and MSVC (otherwise you would not have been able to build it).

    Can you check with something like Dependency Walker to see if everything is getting loaded correctly ?

    O Offline
    O Offline
    orsini29
    wrote on last edited by orsini29
    #11

    @SGaist

    I just downloaded dependency walker and threw my *.exe in there and well...I think we (aka you) found the issue..Can this really be right? I do not even know of half these dependencies..

    API-MS-WIN-CORE-APIQUERY-L1-1-0.DLL
    API-MS-WIN-CORE-APIQUERY-L2-1-0.DLL
    API-MS-WIN-CORE-APPCOMPAT-L1-1-0.DLL
    API-MS-WIN-CORE-APPCOMPAT-L1-1-1.DLL
    API-MS-WIN-CORE-APPINIT-L1-1-0.DLL
    API-MS-WIN-CORE-ATOMS-L1-1-0.DLL
    API-MS-WIN-CORE-COM-L1-1-0.DLL
    API-MS-WIN-CORE-COM-L1-1-1.DLL
    API-MS-WIN-CORE-COM-L1-1-2.DLL
    API-MS-WIN-CORE-COMM-L1-1-0.DLL
    API-MS-WIN-CORE-CONSOLE-L1-1-0.DLL
    API-MS-WIN-CORE-CONSOLE-L1-2-0.DLL
    API-MS-WIN-CORE-CONSOLE-L1-2-1.DLL
    API-MS-WIN-CORE-CONSOLE-L2-1-0.DLL
    API-MS-WIN-CORE-CONSOLE-L2-2-0.DLL
    API-MS-WIN-CORE-CONSOLE-L3-2-0.DLL
    API-MS-WIN-CORE-CRT-L1-1-0.DLL
    API-MS-WIN-CORE-CRT-L2-1-0.DLL
    API-MS-WIN-CORE-DATETIME-L1-1-0.DLL
    API-MS-WIN-CORE-DATETIME-L1-1-1.DLL
    API-MS-WIN-CORE-DATETIME-L1-1-2.DLL
    API-MS-WIN-CORE-DEBUG-L1-1-0.DLL
    API-MS-WIN-CORE-DEBUG-L1-1-1.DLL
    API-MS-WIN-CORE-DELAYLOAD-L1-1-0.DLL
    API-MS-WIN-CORE-DELAYLOAD-L1-1-1.DLL
    API-MS-WIN-CORE-ERRORHANDLING-L1-1-0.DLL
    API-MS-WIN-CORE-ERRORHANDLING-L1-1-2.DLL
    API-MS-WIN-CORE-ERRORHANDLING-L1-1-3.DLL
    API-MS-WIN-CORE-FIBERS-L1-1-0.DLL
    API-MS-WIN-CORE-FIBERS-L1-1-1.DLL
    API-MS-WIN-CORE-FIBERS-L2-1-0.DLL
    API-MS-WIN-CORE-FIBERS-L2-1-1.DLL
    API-MS-WIN-CORE-FILE-L1-1-0.DLL
    API-MS-WIN-CORE-FILE-L1-2-0.DLL
    API-MS-WIN-CORE-FILE-L1-2-1.DLL
    API-MS-WIN-CORE-FILE-L1-2-2.DLL
    API-MS-WIN-CORE-FILE-L2-1-0.DLL
    API-MS-WIN-CORE-FILE-L2-1-1.DLL
    API-MS-WIN-CORE-FILE-L2-1-2.DLL
    API-MS-WIN-CORE-FILE-L2-1-3.DLL
    API-MS-WIN-CORE-HANDLE-L1-1-0.DLL
    API-MS-WIN-CORE-HEAP-L1-1-0.DLL
    API-MS-WIN-CORE-HEAP-L2-1-0.DLL
    API-MS-WIN-CORE-HEAP-OBSOLETE-L1-1-0.DLL
    API-MS-WIN-CORE-INTERLOCKED-L1-1-0.DLL
    API-MS-WIN-CORE-IO-L1-1-0.DLL
    API-MS-WIN-CORE-IO-L1-1-1.DLL
    API-MS-WIN-CORE-JOB-L1-1-0.DLL
    API-MS-WIN-CORE-JOB-L2-1-0.DLL
    API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-0.DLL
    API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-1.DLL
    API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-2.DLL
    API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-LARGEINTEGER-L1-1-0.DLL
    API-MS-WIN-CORE-LIBRARYLOADER-L1-1-0.DLL
    API-MS-WIN-CORE-LIBRARYLOADER-L1-2-0.DLL
    API-MS-WIN-CORE-LIBRARYLOADER-L1-2-1.DLL
    API-MS-WIN-CORE-LIBRARYLOADER-L1-2-2.DLL
    API-MS-WIN-CORE-LIBRARYLOADER-L2-1-0.DLL
    API-MS-WIN-CORE-LOCALIZATION-L1-2-0.DLL
    API-MS-WIN-CORE-LOCALIZATION-L1-2-2.DLL
    API-MS-WIN-CORE-LOCALIZATION-L2-1-0.DLL
    API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-2-0.DLL
    API-MS-WIN-CORE-LOCALIZATION-PRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-MARSHAL-L1-1-0.DLL
    API-MS-WIN-CORE-MEMORY-L1-1-0.DLL
    API-MS-WIN-CORE-MEMORY-L1-1-1.DLL
    API-MS-WIN-CORE-MEMORY-L1-1-2.DLL
    API-MS-WIN-CORE-MEMORY-L1-1-3.DLL
    API-MS-WIN-CORE-NAMEDPIPE-L1-1-0.DLL
    API-MS-WIN-CORE-NAMEDPIPE-L1-2-1.DLL
    API-MS-WIN-CORE-NAMEDPIPE-L1-2-2.DLL
    API-MS-WIN-CORE-NAMESPACE-L1-1-0.DLL
    API-MS-WIN-CORE-NORMALIZATION-L1-1-0.DLL
    API-MS-WIN-CORE-PATH-L1-1-0.DLL
    API-MS-WIN-CORE-PCW-L1-1-0.DLL
    API-MS-WIN-CORE-PRIVATEPROFILE-L1-1-0.DLL
    API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-1-0.DLL
    API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-2-0.DLL
    API-MS-WIN-CORE-PROCESSSNAPSHOT-L1-1-0.DLL
    API-MS-WIN-CORE-PROCESSTHREADS-L1-1-0.DLL
    API-MS-WIN-CORE-PROCESSTHREADS-L1-1-1.DLL
    API-MS-WIN-CORE-PROCESSTHREADS-L1-1-2.DLL
    API-MS-WIN-CORE-PROCESSTHREADS-L1-1-3.DLL
    API-MS-WIN-CORE-PROCESSTOPOLOGY-L1-1-0.DLL
    API-MS-WIN-CORE-PROFILE-L1-1-0.DLL
    API-MS-WIN-CORE-PSAPI-ANSI-L1-1-0.DLL
    API-MS-WIN-CORE-PSAPI-L1-1-0.DLL
    API-MS-WIN-CORE-PSM-KEY-L1-1-0.DLL
    API-MS-WIN-CORE-QUIRKS-L1-1-0.DLL
    API-MS-WIN-CORE-REALTIME-L1-1-0.DLL
    API-MS-WIN-CORE-REGISTRY-L1-1-0.DLL
    API-MS-WIN-CORE-REGISTRY-L1-1-1.DLL
    API-MS-WIN-CORE-REGISTRY-L1-1-2.DLL
    API-MS-WIN-CORE-REGISTRY-L2-1-0.DLL
    API-MS-WIN-CORE-REGISTRYUSERSPECIFIC-L1-1-0.DLL
    API-MS-WIN-CORE-RTLSUPPORT-L1-1-0.DLL
    API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL
    API-MS-WIN-CORE-SHLWAPI-LEGACY-L1-1-0.DLL
    API-MS-WIN-CORE-SHLWAPI-OBSOLETE-L1-1-0.DLL
    API-MS-WIN-CORE-SIDEBYSIDE-L1-1-0.DLL
    API-MS-WIN-CORE-STRING-L1-1-0.DLL
    API-MS-WIN-CORE-STRING-L2-1-0.DLL
    API-MS-WIN-CORE-STRING-L2-1-1.DLL
    API-MS-WIN-CORE-STRING-OBSOLETE-L1-1-0.DLL
    API-MS-WIN-CORE-STRINGANSI-L1-1-0.DLL
    API-MS-WIN-CORE-SYNCH-L1-1-0.DLL
    API-MS-WIN-CORE-SYNCH-L1-2-0.DLL
    API-MS-WIN-CORE-SYNCH-L1-2-1.DLL
    API-MS-WIN-CORE-SYSINFO-L1-1-0.DLL
    API-MS-WIN-CORE-SYSINFO-L1-2-0.DLL
    API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL
    API-MS-WIN-CORE-SYSINFO-L1-2-3.DLL
    API-MS-WIN-CORE-SYSTEMTOPOLOGY-L1-1-0.DLL
    API-MS-WIN-CORE-SYSTEMTOPOLOGY-L1-1-1.DLL
    API-MS-WIN-CORE-THREADPOOL-L1-2-0.DLL
    API-MS-WIN-CORE-THREADPOOL-LEGACY-L1-1-0.DLL
    API-MS-WIN-CORE-THREADPOOL-PRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-TIMEZONE-L1-1-0.DLL
    API-MS-WIN-CORE-URL-L1-1-0.DLL
    API-MS-WIN-CORE-UTIL-L1-1-0.DLL
    API-MS-WIN-CORE-VERSION-L1-1-0.DLL
    API-MS-WIN-CORE-VERSION-L1-1-1.DLL
    API-MS-WIN-CORE-VERSION-PRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-VERSIONANSI-L1-1-0.DLL
    API-MS-WIN-CORE-VERSIONANSI-L1-1-1.DLL
    API-MS-WIN-CORE-WINDOWSERRORREPORTING-L1-1-0.DLL
    API-MS-WIN-CORE-WINDOWSERRORREPORTING-L1-1-1.DLL
    API-MS-WIN-CORE-WINDOWSERRORREPORTING-L1-1-2.DLL
    API-MS-WIN-CORE-WINDOWSERRORREPORTING-L1-1-3.DLL
    API-MS-WIN-CORE-WOW64-L1-1-0.DLL
    API-MS-WIN-CORE-WOW64-L1-1-1.DLL
    API-MS-WIN-CORE-WOW64-L1-1-3.DLL
    API-MS-WIN-CORE-XSTATE-L2-1-0.DLL
    API-MS-WIN-CORE-XSTATE-L2-1-1.DLL
    API-MS-WIN-CRT-CONVERT-L1-1-0.DLL
    API-MS-WIN-CRT-ENVIRONMENT-L1-1-0.DLL
    API-MS-WIN-CRT-FILESYSTEM-L1-1-0.DLL
    API-MS-WIN-CRT-HEAP-L1-1-0.DLL
    API-MS-WIN-CRT-LOCALE-L1-1-0.DLL
    API-MS-WIN-CRT-MATH-L1-1-0.DLL
    API-MS-WIN-CRT-PRIVATE-L1-1-0.DLL
    API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
    API-MS-WIN-CRT-STDIO-L1-1-0.DLL
    API-MS-WIN-CRT-STRING-L1-1-0.DLL
    API-MS-WIN-CRT-TIME-L1-1-0.DLL
    API-MS-WIN-CRT-UTILITY-L1-1-0.DLL
    API-MS-WIN-DEVICES-CONFIG-L1-1-1.DLL
    API-MS-WIN-EVENTING-CLASSICPROVIDER-L1-1-0.DLL
    API-MS-WIN-EVENTING-CONSUMER-L1-1-0.DLL
    API-MS-WIN-EVENTING-CONSUMER-L1-1-1.DLL
    API-MS-WIN-EVENTING-CONTROLLER-L1-1-0.DLL
    API-MS-WIN-EVENTING-PROVIDER-L1-1-0.DLL
    API-MS-WIN-GDI-INTERNAL-UAP-L1-1-0.DLL
    API-MS-WIN-SECURITY-APPCONTAINER-L1-1-0.DLL
    API-MS-WIN-SECURITY-AUDIT-L1-1-0.DLL
    API-MS-WIN-SECURITY-AUDIT-L1-1-1.DLL
    API-MS-WIN-SECURITY-BASE-L1-1-0.DLL
    API-MS-WIN-SECURITY-BASE-L1-2-0.DLL
    API-MS-WIN-SECURITY-BASE-PRIVATE-L1-1-0.DLL
    API-MS-WIN-SERVICE-CORE-L1-1-0.DLL
    API-MS-WIN-SERVICE-CORE-L1-1-1.DLL
    API-MS-WIN-SERVICE-CORE-L1-1-2.DLL
    API-MS-WIN-SERVICE-MANAGEMENT-L1-1-0.DLL
    API-MS-WIN-SERVICE-MANAGEMENT-L2-1-0.DLL
    API-MS-WIN-SERVICE-PRIVATE-L1-1-0.DLL
    API-MS-WIN-SERVICE-PRIVATE-L1-1-2.DLL
    API-MS-WIN-SERVICE-PRIVATE-L1-1-3.DLL
    API-MS-WIN-SERVICE-PRIVATE-L1-1-4.DLL
    API-MS-WIN-SERVICE-WINSVC-L1-1-0.DLL
    API-MS-WIN-SHELL-SHELLCOM-L1-1-0.DLL
    API-MS-WIN-STATESEPARATION-HELPERS-L1-1-0.DLL
    MSVCR90.DLL
    QT5CORE.DLL
    QT5GUI.DLL
    QT5WIDGETS.DLL
    API-MS-WIN-APPMODEL-IDENTITY-L1-2-0.DLL
    API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-1.DLL
    API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-2.DLL
    API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-3.DLL
    API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-7.DLL
    API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
    API-MS-WIN-APPMODEL-RUNTIME-L1-1-1.DLL
    API-MS-WIN-APPMODEL-STATE-L1-2-0.DLL
    API-MS-WIN-APPMODEL-UNLOCK-L1-1-0.DLL
    API-MS-WIN-BASE-UTIL-L1-1-0.DLL
    API-MS-WIN-CONTAINERS-CMCLIENT-L1-1-0.DLL
    API-MS-WIN-CONTAINERS-CMCLIENT-L1-2-0.DLL
    API-MS-WIN-CORE-CALENDAR-L1-1-0.DLL
    API-MS-WIN-CORE-COM-L2-1-1.DLL
    API-MS-WIN-CORE-COM-MIDLPROXYSTUB-L1-1-0.DLL
    API-MS-WIN-CORE-COM-PRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-COM-PRIVATE-L1-1-1.DLL
    API-MS-WIN-CORE-COM-PRIVATE-L1-2-0.DLL
    API-MS-WIN-CORE-COM-PRIVATE-L1-3-0.DLL
    API-MS-WIN-CORE-DEBUG-MINIDUMP-L1-1-0.DLL
    API-MS-WIN-CORE-FEATURESTAGING-L1-1-0.DLL
    API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-1.DLL
    API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-2.DLL
    API-MS-WIN-CORE-LOCALIZATION-L1-1-0.DLL
    API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL
    API-MS-WIN-CORE-MISC-L1-1-0.DLL
    API-MS-WIN-CORE-PRIVATEPROFILE-L1-1-1.DLL
    API-MS-WIN-CORE-PROCESSTOPOLOGY-OBSOLETE-L1-1-0.DLL
    API-MS-WIN-CORE-PSM-APP-L1-1-0.DLL
    API-MS-WIN-CORE-PSM-APPNOTIFY-L1-1-0.DLL
    API-MS-WIN-CORE-REALTIME-L1-1-1.DLL
    API-MS-WIN-CORE-REGISTRY-PRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-SHUTDOWN-L1-1-0.DLL
    API-MS-WIN-CORE-SYNCH-ANSI-L1-1-0.DLL
    API-MS-WIN-CORE-SYSINFO-L2-1-0.DLL
    API-MS-WIN-CORE-TEXTINPUT-CLIENT-L1-1-0.DLL
    API-MS-WIN-CORE-TEXTINPUT-CLIENT-L1-1-1.DLL
    API-MS-WIN-CORE-TOOLHELP-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-ERROR-L1-1-1.DLL
    API-MS-WIN-CORE-WINRT-ERRORPRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-PROPERTYSETPRIVATE-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-PROPERTYSETPRIVATE-L1-1-1.DLL
    API-MS-WIN-CORE-WINRT-REGISTRATION-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
    API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
    API-MS-WIN-COREUI-SECRUNTIME-L1-1-0.DLL
    API-MS-WIN-CRT-PROCESS-L1-1-0.DLL
    API-MS-WIN-DEVICES-QUERY-L1-1-0.DLL
    API-MS-WIN-DEVICES-SWDEVICE-L1-1-0.DLL
    API-MS-WIN-DEVICES-SWDEVICE-L1-1-1.DLL
    API-MS-WIN-DOWNLEVEL-ADVAPI32-L1-1-0.DLL
    API-MS-WIN-DOWNLEVEL-ADVAPI32-L2-1-0.DLL
    API-MS-WIN-DOWNLEVEL-KERNEL32-L1-1-0.DLL
    API-MS-WIN-DOWNLEVEL-KERNEL32-L2-1-0.DLL
    API-MS-WIN-DOWNLEVEL-NORMALIZ-L1-1-0.DLL
    API-MS-WIN-DOWNLEVEL-OLE32-L1-1-0.DLL
    API-MS-WIN-DOWNLEVEL-SHELL32-L1-1-0.DLL
    API-MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL
    API-MS-WIN-DOWNLEVEL-SHLWAPI-L2-1-0.DLL
    API-MS-WIN-DOWNLEVEL-USER32-L1-1-0.DLL
    API-MS-WIN-DOWNLEVEL-VERSION-L1-1-0.DLL
    API-MS-WIN-DWMAPI-L1-1-0.DLL
    API-MS-WIN-DX-D3DKMT-L1-1-0.DLL
    API-MS-WIN-DX-D3DKMT-L1-1-1.DLL
    API-MS-WIN-DX-D3DKMT-L1-1-3.DLL
    API-MS-WIN-DX-D3DKMT-L1-1-4.DLL
    API-MS-WIN-EVENTING-LEGACY-L1-1-0.DLL
    API-MS-WIN-EVENTING-OBSOLETE-L1-1-0.DLL
    API-MS-WIN-EVENTING-TDH-L1-1-0.DLL
    API-MS-WIN-EVENTLOG-LEGACY-L1-1-0.DLL
    API-MS-WIN-GDI-DPIINFO-L1-1-0.DLL
    API-MS-WIN-HTTP-TIME-L1-1-0.DLL
    API-MS-WIN-MM-MISC-L1-1-0.DLL
    API-MS-WIN-MM-MISC-L2-1-0.DLL
    API-MS-WIN-MM-MME-L1-1-0.DLL
    API-MS-WIN-MM-TIME-L1-1-0.DLL
    API-MS-WIN-NETWORKING-INTERFACECONTEXTS-L1-1-0.DLL
    API-MS-WIN-NTUSER-RECTANGLE-L1-1-0.DLL
    API-MS-WIN-NTUSER-SYSPARAMS-L1-1-0.DLL
    API-MS-WIN-OLE32-IE-L1-1-0.DLL
    API-MS-WIN-OOBE-NOTIFICATION-L1-1-0.DLL
    API-MS-WIN-POWER-BASE-L1-1-0.DLL
    API-MS-WIN-POWER-SETTING-L1-1-0.DLL
    API-MS-WIN-RTCORE-NTUSER-CLIPBOARD-L1-1-0.DLL
    API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-0.DLL
    API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-1.DLL
    API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-2.DLL
    API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-4.DLL
    API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-7.DLL
    API-MS-WIN-RTCORE-NTUSER-PRIVATE-L1-1-9.DLL
    API-MS-WIN-RTCORE-NTUSER-SHELL-L1-1-0.DLL
    API-MS-WIN-RTCORE-NTUSER-SYNCH-L1-1-0.DLL
    API-MS-WIN-RTCORE-NTUSER-WINDOW-L1-1-0.DLL
    API-MS-WIN-RTCORE-NTUSER-WINEVENT-L1-1-0.DLL
    API-MS-WIN-RTCORE-NTUSER-WMPOINTER-L1-1-0.DLL
    API-MS-WIN-SECURITY-ACCESSHLPR-L1-1-0.DLL
    API-MS-WIN-SECURITY-ACTIVEDIRECTORYCLIENT-L1-1-0.DLL
    API-MS-WIN-SECURITY-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL
    API-MS-WIN-SECURITY-BASE-L1-2-1.DLL
    API-MS-WIN-SECURITY-BASE-PRIVATE-L1-1-1.DLL
    API-MS-WIN-SECURITY-CAPABILITY-L1-1-0.DLL
    API-MS-WIN-SECURITY-CREDENTIALS-L1-1-0.DLL
    API-MS-WIN-SECURITY-CREDENTIALS-L2-1-0.DLL
    API-MS-WIN-SECURITY-CRYPTOAPI-L1-1-0.DLL
    API-MS-WIN-SECURITY-GROUPPOLICY-L1-1-0.DLL
    API-MS-WIN-SECURITY-ISOLATEDCONTAINER-L1-1-0.DLL
    API-MS-WIN-SECURITY-ISOLATIONPOLICY-L1-2-0.DLL
    API-MS-WIN-SECURITY-LOGON-L1-1-0.DLL
    API-MS-WIN-SECURITY-LOGON-L1-1-1.DLL
    API-MS-WIN-SECURITY-LSALOOKUP-ANSI-L2-1-0.DLL
    API-MS-WIN-SECURITY-LSALOOKUP-L1-1-0.DLL
    API-MS-WIN-SECURITY-LSALOOKUP-L1-1-1.DLL
    API-MS-WIN-SECURITY-LSALOOKUP-L1-1-2.DLL
    API-MS-WIN-SECURITY-LSALOOKUP-L2-1-0.DLL
    API-MS-WIN-SECURITY-LSAPOLICY-L1-1-0.DLL
    API-MS-WIN-SECURITY-PROVIDER-L1-1-0.DLL
    API-MS-WIN-SECURITY-SDDL-L1-1-0.DLL
    API-MS-WIN-SECURITY-SDDLPARSECOND-L1-1-0.DLL
    API-MS-WIN-SECURITY-SYSTEMFUNCTIONS-L1-1-0.DLL
    API-MS-WIN-SERVICE-CORE-L1-1-4.DLL
    API-MS-WIN-SHCORE-COMHELPERS-L1-1-0.DLL
    API-MS-WIN-SHCORE-OBSOLETE-L1-1-0.DLL
    API-MS-WIN-SHCORE-PATH-L1-1-0.DLL
    API-MS-WIN-SHCORE-REGISTRY-L1-1-0.DLL
    API-MS-WIN-SHCORE-REGISTRY-L1-1-1.DLL
    API-MS-WIN-SHCORE-SCALING-L1-1-0.DLL
    API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
    API-MS-WIN-SHCORE-STREAM-L1-1-0.DLL
    API-MS-WIN-SHCORE-STREAM-WINRT-L1-1-0.DLL
    API-MS-WIN-SHCORE-SYSINFO-L1-1-0.DLL
    API-MS-WIN-SHCORE-TASKPOOL-L1-1-0.DLL
    API-MS-WIN-SHCORE-THREAD-L1-1-0.DLL
    API-MS-WIN-SHCORE-UNICODEANSI-L1-1-0.DLL
    API-MS-WIN-SHELL-ASSOCIATIONS-L1-1-1.DLL
    API-MS-WIN-SHELL-CHANGENOTIFY-L1-1-0.DLL
    API-MS-WIN-SHELL-NAMESPACE-L1-1-0.DLL
    API-MS-WIN-SHELL-SHDIRECTORY-L1-1-0.DLL
    API-MS-WIN-SHELL-SHELLFOLDERS-L1-1-0.DLL
    API-MS-WIN-SHLWAPI-IE-L1-1-0.DLL
    API-MS-WIN-SHLWAPI-WINRT-STORAGE-L1-1-1.DLL
    API-MS-WIN-STORAGE-EXPORTS-EXTERNAL-L1-1-0.DLL
    API-MS-WIN-STORAGE-EXPORTS-INTERNAL-L1-1-0.DLL
    DMENTERPRISEDIAGNOSTICS.DLL
    EFSCORE.DLL
    EXT-MS-MF-PAL-L2-1-0.DLL
    EXT-MS-ONECORE-APPDEFAULTS-L1-1-0.DLL
    EXT-MS-ONECORE-APPMODEL-STATEREPOSITORY-CACHE-L1-1-0.DLL
    EXT-MS-ONECORE-APPMODEL-STATEREPOSITORY-CACHE-L1-1-2.DLL
    EXT-MS-ONECORE-APPMODEL-STATEREPOSITORY-INTERNAL-L1-1-1.DLL
    EXT-MS-ONECORE-APPMODEL-STATEREPOSITORY-INTERNAL-L1-1-3.DLL
    EXT-MS-ONECORE-APPMODEL-STATEREPOSITORY-INTERNAL-L1-1-4.DLL
    EXT-MS-ONECORE-DCOMP-L1-1-0.DLL
    EXT-MS-ONECORE-HLINK-L1-1-0.DLL
    EXT-MS-ONECORE-ORIENTATION-L1-1-0.DLL
    EXT-MS-ONECORE-SERVICE-DEVICEDIRECTORY-CLAIMS-L1-1-0.DLL
    EXT-MS-ONECORE-SHELLCHROMEAPI-L1-1-0.DLL
    EXT-MS-WIN-ADSI-ACTIVEDS-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-ENCRYPTEDFILE-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-LSA-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-MSI-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-NPUSERNAME-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-NTMARTA-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-PSM-APP-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-REGISTRY-L1-1-0.DLL
    EXT-MS-WIN-ADVAPI32-REGISTRY-L1-1-1.DLL
    EXT-MS-WIN-ADVAPI32-SAFER-L1-1-0.DLL
    EXT-MS-WIN-APPCOMPAT-AEINV-L1-1-0.DLL
    EXT-MS-WIN-APPCOMPAT-AEPIC-L1-1-0.DLL
    EXT-MS-WIN-APPCOMPAT-APPHELP-L1-1-0.DLL
    EXT-MS-WIN-APPMODEL-APPEXECUTIONALIAS-L1-1-0.DLL
    EXT-MS-WIN-APPMODEL-APPEXECUTIONALIAS-L1-1-1.DLL
    EXT-MS-WIN-APPMODEL-APPEXECUTIONALIAS-L1-1-2.DLL
    EXT-MS-WIN-APPMODEL-DAXCORE-L1-1-0.DLL
    EXT-MS-WIN-APPMODEL-DEPLOYMENT-L1-1-0.DLL
    EXT-MS-WIN-APPMODEL-STATE-EXT-L1-2-0.DLL
    EXT-MS-WIN-APPMODEL-USERCONTEXT-L1-1-0.DLL
    EXT-MS-WIN-APPMODEL-VIEWSCALEFACTOR-L1-1-0.DLL
    EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOY-L1-1-0.DLL
    EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOYONECORE-L1-1-0.DLL
    EXT-MS-WIN-AUDIOCORE-PAL-L1-2-0.DLL
    EXT-MS-WIN-AUDIOCORE-SPATIAL-L1-1-0.DLL
    EXT-MS-WIN-AUTHZ-CONTEXT-L1-1-0.DLL
    EXT-MS-WIN-AUTHZ-REMOTE-L1-1-0.DLL
    EXT-MS-WIN-BIOMETRICS-WINBIO-CORE-L1-1-0.DLL
    EXT-MS-WIN-COM-APARTMENTRESTRICTION-L1-1-0.DLL
    EXT-MS-WIN-COM-CLBCATQ-L1-1-0.DLL
    EXT-MS-WIN-COM-COML2-L1-1-1.DLL
    EXT-MS-WIN-COM-OLE32-L1-1-0.DLL
    EXT-MS-WIN-COM-OLE32-L1-1-1.DLL
    EXT-MS-WIN-COM-OLE32-L1-1-2.DLL
    EXT-MS-WIN-COM-OLE32-L1-1-3.DLL
    EXT-MS-WIN-COM-OLE32-L1-1-4.DLL
    EXT-MS-WIN-COM-OLE32-L1-1-5.DLL
    EXT-MS-WIN-COM-PSMREGISTER-L1-1-0.DLL
    EXT-MS-WIN-COM-SUSPENDRESILIENCY-L1-1-0.DLL
    EXT-MS-WIN-CONTAINERS-POLICYMANAGERCLI-L1-1-0.DLL
    EXT-MS-WIN-CORE-PKEYHELPER-L1-1-0.DLL
    EXT-MS-WIN-CORE-RESOURCEPOLICY-L1-1-0.DLL
    EXT-MS-WIN-CORE-WINRT-REMOTE-L1-1-0.DLL
    EXT-MS-WIN-DESKTOPAPPX-L1-1-0.DLL
    EXT-MS-WIN-DESKTOPAPPX-L1-1-3.DLL
    EXT-MS-WIN-DEVMGMT-DM-L1-1-0.DLL
    EXT-MS-WIN-DEVMGMT-DM-L1-1-2.DLL
    EXT-MS-WIN-DEVMGMT-POLICY-L1-1-0.DLL
    EXT-MS-WIN-DEVMGMT-POLICY-L1-1-1.DLL
    EXT-MS-WIN-DIRECT2D-DESKTOP-L1-1-0.DLL
    EXT-MS-WIN-DOMAINJOIN-NETJOIN-L1-1-0.DLL
    EXT-MS-WIN-DRIVER-SETUP-L1-1-0.DLL
    EXT-MS-WIN-DWMAPI-EXT-L1-1-0.DLL
    EXT-MS-WIN-DWMAPIDXGI-EXT-L1-1-0.DLL
    EXT-MS-WIN-DWMAPIDXGI-EXT-L1-1-1.DLL
    EXT-MS-WIN-DX-D3DKMT-DXCORE-L1-1-0.DLL
    EXT-MS-WIN-DX-D3DKMT-GDI-L1-1-0.DLL
    EXT-MS-WIN-DXCORE-INTERNAL-L1-1-0.DLL
    EXT-MS-WIN-DXCORE-L1-1-0.DLL
    EXT-MS-WIN-EDPUTIL-POLICY-L1-1-0.DLL
    EXT-MS-WIN-EDPUTIL-POLICY-L1-1-1.DLL
    EXT-MS-WIN-ELS-ELSCORE-L1-1-0.DLL
    EXT-MS-WIN-EVENTING-RUNDOWN-L1-1-0.DLL
    EXT-MS-WIN-FAMILYSAFETY-CHILDACCOUNT-L1-1-0.DLL
    EXT-MS-WIN-FECLIENT-ENCRYPTEDFILE-L1-1-0.DLL
    EXT-MS-WIN-FECLIENT-ENCRYPTEDFILE-L1-1-3.DLL
    EXT-MS-WIN-FIREWALLAPI-WEBPROXY-L1-1-0.DLL
    EXT-MS-WIN-FVEAPI-QUERY-L1-1-0.DLL
    EXT-MS-WIN-GDI-CLIPPING-L1-1-0.DLL
    EXT-MS-WIN-GDI-DC-CREATE-L1-1-0.DLL
    EXT-MS-WIN-GDI-DC-L1-2-0.DLL
    EXT-MS-WIN-GDI-DC-L1-2-1.DLL
    EXT-MS-WIN-GDI-DEVCAPS-L1-1-0.DLL
    EXT-MS-WIN-GDI-DRAW-L1-1-0.DLL
    EXT-MS-WIN-GDI-DRAW-L1-1-1.DLL
    EXT-MS-WIN-GDI-DRAW-L1-1-2.DLL
    EXT-MS-WIN-GDI-DRAW-L1-1-3.DLL
    EXT-MS-WIN-GDI-FONT-L1-1-0.DLL
    EXT-MS-WIN-GDI-FONT-L1-1-1.DLL
    EXT-MS-WIN-GDI-FONT-L1-1-2.DLL
    EXT-MS-WIN-GDI-FONT-L1-1-3.DLL
    EXT-MS-WIN-GDI-GDIPLUS-L1-1-0.DLL
    EXT-MS-WIN-GDI-INTERNAL-DESKTOP-L1-1-0.DLL
    EXT-MS-WIN-GDI-INTERNAL-DESKTOP-L1-1-1.DLL
    EXT-MS-WIN-GDI-INTERNAL-DESKTOP-L1-1-2.DLL
    EXT-MS-WIN-GDI-INTERNAL-DESKTOP-L1-1-3.DLL
    EXT-MS-WIN-GDI-INTERNAL-DESKTOP-L1-1-4.DLL
    EXT-MS-WIN-GDI-METAFILE-L1-1-0.DLL
    EXT-MS-WIN-GDI-METAFILE-L1-1-1.DLL
    EXT-MS-WIN-GDI-METAFILE-L1-1-2.DLL
    EXT-MS-WIN-GDI-PATH-L1-1-0.DLL
    EXT-MS-WIN-GDI-PRINT-L1-1-0.DLL
    EXT-MS-WIN-GDI-PRIVATE-L1-1-0.DLL
    EXT-MS-WIN-GDI-RENDER-L1-1-0.DLL
    EXT-MS-WIN-GDI-WCS-L1-1-0.DLL
    EXT-MS-WIN-GPAPI-GROUPPOLICY-L1-1-0.DLL
    EXT-MS-WIN-GUI-DUI70-L1-1-0.DLL
    EXT-MS-WIN-IMM-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-APPCOMPAT-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-DATETIME-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-ERRORHANDLING-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-FILE-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-LOCALIZATION-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-PACKAGE-CURRENT-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-PACKAGE-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-PACKAGE-L1-1-2.DLL
    EXT-MS-WIN-KERNEL32-QUIRKS-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-QUIRKS-L1-1-1.DLL
    EXT-MS-WIN-KERNEL32-REGISTRY-L1-1-0.DLL
    EXT-MS-WIN-KERNEL32-SIDEBYSIDE-L1-1-0.DLL
    EXT-MS-WIN-KERNELBASE-PROCESSTHREAD-L1-1-0.DLL
    EXT-MS-WIN-KERNELBASE-PROCESSTHREAD-L1-1-1.DLL
    EXT-MS-WIN-MININPUT-INPUTHOST-L1-1-0.DLL
    EXT-MS-WIN-MPR-MULTIPLEPROVIDERROUTER-L1-1-0.DLL
    EXT-MS-WIN-MRMCORER-RESMANAGER-L1-1-0.DLL
    EXT-MS-WIN-NETWORKING-WCMAPI-L1-1-0.DLL
    EXT-MS-WIN-NETWORKING-WLANAPI-L1-1-0.DLL
    EXT-MS-WIN-NETWORKING-WLANSTORAGE-L1-1-0.DLL
    EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-0.DLL
    EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL
    EXT-MS-WIN-NTUSER-DC-ACCESS-EXT-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-DIALOGBOX-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-DRAW-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-DRAW-L1-1-1.DLL
    EXT-MS-WIN-NTUSER-DRAW-L1-1-2.DLL
    EXT-MS-WIN-NTUSER-GUI-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-KEYBOARD-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-MENU-L1-1-2.DLL
    EXT-MS-WIN-NTUSER-MESSAGE-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-MESSAGE-L1-1-1.DLL
    EXT-MS-WIN-NTUSER-MESSAGE-L1-1-2.DLL
    EXT-MS-WIN-NTUSER-MISC-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-MISC-L1-2-0.DLL
    EXT-MS-WIN-NTUSER-MISC-L1-5-0.DLL
    EXT-MS-WIN-NTUSER-MISC-L1-5-1.DLL
    EXT-MS-WIN-NTUSER-MOUSE-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-PRIVATE-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-PRIVATE-L1-1-1.DLL
    EXT-MS-WIN-NTUSER-PRIVATE-L1-2-0.DLL
    EXT-MS-WIN-NTUSER-PRIVATE-L1-3-1.DLL
    EXT-MS-WIN-NTUSER-PRIVATE-L1-3-2.DLL
    EXT-MS-WIN-NTUSER-PRIVATE-L1-3-3.DLL
    EXT-MS-WIN-NTUSER-RECTANGLE-EXT-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-ROTATIONMANAGER-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-SERVER-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-STRING-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-SYNCH-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-WINDOW-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-WINDOW-L1-1-1.DLL
    EXT-MS-WIN-NTUSER-WINDOW-L1-1-2.DLL
    EXT-MS-WIN-NTUSER-WINDOW-L1-1-3.DLL
    EXT-MS-WIN-NTUSER-WINDOWCLASS-L1-1-0.DLL
    EXT-MS-WIN-NTUSER-WINDOWSTATION-L1-1-0.DLL
    EXT-MS-WIN-ODBC-ODBC32-L1-1-0.DLL
    EXT-MS-WIN-OLE32-BINDCTX-L1-1-0.DLL
    EXT-MS-WIN-OLE32-IE-EXT-L1-1-0.DLL
    EXT-MS-WIN-OLE32-OLEAUTOMATION-L1-1-0.DLL
    EXT-MS-WIN-OLEACC-L1-1-1.DLL
    EXT-MS-WIN-OOBE-QUERY-L1-1-0.DLL
    EXT-MS-WIN-PRINTER-PRNTVPT-L1-1-0.DLL
    EXT-MS-WIN-PRINTER-PRNTVPT-L1-1-2.DLL
    EXT-MS-WIN-PRINTER-WINSPOOL-CORE-L1-1-0.DLL
    EXT-MS-WIN-PROFILE-EXTENDER-L1-1-0.DLL
    EXT-MS-WIN-PROFILE-USERENV-L1-1-0.DLL
    EXT-MS-WIN-PROFILE-USERENV-L1-1-1.DLL
    EXT-MS-WIN-RAS-RASAPI32-L1-1-0.DLL
    EXT-MS-WIN-RAS-TAPI32-L1-1-1.DLL
    EXT-MS-WIN-RDR-DAVHLPR-L1-1-0.DLL
    EXT-MS-WIN-REINFO-QUERY-L1-1-0.DLL
    EXT-MS-WIN-RESOURCEMANAGER-CRM-L1-2-0.DLL
    EXT-MS-WIN-RESOURCES-DEPLOYMENT-L1-1-0.DLL
    EXT-MS-WIN-RESOURCES-LANGUAGEOVERLAY-L1-1-0.DLL
    EXT-MS-WIN-RESOURCES-LANGUAGEOVERLAY-L1-1-1.DLL
    EXT-MS-WIN-RO-TYPERESOLUTION-L1-1-0.DLL
    EXT-MS-WIN-RPC-SSL-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-GDI-DEVCAPS-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-GDI-OBJECT-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-GDI-RGN-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-GDI-RGN-L1-1-1.DLL
    EXT-MS-WIN-RTCORE-MINUSER-INPUT-L1-1-1.DLL
    EXT-MS-WIN-RTCORE-MINUSER-INTERNAL-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-MINUSER-PRIVATE-EXT-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-MINUSER-PRIVATE-EXT-L1-1-1.DLL
    EXT-MS-WIN-RTCORE-NTUSER-CURSOR-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-DC-ACCESS-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-DPI-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-DPI-L1-2-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-DPI-L1-2-1.DLL
    EXT-MS-WIN-RTCORE-NTUSER-IAM-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-INTEGRATION-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-RAWINPUT-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-SYNCH-EXT-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-SYSCOLORS-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-SYSPARAMS-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-WINDOW-EXT-L1-1-0.DLL
    EXT-MS-WIN-RTCORE-NTUSER-WINDOW-EXT-L1-1-1.DLL
    EXT-MS-WIN-SECUR32-TRANSLATENAME-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-AUTHZ-HELPER-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-CAPAUTHZ-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-CAPAUTHZ-L1-1-1.DLL
    EXT-MS-WIN-SECURITY-CHAMBERS-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-CREDUI-INTERNAL-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-CREDUI-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-CREDUI-L1-1-1.DLL
    EXT-MS-WIN-SECURITY-CRYPTUI-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-CRYPTUI-L1-1-1.DLL
    EXT-MS-WIN-SECURITY-EFS-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-EFSWRT-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-EFSWRT-L1-1-1.DLL
    EXT-MS-WIN-SECURITY-NGC-LOCAL-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-SLC-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-WINSCARD-L1-1-0.DLL
    EXT-MS-WIN-SECURITY-WINSCARD-L1-1-1.DLL
    EXT-MS-WIN-SESSION-USERMGR-L1-1-0.DLL
    EXT-MS-WIN-SESSION-USERTOKEN-L1-1-0.DLL
    EXT-MS-WIN-SESSION-WINSTA-L1-1-0.DLL
    EXT-MS-WIN-SESSION-WTSAPI32-L1-1-0.DLL
    EXT-MS-WIN-SESSION-WTSAPI32-L1-1-1.DLL
    EXT-MS-WIN-SETUPAPI-INF-L1-1-0.DLL
    EXT-MS-WIN-SETUPAPI-INF-L1-1-1.DLL
    EXT-MS-WIN-SHELL-DIRECTORY-L1-1-0.DLL
    EXT-MS-WIN-SHELL-EMBEDDEDMODE-L1-1-0.DLL
    EXT-MS-WIN-SHELL-FILEPLACEHOLDER-L1-1-0.DLL
    EXT-MS-WIN-SHELL-SHELL32-L1-2-0.DLL
    EXT-MS-WIN-SHELL-SHLWAPI-L1-1-0.DLL
    EXT-MS-WIN-SHELL32-SHELLCOM-L1-1-0.DLL
    EXT-MS-WIN-SHELL32-SHELLFOLDERS-L1-1-0.DLL
    EXT-MS-WIN-SMBSHARE-BROWSERCLIENT-L1-1-0.DLL
    EXT-MS-WIN-STORAGE-SENSE-L1-1-0.DLL
    EXT-MS-WIN-STORAGE-SENSE-L1-2-0.DLL
    EXT-MS-WIN-SXS-OLEAUTOMATION-L1-1-0.DLL
    EXT-MS-WIN-TSF-MSCTF-L1-1-0.DLL
    EXT-MS-WIN-TSF-MSCTF-L1-1-1.DLL
    EXT-MS-WIN-UI-VIEWMANAGEMENT-L1-1-0.DLL
    EXT-MS-WIN-USP10-L1-1-0.DLL
    EXT-MS-WIN-WER-UI-L1-1-0.DLL
    EXT-MS-WIN-WER-XBOX-L1-1-0.DLL
    EXT-MS-WIN-WEVTAPI-EVENTLOG-L1-1-0.DLL
    EXT-MS-WIN-WINRT-DEVICE-ACCESS-L1-1-0.DLL
    EXT-MS-WIN-WINRT-STORAGE-L1-1-0.DLL
    EXT-MS-WIN-WLAN-ONEXUI-L1-1-0.DLL
    EXT-MS-WIN-WLAN-SCARD-L1-1-0.DLL
    EXT-MS-WIN-WPC-WEBFILTER-L1-1-0.DLL
    EXT-MS-WIN-WWAN-WWAPI-L1-1-0.DLL
    EXT-MS-WIN-WWAN-WWAPI-L1-1-1.DLL
    EXT-MS-WIN32-SUBSYSTEM-QUERY-L1-1-0.DLL
    EXT-MS-WINDOWSCORE-DEVICEINFO-L1-1-0.DLL
    FVESKYBACKUP.DLL
    HVSIFILETRUST.DLL
    IESHIMS.DLL
    NGCRECOVERY.DLL
    PDMUTILITIES.DLL
    WFDSCONMGR.DLL
    WPAXHOLDER.DLL
    

    Actually, with further review it seems like these are not issues..

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #12

      The API and EXT dlls should be provided by Windows so of no interest in this case.

      One thing that I have not seen, is the dll related to NIDAQmx.

      If I have seen correctly, what you need to do in Qt Creator is to change the PATH environment variable in the Run part of the Project panel and add the path to where the dll(s) are located.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      O 1 Reply Last reply
      1
      • SGaistS SGaist

        The API and EXT dlls should be provided by Windows so of no interest in this case.

        One thing that I have not seen, is the dll related to NIDAQmx.

        If I have seen correctly, what you need to do in Qt Creator is to change the PATH environment variable in the Run part of the Project panel and add the path to where the dll(s) are located.

        O Offline
        O Offline
        orsini29
        wrote on last edited by
        #13

        @SGaist

        I only outputted DLLs that had a yellow question mark next to them in the bottom portion of the screen where it says module. Although another thing of interest is the following, before I get to questions about your initial response.

        e24bc2dd-14f3-4e4f-90a0-4c433cda0b88-image.png

        1. The first three Qt DLLs have a yellow question mark, is this because they are provided at runtime? They sit within my installer directory within the data folder, which as well has the *.exe within it for deployment. Although the installer folder is different then my development folder, which is where I grabbed the *.exe and put into dependency walker.

        2. The DLL NICAIU.dll is related to NIDAQ, which I should have specified in my original response. Although it seems like from a quick google search there are many NIDAQmx dlls...

        Then for your original statement, I already have

        C:\Windows\System32
        

        specified within the Path variable. Although, there are many things specified within the path variable, and I am unsure if these can cause any issues, but they have not as of now since the project runs correctly without simply calling these NIDAQ functions.

        1 Reply Last reply
        0
        • O Offline
          O Offline
          orsini29
          wrote on last edited by
          #14

          Actually this is interesting... I used the *.exe from the installed version of the program on my local computer, and this is what I got

          51d2d43d-eb25-4973-bb7a-5bf2015b15ce-image.png

          cad32442-f2cd-4398-8c33-5d879d21bf9d-image.png

          796c2192-9c5e-4a66-a102-e2d9fcb039ea-image.png

          I will be honest...I do not know how to decipher this, I assume it means something is not being fetched correctly with the DLLs?

          1 Reply Last reply
          0
          • hskoglundH Offline
            hskoglundH Offline
            hskoglund
            wrote on last edited by
            #15

            Hi, for Windows 10 the downloaded Ni-DAQmx sofrware can be either 32-bits or 64-bits flavored. Since you're using a 32-bit Qt version the Ni-DAQ files should have the same bitness.

            For 32-bit apps they load their system dlls from C:\Windows\SysWOW64 directory but in the trace output above they're loading them from C:\Windows\System32 (which is where the 64-bits version of the system dlls are stored).

            Usually this 32-bit/64-bit mixup should return error 0x0000007b and not 0xc0000142 so I'm not sure this is the problem but you could check anyway :-)

            O 1 Reply Last reply
            2
            • hskoglundH hskoglund

              Hi, for Windows 10 the downloaded Ni-DAQmx sofrware can be either 32-bits or 64-bits flavored. Since you're using a 32-bit Qt version the Ni-DAQ files should have the same bitness.

              For 32-bit apps they load their system dlls from C:\Windows\SysWOW64 directory but in the trace output above they're loading them from C:\Windows\System32 (which is where the 64-bits version of the system dlls are stored).

              Usually this 32-bit/64-bit mixup should return error 0x0000007b and not 0xc0000142 so I'm not sure this is the problem but you could check anyway :-)

              O Offline
              O Offline
              orsini29
              wrote on last edited by orsini29
              #16

              @hskoglund

              Interesting... I will switch I assume the PATH variable within the Qt environment to add(?)

              C:\Windows\SysWOW64
              

              or should I just append this path at the end of the PATH variable? Thanks again, hopefully it works!

              Also, why is it that 32 bit DLLs reside in SysWOW64, and 64 bit DLLs reside in System32, is this not confusing to anyone else :)

              Edit: also, I do not think changing my PATH variable within Qt is doing much.. I changed it to the following

              C:\Qt\5.15.9\mingw81_32\bin;
              C:\Qt\Tools\mingw810_32\bin;
              C:\Qt\5.15.9\mingw81_32\bin;
              C:\Qt\Tools\mingw810_32\bin;
              C:\Program Files\Common Files\Oracle\Java\javapath;
              C:\Program Files(x86)\VMware\VMwarePlayer\bin\;
              C:\Qt\Tools\mingw810_32\bin\;
              C:\Windows;
              C:\Windows\System32\Wbem;
              C:\Windows\System32\WindowsPowerShell\v1.0\;
              C:\Windows\System32\OpenSSH\;
              C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;
              C:\Program Files (x86)\Vim\vim82;
              C:\Users\Sorsini\apache-maven-3.8.6\bin;
              C:\Program Files\Git\cmd;
              C:\ProgramFiles\dotnet\;
              C:\Users\Sorsini\AppData\Local\Microsoft\WindowsApps;
              C:\Users\Sorsini\AppData\Local\Programs\Microsoft VSCode\bin;
              C:\Users\Sorsini\AppData\Local\Programs\mongosh\;
              "C:\Program Files;C:\Winnt;C:\Winnt\System32";
              C:\Qt\Tools\mingw810_32\bin\;
              C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2022.2.3\bin;
              C:\Windows\SysWOW64; //added this
              C:\Windows\System32
              

              and whenever I run the installed program, after packaging it through Qt, it still says on dependency walker it is receiving the DLLs from System32

              1 Reply Last reply
              0
              • hskoglundH Offline
                hskoglundH Offline
                hskoglund
                wrote on last edited by
                #17

                Hi, what happens if you try building your app with the MinGW 64-bit compiler?

                O 2 Replies Last reply
                1
                • hskoglundH hskoglund

                  Hi, what happens if you try building your app with the MinGW 64-bit compiler?

                  O Offline
                  O Offline
                  orsini29
                  wrote on last edited by
                  #18

                  @hskoglund

                  I tried to do that earlier today, but I think there is a configuration issue with my MinGW 62-bit compiler. I looked at the properties for it and for the qmake (if I remember correctly), it is accessing the MinGW 32-bit compiler rather than the 62-bit one. I do not have access to my PC until Monday, so I can give some more information on what that configuration looks like exactly. But I was having troubles trying to set the 62 but one up earlier today.

                  I’ll give a reply Monday with what my configurations look like, thanks again for trying to help me out. Means a lot, I’ve been banging my head against the wall on this issue for a little over a week now

                  1 Reply Last reply
                  0
                  • hskoglundH hskoglund

                    Hi, what happens if you try building your app with the MinGW 64-bit compiler?

                    O Offline
                    O Offline
                    orsini29
                    wrote on last edited by orsini29
                    #19

                    @hskoglund

                    I set up the MinGW 64 bit compiler and now I'm receiving the

                    undefined reference to DAQmxCreateTask
                    

                    I rechecked my *.pro file, and I am using Fwlib64, and that is pulling all the functions correctly, without any errors. I am referencing the DLL/LIB/*.H files the same within the *.pro file, and include them both in the *.cpp file I am referencing them in. I decided to see if upgrading to Qt 6.* would make any difference? I was originally on Qt 5.15.9 because it was easier to make 32 bit builds on, which I originally thought was the best route for this project, but I will change if I can get this other NIDAQ library working on the 64-bit build. Any suggestions on other things to look at for the above error? Thanks again.

                    This is the compiler error I am receiving, not sure if this will give a little bit more insight...

                    C:/Qt/Tools/mingw1120_64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: debug/mainwindow.o: in function `MainWindow::MainWindow(QWidget*)':
                    C:\Users\Sorsini\Documents\Qt Prototypes\Test\test/mainwindow.cpp:13: undefined reference to `DAQmxCreateTask'
                    collect2.exe: error: ld returned 1 exit status
                    mingw32-make[1]: Leaving directory 'C:/Users/Sorsini/Documents/Qt Prototypes/Test/test'
                    mingw32-make[1]: *** [Makefile.Debug:74: debug/test.exe] Error 1
                    mingw32-make: *** [Makefile:45: debug] Error 2
                    11:01:36: The process "C:\Qt\Tools\mingw1120_64\bin\mingw32-make.exe" exited with code 2.
                    Error while building/deploying project test (kit: Desktop Qt 6.3.2 MinGW 64-bit)
                    When executing step "Make"
                    
                    1 Reply Last reply
                    0
                    • hskoglundH Offline
                      hskoglundH Offline
                      hskoglund
                      wrote on last edited by
                      #20

                      If you rebuild in Release mode (instead of Debug) you still get the same error?

                      O 1 Reply Last reply
                      1
                      • hskoglundH hskoglund

                        If you rebuild in Release mode (instead of Debug) you still get the same error?

                        O Offline
                        O Offline
                        orsini29
                        wrote on last edited by
                        #21

                        @hskoglund

                        I downloaded MSVC 2019 32 and 64 bit compilers just to see if anything will change and I received the following

                        Error with MSVC 64 bit
                        dd08b1e5-2870-4f32-a5a0-c42896303062-image.png ![5ec5dd91-6176-4ec9-862b-ba0fd5fd146d-image.png]

                        a6a455b9-05eb-472f-a688-4910cddfa651-image.png

                        Error with MSVC 32 bit
                        34f8a07d-e453-4469-a8c8-8c7b27829a94-image.png

                        093ee15c-e7bd-476a-9926-9d8d7502cf82-image.png

                        As for building in release mode, I received the same error as above for both of the compilers. This is the same for MinGW 32/64 as well, except I received the "Application was unable to start correctly (0xc0000142)" error.

                        1 Reply Last reply
                        0
                        • hskoglundH Offline
                          hskoglundH Offline
                          hskoglund
                          wrote on last edited by
                          #22

                          Hi, if you build one of Qt's example apps, like the "Application Example", does it run correctly? (Jiust want to check that your compiler toolchains are up to scratch).

                          O 1 Reply Last reply
                          1
                          • hskoglundH hskoglund

                            Hi, if you build one of Qt's example apps, like the "Application Example", does it run correctly? (Jiust want to check that your compiler toolchains are up to scratch).

                            O Offline
                            O Offline
                            orsini29
                            wrote on last edited by
                            #23

                            @hskoglund

                            Yup, I just compiled on of my former applications and it compiled okay

                            1 Reply Last reply
                            0
                            • hskoglundH Offline
                              hskoglundH Offline
                              hskoglund
                              wrote on last edited by
                              #24

                              Ok the compiler(s) work with a vanilla Qt program with no external libs dependencies.

                              So what happens if you reduce the number of external libs you are depending on: right now you are trying to link with both Fwlib32.lib and IDAQmx.lib.
                              (If one of them has another bitness (32 instead of 64 or the other way around) that's enough to cause those linker errors above.)

                              Could you try a smaller program that is only dependent on one of them? I.e. links only with just one of them? Either only Fwlib32.lib or only NIDAQmx.lib?

                              O 2 Replies Last reply
                              1
                              • hskoglundH hskoglund

                                Ok the compiler(s) work with a vanilla Qt program with no external libs dependencies.

                                So what happens if you reduce the number of external libs you are depending on: right now you are trying to link with both Fwlib32.lib and IDAQmx.lib.
                                (If one of them has another bitness (32 instead of 64 or the other way around) that's enough to cause those linker errors above.)

                                Could you try a smaller program that is only dependent on one of them? I.e. links only with just one of them? Either only Fwlib32.lib or only NIDAQmx.lib?

                                O Offline
                                O Offline
                                orsini29
                                wrote on last edited by orsini29
                                #25

                                @hskoglund

                                So the above error messages are with a program just linking to NIDAQmx.lib, I put the code for my *.pro and *.cpp below

                                test.pro

                                QT       += core gui
                                QT       += widgets
                                
                                greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
                                
                                CONFIG += c++11
                                
                                # You can make your code fail to compile if it uses deprecated APIs.
                                # In order to do so, uncomment the following line.
                                #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000    # disables all the APIs deprecated before Qt 6.0.0
                                
                                SOURCES += \
                                    main.cpp \
                                    mainwindow.cpp
                                
                                HEADERS += \
                                    NIDAQmx.h \
                                    mainwindow.h
                                
                                FORMS += \
                                    mainwindow.ui
                                
                                # Default rules for deployment.
                                qnx: target.path = /tmp/$${TARGET}/bin
                                else: unix:!android: target.path = /opt/$${TARGET}/bin
                                !isEmpty(target.path): INSTALLS += target
                                
                                LIBS += \
                                    ./NIDAQmx.lib
                                

                                mainwindow.cpp

                                #include "mainwindow.h"
                                #include "ui_mainwindow.h"
                                #include "./NIDAQmx.h"
                                
                                MainWindow::MainWindow(QWidget *parent): QMainWindow(parent), ui(new Ui::MainWindow) {
                                    ui->setupUi(this);
                                
                                    TaskHandle taskHandle;
                                    DAQmxCreateTask("", &taskHandle);
                                
                                }
                                
                                MainWindow::~MainWindow() {
                                    delete ui;
                                }
                                

                                The error messages I receive are as above with the screenshots.

                                I also ran this in release mode, as well as debug mode too.

                                When compiling the application without making any calls to a method within the library (ex: DAQmxCreateTask(...)), the project will compile perfectly fine. Though once I uncomment the line, it gives me that same error

                                1 Reply Last reply
                                0
                                • hskoglundH hskoglund

                                  Ok the compiler(s) work with a vanilla Qt program with no external libs dependencies.

                                  So what happens if you reduce the number of external libs you are depending on: right now you are trying to link with both Fwlib32.lib and IDAQmx.lib.
                                  (If one of them has another bitness (32 instead of 64 or the other way around) that's enough to cause those linker errors above.)

                                  Could you try a smaller program that is only dependent on one of them? I.e. links only with just one of them? Either only Fwlib32.lib or only NIDAQmx.lib?

                                  O Offline
                                  O Offline
                                  orsini29
                                  wrote on last edited by orsini29
                                  #26

                                  @hskoglund

                                  I started to dive deeper into the NI folder from the installation and found some *.h and *.lib files that were not in the original path mentioned above, I added these in because they actually have a lib32 and lib64 folder containing the libraries. Upon adding the 32 bit libraries I edited my *.pro file, and now instead of receiving any application/compile output console errors, I am just receiving the "Application was unable to start correctly" error again...

                                  So I ran the new cleaned/rebuilt application within Dependency Walker, and I noticed that the NICAIU.dll is now not read (assuming that the red square denotes an issue), as seen below

                                  5d0256ae-b60c-4f3a-8699-4a5eea2a7a01-image.png

                                  Although, QT5WIDGETSD.DLL and QT5CORED.DLL have the question mark next to them. I do not think this is where the issue is stemming from though..Also it is still fetching System32 dlls rather than the SysWOW64 dlls, although I am compiling the application with the MSVC 32 bit. When I tried to compile with the 64 bit libs, I received the same error message although dependency walker showed red squares next to all the DLLs.

                                  When I press F7 within Dependency Walker to profile the .exe, I received the errors saying these two DLLs are unavailable.
                                  76c25342-4327-4633-9461-3dada49cefc8-image.png

                                  I went into the MSVC2019 bin and grabbed them explicitly and moved them into the debug folder with the dummy.exe
                                  0b7b8e05-9cb6-4176-92eb-cc77789b5244-image.png

                                  and received this on dependency walker, which looks better/more promising.

                                  Then I being profiling again, and I do not receive any error messages but Dependency Walker stops responding and will not load anything after a short bit of time.

                                  The logging window when Dependency Walker crashes is looking like this
                                  88d99d9f-a2bc-4e5d-a0b9-b8a4a1fc5eef-image.png

                                  jsulmJ 1 Reply Last reply
                                  0
                                  • O orsini29

                                    @hskoglund

                                    I started to dive deeper into the NI folder from the installation and found some *.h and *.lib files that were not in the original path mentioned above, I added these in because they actually have a lib32 and lib64 folder containing the libraries. Upon adding the 32 bit libraries I edited my *.pro file, and now instead of receiving any application/compile output console errors, I am just receiving the "Application was unable to start correctly" error again...

                                    So I ran the new cleaned/rebuilt application within Dependency Walker, and I noticed that the NICAIU.dll is now not read (assuming that the red square denotes an issue), as seen below

                                    5d0256ae-b60c-4f3a-8699-4a5eea2a7a01-image.png

                                    Although, QT5WIDGETSD.DLL and QT5CORED.DLL have the question mark next to them. I do not think this is where the issue is stemming from though..Also it is still fetching System32 dlls rather than the SysWOW64 dlls, although I am compiling the application with the MSVC 32 bit. When I tried to compile with the 64 bit libs, I received the same error message although dependency walker showed red squares next to all the DLLs.

                                    When I press F7 within Dependency Walker to profile the .exe, I received the errors saying these two DLLs are unavailable.
                                    76c25342-4327-4633-9461-3dada49cefc8-image.png

                                    I went into the MSVC2019 bin and grabbed them explicitly and moved them into the debug folder with the dummy.exe
                                    0b7b8e05-9cb6-4176-92eb-cc77789b5244-image.png

                                    and received this on dependency walker, which looks better/more promising.

                                    Then I being profiling again, and I do not receive any error messages but Dependency Walker stops responding and will not load anything after a short bit of time.

                                    The logging window when Dependency Walker crashes is looking like this
                                    88d99d9f-a2bc-4e5d-a0b9-b8a4a1fc5eef-image.png

                                    jsulmJ Offline
                                    jsulmJ Offline
                                    jsulm
                                    Lifetime Qt Champion
                                    wrote on last edited by
                                    #27

                                    @orsini29 said in Qt 5.15.9, MinGW 32-bit compiler, "Application was unable to start correctly (0xc0000142)".:

                                    LNK4272: library machine type 'x86' conflicts with target machine type 'x64'

                                    You are mixing 32bit and 64bit. This will not work. If you want to build 64bit application then all libraries used have to also be 64bit.

                                    https://forum.qt.io/topic/113070/qt-code-of-conduct

                                    O 1 Reply Last reply
                                    2
                                    • jsulmJ jsulm

                                      @orsini29 said in Qt 5.15.9, MinGW 32-bit compiler, "Application was unable to start correctly (0xc0000142)".:

                                      LNK4272: library machine type 'x86' conflicts with target machine type 'x64'

                                      You are mixing 32bit and 64bit. This will not work. If you want to build 64bit application then all libraries used have to also be 64bit.

                                      O Offline
                                      O Offline
                                      orsini29
                                      wrote on last edited by orsini29
                                      #28

                                      @jsulm

                                      Yeah I realized that by using this 64 bit compiler, I was trying to see if maybe the 64 bit would work because the bitness of the library was unknown, until I did a deeper dive into the folder structure and found another set of *.libs that told me which bitness they were with a parent folder named lib32 or lib64. Although, even building with the 32 bit lib I still receive the error marked on the question.

                                      "Application was unable to start correctly (0xc0000142)"

                                      jsulmJ 1 Reply Last reply
                                      0
                                      • O orsini29

                                        @jsulm

                                        Yeah I realized that by using this 64 bit compiler, I was trying to see if maybe the 64 bit would work because the bitness of the library was unknown, until I did a deeper dive into the folder structure and found another set of *.libs that told me which bitness they were with a parent folder named lib32 or lib64. Although, even building with the 32 bit lib I still receive the error marked on the question.

                                        "Application was unable to start correctly (0xc0000142)"

                                        jsulmJ Offline
                                        jsulmJ Offline
                                        jsulm
                                        Lifetime Qt Champion
                                        wrote on last edited by
                                        #29

                                        @orsini29 said in Qt 5.15.9, MinGW 32-bit compiler, "Application was unable to start correctly (0xc0000142)".:

                                        "Application was unable to start correctly (0xc0000142)"

                                        This is another error. Now your app is building but not starting. I guess the library is not found. You can either copy it into the same folder (build folder) where you app executable is or set PATH variable in Run environment in QtCreator, so that it points to the folder where the lib is.

                                        https://forum.qt.io/topic/113070/qt-code-of-conduct

                                        1 Reply Last reply
                                        1
                                        • O Offline
                                          O Offline
                                          orsini29
                                          wrote on last edited by
                                          #30

                                          Fixed the issue.

                                          Turns out it was something with my laptop. I had gotten a secondary laptop that had the same environment, all Windows 10, downloaded the NIDAQmx software, and it connected to my Qt application perfectly fine. Very odd, unsure why this happened. I went about the installation process the same on both laptops.

                                          I hope nobody ever has to go through this issue again, but if you are, might want to try on a new laptop..Worked for me!

                                          1 Reply Last reply
                                          0

                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Users
                                          • Groups
                                          • Search
                                          • Get Qt Extensions
                                          • Unsolved