The following items are notable issues fixed between the release of LabVIEW 2026 Q1 and LabVIEW 2026 Q3, 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 LabVIEW.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 3013524 |
LabVIEW Class Becomes Corrupt When It Contains Multiple DLLs With the Same NameClasses that contain multiple DLLs with the same file name become corrupt after saving and reopening. Once corrupted, you cannot open the classes.
Workaround: Fixed in LabVIEW 2026 Q3. When a class loads, it ignores DLLs with duplicate names.
|
Reported Version: LabVIEW: 2024 Q3 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3557446 |
LabVIEW Crashes When You Open a Class Method That References a Deleted Static Dispatch PropertyRemoving a static dispatch property from a class causes LabVIEW to crash when you subsequently open a method that uses a property node for that property.
Workaround: Fixed in LabVIEW 2026 Q3. |
Reported Version: LabVIEW: 2019 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3723623 |
LabVIEW Sometimes Crashes When Opening Properties DialogLabVIEW sometimes crashes when you open the Properties dialog for a newly placed control on a VI if the hierarchy of the VI contains a static reference to the control.
Workaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2024 Q3 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3765688 |
LabVIEW Sometimes Hangs After Placing Diagram Disable StructureLabVIEW sometimes hangs after you place a Diagram Disable structure around code that contains a Case Structure.
Workaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3775285 |
VI Execution Sometimes Hangs After Disabling Execution HighlightingAfter you disable execution highlighting, your VI sometimes remains in the run state without LabVIEW executing the VI.
Workaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2025 Q3 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3778636 |
LabVIEW 64-bit Crashes When Clearing Data from XY GraphWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2023 Q3 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3793925 |
LabVIEW Crashes When Adding Breakpoint if INI token openProbesInOwnWindows is TrueWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2025 Q3 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3806303 |
LabVIEW Crashes When Comparing VIs Containing FPGA IO NodesWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2024 Q3 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3851971 |
LabVIEW Crashes When Disabling Debugging for a Target While Custom Probes are SetLabVIEW crashes if you add a custom probe to a VI and then disable debugging for that VI's target in the Project Environment Settings.
Workaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3876146 |
LabVIEW Sometimes Crashes When Opening a Project from a Universal Naming Convention PathWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 24, 2026 |
|
| 3454278 |
LabVIEW May Report Error 1631 When Building a Packed LibraryWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2025 Q3 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 25, 2026 |
|
| 3695783 |
LabVIEW Warns That Dependency Was Loaded From New Path When Opening .NET Core Example VIWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 25, 2026 |
|
| 3596234 |
LabVIEW on Ubuntu 22, RHEL 8, and RHEL 9 Crashes When Selecting Noto Color Emoji FontWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2025 Q3 | LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 25, 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: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2025 Q3 | LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 25, 2026 |
|
| 3702292 |
Initial Position Panel and Diagram for Main.vi in Simple State Machine Project Template Are Not at Top-Left of MonitorWorkaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 25, 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 through 2026 Q1) on the same machine, the older versions of LabVIEW lose access to VI Analyzer erroneously. Workaround: Fixed in LabVIEW 2026 Q3.
|
Reported Version: LabVIEW: 2025 Q3 | LabVIEW: 2026 Q1 Resolved Version: LabVIEW: 2026 Q3 Added: Jul 4, 2026 |
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.