LabVIEW Executable Runs on Development Computer but Not Deployment Computer

Updated Aug 14, 2019

Reported In


  • LabVIEW
  • LabVIEW Application Builder Module
  • LabVIEW Run-Time Engine

Issue Details

  • I have created an executable of my LabVIEW application using the Application Builder and it works fine on my PC but doesn't work on my colleague's PC. Should I create an installer instead? 
  • I sent an LabVIEW executable to a customer but my customer is unable to run it on his computer. Dialog box pops up with "LabVIEW: Resource not found." How can my customer run my executable?
  • I have downloaded the LabVIEW Run-Time Engine compatible with my system and executable, but the program still will not run on my target machine.


A system must have all required application dependencies and their corresponding versions. When utilizing NI hardware, the required hardware drivers must be installed. Example dependencies include LabVIEW Run-Time, DAQmx, and VISA. For maximum compatibility, distributions should be compiled on the same operating system they are being deployed on.

One way to make sure we have all the required dependencies is create an Installer instead of an executable.

Additional Information

Application Builder can create two unique types of distributions: Stand-alone Applications and Installers. 

Stand-alone Applications

  • Stand-alone applications provide users with executable versions of VIs. (Windows) utilize  .exe extension while  (Mac OS) utilize .app extension. 
  • Stand-alone applications do not include the applications required dependencies i.e. run-time engines and hardware drivers. 

Installers (Windows Only)

  • Create an installer  to distribute an application that packages the application and required dependencies i.e. run-time engines and hardware drivers. 
  • Installers allow for custom installation graphics.


Not Helpful