Critical Security Update
To help protect your systems, customers using NI driver software 2026 Q2 or earlier should visit ni.com/ni-pal-update and follow the recommended actions.
This document contains the LabVIEW known issues that were discovered before and since the release of LabVIEW 2026 Q1. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 3599848 |
Localized Versions of LabVIEW Show English Names in PalettesSpace Constant and Command Line String To Path do not have localized names in the String palette.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3454278 |
LabVIEW May Report Error 1631 When Building a Packed LibraryWorkaround: Add this line to the LabVIEW configuration file: NewAppBuilderCache.RemoveLibraryReferences=False
|
Reported Version: LabVIEW 2025 Q3 | LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3600663 |
JKI Dragon Does Not Always Install Declared Dependencies When Opening LabVIEW ProjectsWhen you open a LabVIEW project that has missing declared dependencies, JKI Dragon may fail to initiate the dependency installation process.
Workaround: Open the LabVIEW project in LabVIEW and open Project Dependencies from the toolbar to install the missing dependencies manually. Note that you can also open the JKI Dragon application and check for updates. Refer to the release notes for future versions of JKI Dragon for updates on this issue.
|
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3686436 |
LabVIEW for Linux Reports Error When Installing ni-labview-offline-manualWhen installing LabVIEW for Linux, an error message appears that says "Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply time expired, or the network connection was broken." However, both LabVIEW and the offline help install successfully and function correctly.
Workaround: Consult How do I resolve errors when installing the offline user manual with the LabVIEW 2026 Q1 Linux ISO installer? for more information on this error.
|
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3695783 |
LabVIEW Warns That Dependency Was Loaded From New Path When Opening .NET Core Example VIWorkaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 3, 2026 |
|
| 3596234 |
LabVIEW on Ubuntu 22, RHEL 8, and RHEL 9 Crashes When Selecting Noto Color Emoji FontWorkaround: Do not use the Noto Color Emoji font on distributions that use versions of libXft older than 2.3.5.
|
Reported Version: LabVIEW 2025 Q3 | LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3697602 |
VI Does Not Prompt to Save Changes After Removing Disabled BreakpointAfter removing a disabled breakpoint on a VI in LabVIEW 2025 Q3, or on a VI outside of a project in LabVIEW 2026 Q1, the VI is not marked with unsaved changes. Note that VIs in projects in LabVIEW 2026 Q1 store breakpoints in a separate file, so the lack of unsaved changes there is not a bug.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2025 Q3 | LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3702292 |
Initial Position Panel and Diagram for Main.vi in Simple State Machine Project Template Are Not at Top-Left of MonitorWorkaround: Open [LabVIEW 2026]\ProjectTemplates\Source\Core\Simple State Machine\Main.vi, move its window to the desired initial window position, and save the VI.
|
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3717800 |
Image Created by Get Conpane Image Method Includes Discuss with Nigel LinkWorkaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2025 Q3 | LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3231187 |
LabVIEW 2025 Q3 Community Edition for Windows Incorrectly Includes Nigel AIThe installer for LabVIEW 2026 Q1 Community Edition includes the Nigel AI, but to use Nigel you must have an active subscription license, multi-seat license, or Software Service Program for LabVIEW Professional.
Workaround: Deselect NI Nigel AI for LabVIEW 2026 when setting up your LabVIEW Community Edition installation.
|
Reported Version: LabVIEW 2025 Q3 | LabVIEW 2026 Q1 Resolved Version: N/A Added: Jan 29, 2026 |
|
LabVIEW Code Completion with Nigel AI May Suggest Code With Incorrectly Configured NodesLabVIEW Code Completion with Nigel AI may suggest code that includes Bundle, Unbundle, Property, and Invoke nodes that aren't configured to match the intended functionality.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
||
| 3593533 |
LabVIEW Code Completion Always Prompts Login after Logging in to Nigel AI and Rebooting SystemLabVIEW Code Completion always prompts you to log in to Nigel AI the first time you use it after rebooting the system. If you were previously logged in, the Nigel chat window opens and logs in automatically, but you need to repeat your code completion request.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 2, 2026 |
|
| 3700726 |
LabVIEW Loses Undo History Prior to Code Completion With Nigel AIIf you edit a VI before using Code Completion with Nigel AI, LabVIEW loses your undo history. You cannot use the Undo command to undo these earlier changes.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW 2026 Q1 Resolved Version: N/A Added: Feb 3, 2026 |
|
| 3266479 |
VI Analyzer Toolkit Stops Working in Older Versions of LabVIEW When You Add a Newer VersionVI Analyzer Toolkit for LabVIEW 2024 Q3 and later installs into a shared location (LVAddons) instead of the LabVIEW folder. If you have LabVIEW 2024 Q3, 2025 Q1, or 2025 Q3 installed on your machine and install a newer version of LabVIEW (2025 Q1 or later) on the same machine, the older versions of LabVIEW lose access to VI Analyzer erroneously. Workaround: Refer to these documents for more information: VI Analyzer Tests Will Not Load After Installing Newer LabVIEW Version - NI, Missing Example and VI of LabVIEW Toolkit Version 2026 Q1 in LabVIEW 2025 Q3 - NI
|
Reported Version: LabVIEW 2025 Q3 | LabVIEW 2026 Q1 Resolved Version: N/A Added: Apr 7, 2026 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.