Why Does My LabVIEW Executable Not Work On Another Computer

Updated Nov 9, 2018

Reported In


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


  • NI-DAQmx

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 colleagues PC. Have I created the correct product or should I create an installer? 

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?


A PC must have all the required toolkits, drivers and run-time engines installed that were used to develop the LabVIEW application. These can manually be installed or included in an Installer along with the executable. Check to make sure the LabVIEW Run-Time Engine installed is compatible with the LabVIEW version the executable was developed in. 

Additional Information

Two deliverables the Application Builder can create are Stand-alone Applications and Installers. Both have their use cases and it is important to understand when to use either. 

Stand-alone Applications

  • Use stand-alone applications to provide other users with executable versions of VIs. (Windows) Applications have a .exe extension. (Mac OS) Applications have .app extension. 
  • Contains only the LabVIEW VI's and does not contain any other resources needed to run. For the executable to run, the PC must have the necessary run-time engines, drivers, etc. 


  • (Windows) Use Installers to distribute stand-alone applications, shared libraries, and source distributions that you can create with Application Builder.
  • Can include drivers and libraries to ensure the user's PC has all the resources the .exe is dependent on.
  • Can include custom installer graphics to customize the installation experience. 
When interfacing with hardware, ensure the correct driver is installed on the computer (DAQmx, 488.2, etc).


Not Helpful