Issue Details

When calling a LabWindows/CVI-compiled .dll file from TestStand or LabVIEW, I see the following error message:

Could not load DLL or external library '<DLL PATH>'.

This DLL requires the following DLLs which could not be found or loaded:
api-ms-win-core-console-l1-1-0.dll (Not Found)
api-ms-win-core-datetime-l1-1-1.dll (Not Found)
api-ms-win-core-debug-l1-1-1.dll (Not Found)
api-ms-win-core-errorhandling-l1-1-1.dll (Not Found)
api-ms-win-core-fibers-l1-1-1.dll (Not Found)
api-ms-win-core-file-l1-2-1.dll (Not Found)
api-ms-win-core-handle-l1-1-0.dll (Not Found)
api-ms-win-core-heap-l1-2-0.dll (Not Found)
api-ms-win-core-localization-l1-2-1.dll (Not Found)
api-ms-win-core-libraryloader-l1-2-0.dll (Not Found)
api-ms-win-core-memory-l1-1-2.dll (Not Found)
api-ms-win-core-namedpipe-l1-2-0.dll (Not Found)
api-ms-win-core-processenvironment-l1-2-0.dll (Not Found)
api-ms-win-core-processthreads-l1-1-2.dll (Not Found)
api-ms-win-core-profile-l1-1-0.dll (Not Found)
api-ms-win-core-string-l1-1-0.dll (Not Found)
api-ms-win-core-synch-l1-2-0.dll (Not Found)
api-ms-win-core-sysinfo-l1-2-1.dll (Not Found)
api-ms-win-core-util-l1-1-0.dll (Not Found)
api-ms-win-eventing-provider-l1-1-0.dll (Not Found)
api-ms-win-eventing-controller-l1-1-0.dll (Not Found)
api-ms-win-eventing-consumer-l1-1-0.dll (Not Found)
api-ms-win-core-interlocked-l1-2-0.dll (Not Found)
api-ms-win-core-io-l1-1-1.dll (Not Found)
api-ms-win-core-registry-l1-1-0.dll (Not Found)
api-ms-win-core-string-obsolete-l1-1-0.dll (Not Found)
api-ms-win-core-heap-obsolete-l1-1-0.dll (Not Found)
api-ms-win-core-timezone-l1-1-0.dll (Not Found)
api-ms-win-core-threadpool-legacy-l1-1-0.dll (Not Found)
api-ms-win-security-base-l1-2-0.dll (Not Found)
api-ms-win-core-apiquery-l1-1-0.dll (Not Found)
api-ms-win-core-crt-l1-1-0.dll (Not Found)
api-ms-win-core-crt-l2-1-0.dll (Not Found)
api-ms-win-core-xstate-l2-1-0.dll (Not Found)
api-ms-win-core-delayload-l1-1-1.dll (Not Found)
api-ms-win-security-lsalookup-l1-1-1.dll (Not Found)
api-ms-win-security-lsapolicy-l1-1-0.dll (Not Found)
api-ms-win-core-threadpool-l1-2-0.dll (Not Found)
api-ms-win-core-wow64-l1-1-0.dll (Not Found)
api-ms-win-service-core-l1-1-1.dll (Not Found)
api-ms-win-service-core-l1-1-2.dll (Not Found)
api-ms-win-service-management-l1-1-0.dll (Not Found)
api-ms-win-service-management-l2-1-0.dll (Not Found)
api-ms-win-service-private-l1-1-2.dll (Not Found)
api-ms-win-service-private-l1-1-1.dll (Not Found)
api-ms-win-service-winsvc-l1-2-0.dll (Not Found)
api-ms-win-security-base-private-l1-1-1.dll (Not Found)
api-ms-win-core-registry-l1-1-1.dll (Not Found)
api-ms-win-core-rtlsupport-l1-2-0.dll (Not Found)
api-ms-win-core-processthreads-l1-1-3.dll (Not Found)
api-ms-win-core-heap-l2-1-0.dll (Not Found)
api-ms-win-core-enclave-l1-1-0.dll (Not Found)
api-ms-win-core-synch-l1-2-1.dll (Not Found)
api-ms-win-core-file-l1-2-2.dll (Not Found)
api-ms-win-core-job-l1-1-0.dll (Not Found)
api-ms-win-core-threadpool-private-l1-1-0.dll (Not Found)
api-ms-win-core-libraryloader-l1-2-2.dll (Not Found)
api-ms-win-core-libraryloader-l2-1-0.dll (Not Found)
api-ms-win-core-namedpipe-l1-2-2.dll (Not Found)
api-ms-win-core-datetime-l1-1-2.dll (Not Found)
api-ms-win-core-sysinfo-l1-2-3.dll (Not Found)
api-ms-win-core-localization-private-l1-1-0.dll (Not Found)
api-ms-win-core-processsnapshot-l1-1-0.dll (Not Found)
api-ms-win-core-errorhandling-l1-1-3.dll (Not Found)
api-ms-win-core-comm-l1-1-0.dll (Not Found)
api-ms-win-core-wow64-l1-1-1.dll (Not Found)
api-ms-win-core-realtime-l1-1-0.dll (Not Found)
api-ms-win-core-processtopology-l1-2-0.dll (Not Found)
api-ms-win-core-namespace-l1-1-0.dll (Not Found)
api-ms-win-core-file-l2-1-2.dll (Not Found)
api-ms-win-core-file-l2-1-1.dll (Not Found)
api-ms-win-core-localization-l2-1-0.dll (Not Found)
api-ms-win-core-normalization-l1-1-0.dll (Not Found)
api-ms-win-core-fibers-l2-1-1.dll (Not Found)
api-ms-win-core-sidebyside-l1-1-0.dll (Not Found)
api-ms-win-core-appcompat-l1-1-1.dll (Not Found)
api-ms-win-core-windowserrorreporting-l1-1-0.dll (Not Found)
api-ms-win-core-console-l2-1-0.dll (Not Found)
api-ms-win-core-psapi-l1-1-0.dll (Not Found)
api-ms-win-core-psapi-ansi-l1-1-0.dll (Not Found)
api-ms-win-security-appcontainer-l1-1-0.dll (Not Found)
api-ms-win-security-audit-l1-1-1.dll (Not Found)
api-ms-win-core-perfcounters-l1-1-0.dll (Not Found)
api-ms-win-core-string-l2-1-0.dll (Not Found)
api-ms-win-core-privateprofile-l1-1-1.dll (Not Found)
api-ms-win-core-atoms-l1-1-0.dll (Not Found)
api-ms-win-core-localization-obsolete-l1-3-0.dll (Not Found)
api-ms-win-core-stringansi-l1-1-0.dll (Not Found)
api-ms-win-core-kernel32-private-l1-1-1.dll (Not Found)
api-ms-win-core-kernel32-legacy-l1-1-1.dll (Not Found)
api-ms-win-core-appinit-l1-1-0.dll (Not Found)
api-ms-win-gdi-internal-uap-l1-1-0.dll (Not Found)
api-ms-win-eventing-classicprovider-l1-1-0.dll (Not Found)
api-ms-win-devices-config-l1-1-1.dll (Not Found)
api-ms-win-mm-time-l1-1-0.dll (Not Found)
api-ms-win-mm-mme-l1-1-0.dll (Not Found)
api-ms-win-mm-misc-l1-1-1.dll (Not Found)
api-ms-win-core-path-l1-1-0.dll (Not Found)
api-ms-win-core-kernel32-private-l1-1-2.dll (Not Found)
api-ms-win-eventing-obsolete-l1-1-0.dll (Not Found)
api-ms-win-security-activedirectoryclient-l1-1-0.dll (Not Found)
api-ms-win-core-string-l2-1-1.dll (Not Found)
api-ms-win-core-localization-l1-2-2.dll (Not Found)
api-ms-win-core-version-l1-1-0.dll (Not Found)
api-ms-win-core-shlwapi-obsolete-l1-2-0.dll (Not Found)
api-ms-win-core-shlwapi-legacy-l1-1-0.dll (Not Found)
api-ms-win-core-kernel32-legacy-l1-1-5.dll (Not Found)
api-ms-win-core-url-l1-1-0.dll (Not Found)
api-ms-win-core-registryuserspecific-l1-1-0.dll (Not Found)
api-ms-win-storage-exports-internal-l1-1-0.dll (Not Found)
api-ms-win-storage-exports-external-l1-1-0.dll (Not Found)
api-ms-win-shell-shellcom-l1-1-0.dll (Not Found)
api-ms-win-shell-shellfolders-l1-1-0.dll (Not Found)
api-ms-win-core-job-l2-1-0.dll (Not Found)
api-ms-win-security-capability-l1-1-0.dll (Not Found)
api-ms-win-core-com-l1-1-1.dll (Not Found)
api-ms-win-crt-string-l1-1-0.dll (Not Found)
api-ms-win-crt-runtime-l1-1-0.dll (Not Found)
api-ms-win-crt-private-l1-1-0.dll (Not Found)
api-ms-win-core-winrt-error-l1-1-1.dll (Not Found)
api-ms-win-core-com-midlproxystub-l1-1-0.dll (Not Found)
api-ms-win-core-winrt-string-l1-1-0.dll (Not Found)
api-ms-win-security-sddl-l1-1-0.dll (Not Found)
api-ms-win-core-com-private-l1-1-0.dll (Not Found)
api-ms-win-core-com-private-l1-1-1.dll (Not Found)
api-ms-win-core-quirks-l1-1-0.dll (Not Found)
api-ms-win-core-psm-key-l1-1-0.dll (Not Found)
api-ms-win-crt-locale-l1-1-0.dll (Not Found)
api-ms-win-core-synch-l1-1-0.dll (Not Found)
api-ms-win-core-processthreads-l1-1-0.dll (Not Found)
api-ms-win-core-sysinfo-l1-2-0.dll (Not Found)
api-ms-win-core-file-l1-1-0.dll (Not Found)
api-ms-win-core-file-l2-1-0.dll (Not Found)
api-ms-win-core-file-l1-2-0.dll (Not Found)
api-ms-win-core-errorhandling-l1-1-0.dll (Not Found)
api-ms-win-core-localization-l1-2-0.dll (Not Found)
api-ms-win-core-rtlsupport-l1-1-0.dll (Not Found)
api-ms-win-core-processthreads-l1-1-1.dll (Not Found)
api-ms-win-core-debug-l1-1-0.dll (Not Found)
api-ms-win-core-sysinfo-l1-1-0.dll (Not Found)
api-ms-win-core-libraryloader-l1-1-0.dll (Not Found)
api-ms-win-core-interlocked-l1-1-0.dll (Not Found)
api-ms-win-core-versionansi-l1-1-0.dll (Not Found)
Tkdpo2k3k4k.dll (Not Found)
niHSDIO.dll (Not Found)
niFgen_32.dll (Not Found)
ke24xx.dll (Not Found)
hpe435xb_32.dll (Not Found)
BUSAPI32.dll (Not Found)
AgtN330X_32.dll (Not Found)
pipx40_32.DLL (Not Found)

Solution

This error usually happens when the software calling the LabWindows/CVI-compiled DLL is not able to load a missing DLL or missing dependencies of the DLL on the deployment system. There are several steps you can try to troubleshoot the issue and find the source of the issue:

• Check that all files involved in the LabWindows/CVI project have been compiled for the specific operating system (e.g. Windows 7, Windows 10). If you have updated the OS of your system, NI recommends that you recompile the LabWindows/CVI project so that you can verify that all the dependencies are available on the specific OS. If the LabWindows/CVI DLL being called was built with another OS version, the library files being called may not exist in the different OS version regardless of NI products.
• Open the software calling the DLL (i.e. TestStand, LabVIEW, etc) as administrator. This step is recommended even if you have local admin privileges. This step is important because depending on the system security configuration the program calling the DLL may not have the appropriate privileges to access the LabWindows/CVI DLL or its dependencies.
• Make sure that software drivers and third-party software used by the LabWindows/CVI DLL are installed on the target PC. You also need to verify that the software installed is compatible with the operating system and the same version as the one used in the development computer.
• If your LabWindows/CVI DLL references other DLLs, make sure that they are located at the expected location and that have the correct access permissions. As a test, you can copy the DLL being used by the LabWindows/CVI DLL into the same directory to see if it can be found by the main program/DLL.
• If you are using third-party software within the LabWindows/CVI project and it runs correctly on the development environment but not in a deployment system, it is probable that there are missing dependencies. We recommend that you use a software tool that allows you to track missing dependencies to identify the missing software. One available open-source program to track dependencies is the following: Dependencies - An open-source modern Dependency Walker (External Link). 

Additional Information

This appears to occur when the LabWindows/CVI code used to build the DLL involves libraries or dependencies that were compiled for an older Windows operating system like Windows XP.
Many C/C++ DLLs developed with Visual Studio that could be a dependency of the LabWindows/CVI project if using third-party software rely on runtimes or drivers that are installed on the development system. One of these dependencies is the Visual C++ Redistributable for Visual Studio, you can check that the same version is installed on the target PC.