[Bug] VIPM Shows No Packages Installed in LV 2023 Q3 after upgrading from LV 2023 Q1

Who is Affected

LabVIEW 2023 Q3 users who upgraded from LabVIEW 2023 Q1 and already had packages installed with VIPM.

Symptoms

Packages were installed in LabVIEW 2023 Q1 (and do show in the palettes of LabVIEW 2023 Q3) but VIPM shows no packages installed in LabVIEW 2023 Q3.

Problem Details

VIPM keeps an installation database of installed packages for each LabVIEW version. The reason that previously installed packages show as missing is because VIPM initialized a new installation database for 2023 Q3 and left the old installation database for 2023 Q1 in place, unused.

Problem Background

Recently, LabVIEW introduced a new versioning system where quarterly release numbers are used as LabVIEW's minor version number (LabVIEW 2023 Q3 --> 23.3). Previously, service pack releases used the bugfix version number (e.g. LabVIEW 2019 SP1 --> 19.0.1). Historically, it has been assumed that the minor version number would never change and only the bugfix version number would be incremented for SP releases (e.g. quarterly or semi-annual service packs). Accounting for this change in quarterly versioning of LabVIEW has impacted a variety of different LabVIEW tools (and features of LabVIEW)

Work-around

1) Use VIPM to uninstall all packages from LabVIEW 2023 Q3 2) Exit / Quit VIPM 3) Delete the LV 23.3 (64-bit) package installation database folder (located here C:\ProgramData\JKI\VIPM\databases\) 4) Rename the LV 23.1 (64-bit) folder as LV 23.3 (64-bit) 5) Restart VIPM 6) Uninstall all packages from LabVIEW 2023 Q3 7) Re-install the packages you need for working on your project (e.g. using Dragon).

Plans for a Fix

A VIPM 2023.3 f1 is planned, which will have a fix for this issues, and will also include a solution for verifying the package installation databases.

vipm-io / vipm-desktop-issues