Library Not Found or Failed to Load When Importing DLL or Using a VI in LabVIEW

Issue Details

• When attempting to use a VI included in a LabVIEW toolkit or add-on, such as the Vision Development Module, the VI cannot be executed, and the following error message is displayed. 
• After importing my DLL into a LabVIEW VI using a Call Library Function Node, the run arrow is broken, and I receive the following errors.
  
  The library specified for this node cannot be found or cannot be loaded. Right-click the Call Library Function node and select Configure, then choose the correct library name or path.
   

Solution

This issue can occur due to multiple reasons including, but not limited to, an incorrect file path to the Dynamic Link Library (DLL), dependencies required by the DLL not being located, or corrupted software components. Try the troubleshooting steps below to resolve these errors.
 

• Right-click the Call Library Function Node (CLFN) used to call the DLL and ensure that the specified location of the DLL is correct.
  • Check if the CLFN uses absolute or relative paths.
• Confirm the bitness of the DLL matches the bitness of the LabVIEW version you are using. If you try to run a 32-bit DLL from LabVIEW 64-bit or vice-versa, you might encounter this error.
• ​Load your DLL into a dependency checker program that will make sure that you are not missing any dependencies. 
  • There is an open source dependency checker on GitHub that can be useful for this, although it is not the only software that would work for checking dependencies.
  • To solve a missing dependency problem, you will need to place the dependency in the correct location or statically include the dependency when you build the DLL. The particular methods for doing this will depend on your programming language and particular application.
• If possible, contact the developer of the DLL and ask whether there are dependencies that require the installation of additional software. 
• Ensure that your Windows account has permission to read the file. The external link Access Control Overview from Microsoft contains information about managing permissions.
• This issue can also occur after updating your Windows Operating System. Please make sure all of the dependencies of your DLL (e.g., FTD2xx.dll) are not removed after the Windows update.
• Make sure no other program like Source Code Control or anti-virus are blocking the DLL.
• If the issue occurs when attempting to use a VI included in a LabVIEW toolkit or add-on, remove the NI software and reinstall it using the NI Package Manager. 

Additional Information

Windows 64-bit does not support mixed 64-bit/32-bit processes, that is why the bitness of the DLL and LabVIEW needs to match. Windows 10/11 uses two directories for program installations, 64-bit programs are located in the Program Files directory and 32-bit programs are located in the Program Files (x86) directory.