NI Package Manager 18.0.1 Known Issues

Aperçu

This document contains important last-minute information about NI Package Manager, including known issues.

Known Issues by Category

The following items are known issues in NI Package Manager 18.0.1 sorted by Category.

Installation and Activation
631981 Package Manager physical media installation fails installing without .NET 4.6.2
684715 Store installation fails with "FIPS-compliant" encryption enabled.
Menus
658457 Feed edits are not cancelled



ID Known Issue
Installation and Activation
631981

Return
Package Manager physical media installation fails installing without .NET 4.6.2
When installing NI Package Manager from physical media on a machine without internet connection, if the machine being installed to does not have .NET 4.6.2 installed, the installation will fail due to a missing Microsoft certificate file.

Workaround: Download and install the certificate using the instructions on Microsoft's website: https://blogs.msdn.microsoft.com/vsnetsetup/2016/03/28/a-certificate-chain-could-not-be-built-to-a-trusted-root-authority-2/

Reported Version: 17.5    Resolved Version: N/A    Added: 03/21/2018
684715

Return
Store installation fails with "FIPS-compliant" encryption enabled.
NI Package Manager installations from the Store fail with the message "Exception has been thrown by the target of an invocation" when the Windows "FIPS-compliant" setting is enabled.

Workaround: Disable FIPS and re-run the installation.

Reported Version: 17.5    Resolved Version: N/A    Added: 03/21/2018
Menus
658457

Return
Feed edits are not cancelled
When editing a feed URL in NI Package Manager, selecting the "Cancel" button does not undo changes to the feed URL.

Workaround: Manually undo changes made to the feed URL.

Reported Version: 18.0    Resolved Version: N/A    Added: 03/21/2018

Document last updated on 3/23/2018

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).