The following items are notable issues fixed between the release of Package Manager 20.7 and Package Manager 21.0, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of Package Manager.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1415193 |
Newly built deployment installers do not install on Win7 32-bitAfter the release of Package Manager 20.7 on April 9, 2021, building 32-bit deployments in LabVIEW, TestStand, NI Package Builder, or LabWindows/CVI on 64-bit OS internet-connected systems create package installers that might fail to install on 32-bit OSes. Attempting to install the built deployment will result in the installer reporting that it is unable to locate ni-package-manager (or other Package Manager packages) with a compatible version and architecture. Note: Deployments built before April 9, 2021, are not affected and should still install successfully. Workaround: Refer to the NI KnowledgeBase at www.ni.com/kb/ and enter the title "NI Package-Based Distribution Built on 64-Bit Computer Fails to Install On 32-Bit" |
Reported Version: Package Manager 20.7 Resolved Version: Package Manager 21.0 Added: May 4, 2021 |
|
| 1430830 |
Installers run using --quiet or --passive option fail with error code -125813 when installation requires removal of a packageWhen an installer requires removal of a package during installation, using the --quiet or --passive command line options always fail with error code -125813. Package Manager 21.0 no longer errors and removes required packages. Workaround: There is currently no known workaround for this issue. |
Reported Version: Package Manager 20.6 Resolved Version: Package Manager 21.0 Added: May 4, 2021 |
|
| 1436537 |
Installers built by Package Builder and Volume License Manager might incorrectly exclude dependent packagesOffline installers built by Package Builder and Volume License Manager that include packages from NI installers on disk can incorrectly exclude dependent packages, which results in the following error messages during installation:"A required package could not be found: The package 'package-name' requires package 'dependent-package (>= version)' that has an architecture compatible with this operating system." Workaround: There is currently no known workaround for this issue. |
Reported Version: Package Manager 20.6 Resolved Version: Package Manager 21.0 Added: May 4, 2021 |
|
| 148740 |
Package installation error generically reports to check your internet connection and try againWhen installation of a package errors, Package Manager generically reports that an error occurred and to check your internet connection and try again. Package Manager 21.0 and later now reports the underlying error, such as, the error returned from the MSI the package installs. Workaround: There is currently no known workaround for this issue. |
Reported Version: Package Manager 20.5 Resolved Version: Package Manager 21.0 Added: Jul 14, 2021 |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.