Archived:Control Could Not Be Loaded Error When Placing ActiveX Control on Front Panel

Updated Jul 19, 2019

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Issue Details

  • When I try to place an ActiveX object from the ActiveX palette on the front panel I get the message "Control could not be loaded". How can I fix this?
  • I upgraded the versison of .NET Framework by updating National Instrument's software. Now the controls on my executables say "Control could not be loaded." How can I fix this?


The ActiveX palette item is not properly linked to the ActiveX control, so LabVIEW is unable to find the correct path to the ActiveX control on disk.

To fix this issue it may be necessary to repair the LabVIEW run-time engine.
  1. Navigate to Control Panel >> Add/Remove Programs >> National Instruments Software
  2. Select the appropriate NI LabVIEW Run-Time Engine and click Repair
  3. Restart your computer.


Additional Information

Note: If you are using NI Package Manager the option to Repair is not available and you must uninstall and reinstall the Run-Time Engine.

Note: These steps are viable for LabVIEW Run-Time Engine 7.1.1 or lower, Versions 8.0 and above of the run-time engine do not appear under National Instruments Software in Add/Remove Programs. The version of LabVIEW Run-Time Engine installed can be seen in Measurement & Automation Explorer (MAX).

In addition, older versions of the LabVIEW run-time engine have been known to occasionally cause this error when the ActiveX control is installed to a directory that is not on the Windows path. Ensure that you have upgraded to the latest version of the run-time engine to solve this problem.

This message can also occur if the ActiveX control uses the .NET Framework and this framework is not installed on the PC. In addition, it may happen if incompatible versions of the framework are being used when going from a development to target machine. For .NET versions 2.0 and higher are backwards compatible. For example, if the .NET Framework 3.5 is installed, aspects of the .NET Framework 2.0 can be used.