Support Knowledge Base
- Resolving issues with VIPM connecting to LabVIEW
- Error 11 ("Too many files open") on VIPM for Linux
- Package Build and Install Errors Due to Long Paths
- VIPM Sometimes shows a blank Package Information dialog when clicking a VI Package link
- VI Package Manager Runtime Engine - Installation Media Required for Repair
- File Permission Errors running VIPM on macOS
- VI Package Builder removes cross-platform wildcards from Call-Library Function nodes during the build process
- VIPM 2020 Crashing on macOS 11 "Big Sur"
- Error 1357 during a package build (File Already Exists)
- [18867] VI Packages cannot be built if their hierarchy contains VIs stored under the LabVIEW\help folder (results in Missing VIs error)
- [18866] Package Repository URL is coerced to lowercase when adding (should preserve case when adding)
- [18855] Clicking VIPM icon on Windows taskbar should open VIPM if it's running in System Tray
- [18852] Cannot Install Package (Error 8: Open/Create/Replace File related to a package spec file)
- [18825] VIPM API doesn't handle LabVIEW 2020
- [18805] Error dialog when installing VI Package Manager 2020.1 runtime engine prerequisites
- VIPM Package Repository Clients Missing Dependencies on Sub-packages (often System Packages)
- Disabling VIPM service (System Tray) startup when LabVIEW starts up
- VIPC Dependency Scanning Does Not Find Packages With Malleable VIs (VIM files)
- VIPM installation may freeze or hang at the "Installing prerequisite software" step (Windows 10)
- Error Code 54 when checking for package updates
- Deactivation Fails for Licensed Add-ons built with VIPM
- Enable 30 Day VIPM Pro Trial
- An untitled VI opens when installing a VI Package with a Custom Action VI
- VIPM 2013 cannot install packages built in VIPM 2014 or greater
- VIPM for Linux
- VIPM Labs
- Error 5 occurred at an unidentified location - Error Message
- Issue with Installing VIPM on Linux
- VIPM fails to launch after splash screen on Windows
- Troubleshooting Package Building Problems