This document contains the LabVIEW known issues that were discovered before and since the release of LabVIEW 2026 Q3. 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 |
|---|---|---|---|
| 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 | LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 25, 2026 |
|
| 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 | LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 25, 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 | LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 25, 2026 |
|
| 3231187 |
LabVIEW 2025 Q3 Community Edition for Windows Incorrectly Includes Nigel AI AdvisorThe installer for LabVIEW 2025 Q3 Community Edition includes the Nigel AI Advisor, 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 Advisor for LabVIEW 2025 when setting up your LabVIEW Community Edition installation.
|
Reported Version: LabVIEW: 2025 Q3 | LabVIEW: 2026 Q1 | LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 9, 2026 |
|
| 3924511 |
Debug Window Doesn't Correctly Display Probe Value of Variant Containing Strings in UTF-8 EncodingThe Value column of the Debug Window doesn't correctly display strings with UTF-8 encoding when the strings are in a Variant.
Workaround: Refer to the Probe Display instead of the Value column.
|
Reported Version: LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 24, 2026 |
|
| 3904440 |
NI Advanced HTTP Client API VIs and JKI HTTP REST API Client VIs Return Error 2Workaround: Install a LabVIEW Run-Time Engine from version 2024 Q3 or earlier.
|
Reported Version: LabVIEW: 2025 Q1 | LabVIEW: 2025 Q3 | LabVIEW: 2026 Q1 | LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 24, 2026 |
|
| 3949718 |
Import Strings from XLIFF Reports Missing Tag for Path ControlWhen exporting VI strings to XLIFF for a VI containing a path control where the path control does not define a custom prompt, LabVIEW does not export a tag for the prompt. However, the Import Strings from XLIFF function expects expects path controls to have tags and reports a missing tag error while parsing for Path objects. Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 24, 2026 |
|
| 3901764 |
Unable to Add Targets to Project When Using 64-bit Japanese LabVIEW with 64-bit English Real-Time and FPGA ModulesWorkaround: Use 32-bit LabVIEW Japanese if you require RT and FPGA functionality.
|
Reported Version: LabVIEW FPGA Module: 2026 Q1 | LabVIEW Real-Time Module: 2026 Q1 | LabVIEW: 2026 Q1 | LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 24, 2026 |
|
| 3966315 |
Multilingual Temperature Monitor Example VI Isn't Visible in Example Finder Task View or Search ResultsWorkaround: Open Multilingual Temperature Monitor.vi using the Directory Structure view under UTF-8\Multilingual User Interface.
|
Reported Version: LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 14, 2026 |
|
| 3970142 |
Captions in Type Definitions Erroneously Remain in System Encoding After Migrating VIs to UTF-8Captions that are in type definition instances erroneously remain in system encoding after using the UTF-8 Migration tool to convert control/indicator captions in a VI to UTF-8 encoding
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 17, 2026 |
|
| 3970830 |
VI Cannot Save in Previous Version Format After Editing a Case Structure Selector LabelIf you edit a Case Structure selector label for a case structure whose selector is a type other than a system-encoded string in a VI that is saving to a prior version, the VI toolbar displays a Save Compatibility Warning. The Error List doesn't provide details about why the VI cannot save to the specified version.
Workaround: This error occurs due to LabVIEW erroneously setting the encoding for the Case Structure selector label to UTF-8 even if you do not edit the label. If you string with System encoding to the Case Structure selector, you can clear the Save Compatibility Warning. Then, undo until the original input to the Case Structure selector is restored.
|
Reported Version: LabVIEW: 2026 Q3 Resolved Version: N/A Added: Jul 22, 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
The registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a worldwide basis.