This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Select Source Dialog Prompt When Building an Installer on LabVIEW™ and LabWindows™/CVI™

Updated Jul 28, 2026

Reported In

Software

  • LabVIEW
  • LabVIEW Application Builder Module
  • LabWindows/CVI
  • Measurement Studio

Driver

  • Instrument Drivers

Issue Details

  • When trying to build an installer in LabVIEW I get the following error message:

Some installers you selected for this build are not available on this computer. The preselected media below contain the required installers.If you have the preselected media, click OK. If not, deselect the media you do not have and select media you do have. When the selected media contain all the required installers, click OK. During the build you will be prompted for required media.

 
  • I am trying to create an installer using LabWindows/CVI and during the build it shows the following error message:

Distribution Not Found

The path no longer exists.
Cannot find distribution "NI MetaUninstaller".

If you would like to specify a different path where the distribution can be found, enter it below.

 

InstallerBuildErrorMessage.jpg

Why am I getting this dialog prompt, and how do I include these additional installers in my build?

Solution

The Select Source dialog box appears when required installer source files for selected components are missing. When building an installer that includes additional software, LabVIEW Application Builder requires access to the original installation media for those components. For example, including NI‑DAQmx may prompt for the device driver media that contains NI‑DAQmx.

Note: Before fixing the dependency issue for the installer the program is asking about, please check if the installers being included in the distribution file are necessary for running your application. In some cases, you might be including additional software that is not being used in your application and might include a dependency that is not installed in your computer.


The solution to these dependency errors depends on how the software was originally installed, please verify which one applies to your case

  1. If the installer was downloaded from ni.com/downloads and the extracted source files were deleted:
    • It will be necessary to download the same version and unzip it again before the build and point the Select Source dialog to the directory in which setup.exe was extracted.
    • For IVI drivers and self-extracting executables (.exe), the WinZip Self-Extractor extracts files to C:\National Instruments Downloads\. If the download came as a .zip file, extract the files, then point it to where the extracted setup.exe is located.
  2. If the software was installed from a CD or USB device:
    • It will be necessary to put CD or USB into the drive before building the installer.
    • If you no longer have the media from where it was installed, it is recommended that you uninstall the component and reinstall it using an installer from the NI website.
  3. If the software was installed from a network location:
    • Make sure access to the files on the network drive or one of the two above options is still possible.
  4. If the software was installed using a LabVIEW-built installer:
    • The "Select Source" dialog may reference that LabVIEW-built installer, so it will be necessary to point to that installer.
    • If the previous step didn't work, repair or force reinstall the same software stack as the computer that built the original installer to have fresh installs of the software with the setup files.
    • It is also possible to upgrade to a newer version of the software by downloading it from the NI website.
  5. If updates are pending in NI Package Manager:
    • If there are any pending updates shown in the NI Package Manager related to the software component the error message is asking about, please update the component and after the process is finished try rebuilding the installer.


If none of the above steps solve the issue and you recently build an installer and then deleted it, this issue may be occurring because there is a reference to a previously built installer in the Operating System Registry that LabVIEW is trying to use when building a new installer. Therefore, to solve the problem you have to delete the key registry that is associated with that installer. To complete this task, you have to follow the steps listed below.

Note: Proceed with extreme caution with the following steps. Modifying the Windows registry can affect system stability. Ensure the correct key is selected before making changes.
 

1. Type Regedit in the Windows search bar and run the Registry Editor Application as administrator.

 

search_regedit.png

 
2. Once in the Registry Editor Window, navigate to the next path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\National Instruments\Common\Installer\Distributions

path_in_regedit.png

3. Once you are on the Distributions folder, look for the key registry that is associated with that installer and delete it by right-clicking on it. To know exactly which key corresponds to your installer, select the key and look at the right side of the window for more information. Here you will find the Title, as well as the Distribution Root (DistRoot).

Deleting_Key.png

 

To avoid this dialog box in the future, make sure the following settings are selected when building an installer:

  • When using LabVIEW 2013 or Newer, selecting the Copy all future installers to this computer when you run them checkbox will cause all future installers to run on the system to automatically copy their products into the local cache during the install. This will prevent future prompts for the location of those installers from within the Installer Builder utility.
  
 
  • When using LabVIEW 2010 - 2012, this dialogue can be avoided by selecting the Copy selected installers to this computer before building option in the Additional Installers window in the Installer Build Specifications.

Additional Information

LabVIEW requires the additional installer’s source MSI and .id files that were used for installation on the development machine to be able to install the additional installer on other machines. These source files are not usually left on the development machine after installation. The Installer source location field tells LabVIEW where to find these needed source files. LabVIEW will, by default, set this field to the last location used to install the additional installer on the development machine. This should be the root directory of the location from where product has been installed, usually on a CD or network drive. 

Note: On Windows 10 PCs, the default Installer Source Location is C:\ProgramData\National Instruments\MDF\ProductCache. If the installer source file is located here but the Installer Build Specifications are not recognising it's presence, repair the Additional Installer package as described in Repair Software In NI Package Manager (NIPM) .

Some of these shared installer dependencies may have had a new version installed by another NI product and that product will be required in order to build the installer.

For example, say NI-DAQmx 8.0 is installed, which also installs NI Measurement & Automation Explorer (MAX) 4.0. As a result, NI MAX 4.0 will be installed on the computer.

Later Measurement Studio 8.0 is installed, which installs a newer version of NI MAX (4.1) and overwrites the previous version of NI MAX (4.0) (note: the version numbers of MAX are just an example and don't reflect real revisions shipped with various products). Now, NI-DAQmx 8.0 depends on Measurement Studio, and when an installer that includes NI-DAQmx 8.0 is built, it will need to copy the Measurement Studio installer from the distribution that installed it. So, while Measurement Studio is not directly being included, a shared dependency that it updated is being included, and the Application Builder needs to copy the installer of that dependency.