VeriStand Engine Removed After Running LabVIEW EXE on Target

Updated May 3, 2018

Reported In


  • VeriStand
  • LabVIEW Real-Time Module

Issue Details

I have a standalone LabVIEW application and a standalone VeriStand application that both work fine on their own. When I run the LabVIEW project first, then run the VeriStand project, the host cannot deploy to the real time target. It appears that the VeriStand Engine is no longer on the target and I have to reinstall it for VeriStand to work again. Why is this happening?


This is expected behavior. VeriStand automatically is set to be the startup executable. If you run another application as the start up executable, there is no way to go back to VeriStand and manually set it as the startup executable again. For example, if you want a LabVIEW exe to be the start up VI you right click it and choose as start up. The VeriStand engine is not a LabVIEW exe so this is not an option.

One potential work around is to use the open source work space tool called Reset VeriStand as Startup
NOTE: This tool is not maintained or supported by National Instruments.