Error: DotnetClientPackageManagerNotInstalledError when running NI Package Manager

Updated Sep 27, 2023

Reported In


  • LabVIEW
  • TestStand
  • Package Manager

Operating System

  • Windows

Issue Details

  • I downloaded the Academic Volume License (AVL) and when I run the installer I get an NI Package Manager Error.
  • I tried to download NI Package Manager, LabVIEW, or TestStand separately from the NI download page and saved them to disk. When I try to run the file to install the software, I get an NI Package Manager Error:
An error occured while starting the session on the package manager solver library. 
ErrorCode: DotnetClientPackageManagerNotInstalledError


Try the following troubleshooting steps:
  • Try downloading the software from NI Software Product Downloads with different web browsers.
  • Disable the firewall while downloading and make sure there isn't any anti-virus software that could stop items from executing.
  • If this is for FIRST Robotics, download the offline installer for the FRC Game Tools and mount as disk. Then try any further needed installs again.
  • Try to run the installer with Administrative privileges.
  • Try to download the offline installer for the software version prior to your targeted version. For example, you are looking for NI Package Manager 20.0, but you encounter this error while attempting to install. You can try to download and install the offline installer for NI Package Manager 17.0 first. Once it is successfully installed, update it to NI Package Manager 20.0 from within NI Package Manager.
  • Download the NI Package Manager offline installer and install it offline. Reconnect to the internet after the installation is complete to download.
  • Install the oldest NI Package Manager to the machine as described above (version 17.0). Try to install the latest NI Package Manager to another machine then navigate to C:\ProgramData\National Instruments\NI Package Manager\packages folder and transfer ni-package-manager_[package version]_windows_x64.nipkg file to the problematic machine and run this file.