LabVIEW Executable Error: "(Hex 0x464) VI Is Not Loadable"

Updated Oct 23, 2023

Reported In


  • LabVIEW 2018

Issue Details

  • I am getting the following LabVIEW error message: LabVIEW: (Hex 0x464) VI is not loadable.

  • This error message is also shown in the image below:

  • My LabVIEW executable builds successfully, but sometimes the executable doesn't work as the above error message appears before the LabVIEW VI loads.
  • I am using LabVIEW 2018 (32-bit) to develop an application. When I open the stand-alone application, I get the above error message.
  • I am using functions from "NI_AALBase.lvlib", and I get the error below:

"An error occurred loading VI 'NI_AALBase.lvlib: Std Deviation and'.
LabVIEW load error code 1: LabVIEW load error code"


There are several possible causes for this error. Therefore, this article is not exhaustive but will address some of the common situations that may result in this error when running a LabVIEW executable.

If Using LabVIEW 2018 (32-bit):
This error is solved with the LabVIEW 2018 (32-bit) f2 Patch release. Go to the LabVIEW 2018 (32-bit) f2 Patch download page to install and upgrade to this version.

If Using "NI_AALBase.lvlib":
When any function inside "NI_AALBase.lvlib" is included in a VI, the resulting standalone application becomes unloadable.

The following steps are a workaround for this situation:

  • In the Project Explorer, move "NI_AALBase.lvlib" from Dependencies and place it under My Computer.

  • In Build Properties, move "NI_AALBase.lvlib" to the "Always Included" section.

  • Rebuild the Build Specification.

  • Run the executable.

If the "Std Deviation and Variance VI" in the NI_AALBase.lvlib is used and throws this error, you should update your LabVIEW version to at least LabVIEW 2020, because this bug was fixed in this version.

Additional Information

This issue can happen if multiple versions of a VI or NI software are loaded on disk (ex. LabVIEW 2018 64bit & 32bit). The compiler may pull the wrong VI version to compile resulting in this error being generated.