Error 1935 When Installing NI Software

Updated Dec 14, 2017

Reported In

Software

  • TestStand 2012
  • LabWindows/CVI 2012 Full
  • LabVIEW 2012 Full

Issue Details

While attempting to install NI software, such as LabVIEW, TestStand, Multisim, or a LabVIEW built installer, my installation failed. The error window reports Error 1935 or a problem with the installation of a specific assembly. How can I fix this error to install software?

The "NI Software Package Dependency" installation has failed with the following error:

Error 1935. An error occurred during the installation of assembly 'NationalInstruments.Software.assembly...'. Please refer to Help and Support for more information.

Continue?




Solution

  1. Run the installer again, or restart your computer and then launch the installer again. This will resolve the behavior if another installation or an update is the cause of the problem.
  2. Run the installation as an administrator. Navigate to the folder where the NI software you are installing is. Then, right-click the setup.exe file and select Run as administrator to resolve any possible permissions issues. This may require an administrator password depending on your system configuration.
  3. Disable any anti-virus, anti-spyware, or firewalls for the duration of the installation. These services have been known to block permissions for installing software.
  4. Reboot your computer and run the NI installer again with the same settings to ensure proper software installation. This type of error can also occur when you do not reboot after installing the Microsoft .NET Framework. For more information on the required reboot, refer to Why am I Prompted to Install the .NET Framework before Installing NI software?

Additional Information

Error 1935 is a Microsoft Installer error linked with permissions during the installation of software. Typically, either there is something on the computer which is blocking the installation or you do not have the necessary privileges to install software.

One example of this could be when Windows Update starts installing updates while an NI Installer is running. Another example could be if the installer is trying to write to a directory on disk which the current user does not have permissions to access. 

WAS THIS ARTICLE HELPFUL?

Not Helpful