The following items are notable issues fixed between the release of LabVIEW 2025 Q1 and LabVIEW 2025 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 |
|---|---|---|---|
| 3063044 |
VI Comparison Report Can Show Incorrect Text Value Change for CaptionIn some cases, a caption text value change can have the "from" and "to" strings in the wrong order.
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3063044 |
Python Node With Object Refnum Input Returns Error 1744 After Repeated CallsWhen using a Python Node with a Python object refnum as an input, LabVIEW returns error 1744 after 1,048,576 calls.
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2023 Q3 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 2972983 |
Select .NET Core Constructor Dialog Incorrectly Reports No Public Constructors For Classes Not Part of Any NamespaceIf you select a class that is not part of any namespace in the Select .NET Core Constructor dialog, the message This class contains no public constructors is displayed, even if the class does contain public constructors.
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3005689 |
LabVIEW Does Not Detect When LabVIEW Class Should Be Broken Because Its Private Data Includes Set or Map That Contains the ClassWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2019 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3006536 |
.NET Refnum Control Is Missing Select .NET Core Class Right-Click MenuWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3008439 |
Constructor Node for .NET Core Does Not Include Exception Details with Error 1172Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3039297 |
Simple Numeric Constant Created Instead of Ring When Creating Constant from Ring Typed Terminal of LabVIEW Class Property NodeWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3066513 |
Calls to .NET Core Methods With Multiple Return Values Do Not Return Values to Output ParametersIf you call a .NET Core method that uses the out keyword to have multiple return values, LabVIEW does not correctly return those values.
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3066525 |
.NET Core Enumerations Are Treated As ReferencesLabVIEW can pass numeric values to and from .NET Framework properties and method parameters, but when using .NET Core properties and methods, you must use references instead. This limitation requires you to write extra code to get and set values on the reference. Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3073490 |
LabVIEW Crashes When Outputs on .NET Core Property or Invoke Nodes Are UnwiredWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3077738 |
LabVIEW Sometimes Crashes With .NET Core Methods Using Arrays of StringsWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3144001, 3166958 |
Vulnerabilities CVE-2025-2633 and CVE-2025-2634Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 2941475 |
Text Entry Renders Incorrectly in Table Cells with Centered TextWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2024 Q3 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 2963459 |
Python Node Returns Error 1667 When Module Path Contains Unicode CharactersWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2023 Q1 | LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 2974910 |
Configuration Dialog Missing for Fixed Point Shared VariableWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2024 Q3 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3126088 |
Web Service URL Limited to 512 CharactersWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 2918538 |
Compile Error When Using Not A Number/Path/Refnum Function with Dynamic DataWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2024 Q3 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 2922757 |
Cannot Edit Enum Array Element By Holding Ctrl Key and Clicking the ElementWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2020 SP1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 2930247 |
Mass Compile Slower Because LabVIEW Does Not Save VIs in LVAddonsWhen you mass compile VIs that reference VIs in the version-independent location on the computer (LVAddons), the VIs in LVAddons are compiled multiple times, which causes the mass compile to take longer to complete. Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2024 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3003728 |
LabVIEW Sometimes Crashes After Reordering Controls on Page of Tab ControlWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2024 Q3 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3011141 |
Tree Alternating Row Color is Incorrect on First Row if Column Headers Not VisibleWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3029109 |
VI Window Sometimes Positioned Incorrectly When VI Properties for Window Position and Panel Size Are SetWhen a VI has both Window Position and Panel Size configured to non-default values in its Properties, the run-time position of the window can be incorrect.
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3040552 |
LabVIEW Sometimes Crashes After Replacing Tab Control with Another Tab ControlWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3042977 |
Probe Display of XML Reference Does Not Display Correct ValueWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2023 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3044350 |
LabVIEW Does Not Report Save Compatibility Issue with Splitter Bars When Saving to Versions Earlier than 19.0Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3045969 |
LabVIEW Crashes When Executing Replace No Attributes Method on Tab ControlWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3050230 |
Debug Write.vim Erroneously Displays Last Element of Non-string Array At Beginning of Debug StringWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3058541 |
Some Mixed Signal Graph Plots Do Not Display Plot Area Foreground ImageWhen a Mixed Signal Graph has the "Plot Images:Front" property set, only the first plot displays the image.
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2020 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3160785 |
No Value Change Event Fired After Deleting Array Element With Ctrl+Del Keyboard ShortcutWorkaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3161234 |
Reentrant VIs Sometimes Lose Reentrancy Setting Unexpectedly in Project Configured With a Save Version Earlier Than the Editor Version
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3162353 |
Controls In Built Applications Do Not Receive Mouse Wheel Event If Ctrl Key Is Also Pressed
Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3168519 |
LabVIEW Does Not Detect Save Incompatibility for Concatenate Strings in Save Versions Prior to 21.0Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 1554661 |
Error 1055 in VISL_findDependentVISvr.vi when Building ExecutableError 1055 sometimes occurs when building an EXE with the LabVIEW DSC Module installed. Workaround: Fixed in LabVIEW 2025 Q3. |
Reported Version: LabVIEW 2019 SP1 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3036893 |
Vulnerability CVE-2025-7361Fixed Vulnerability CVE-2025-7361. LabVIEW no longer supports Code Interface Nodes unless the configuration file contains EnableCodeInterfaceNodes=True.
Workaround: Fixed in LabVIEW 2025 Q3.
|
Reported Version: LabVIEW 2023 Q3 Resolved Version: LabVIEW 2025 Q3 Added: Jul 1, 2025 |
|
| 3075204 |
Vulnerabilities CVE-2025-7848 and CVE-2025-7849Fixed Memory Corruption Vulnerabilities CVE-2025-7848 and CVE-2025-7849.
Workaround: Fixed in LabVIEW 2025 Q3.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Added: Aug 1, 2025 |
|
| 3064741 |
Command Window Appears When Running Installer Built by LabVIEWWorkaround: Fixed in LabVIEW 2025 Q3.
|
Reported Version: LabVIEW 2025 Q1 Resolved Version: LabVIEW 2025 Q3 Added: Aug 1, 2025 |
|
| 3179057 |
Internal warning 0x558A98DB: "undo.cpp", line 5422 When Removing Breakpoint from Reentrant Clones in Debug WindowAfter you remove a breakpoint from a reentrant clone in the Debug window, LabVIEW will display Internal warning 0x558A98DB: "undo.cpp", line 5422. The breakpoint will be removed from the reentrant original and all clones.
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Jul 9, 2025 |
|
| 3181565 |
Creating VI Comparison Report Can Delete Destination FolderWhen creating a VI Comparison report in HTML, HTML single file, or XML format, if a folder with same name as the report exists in the specified destination, the folder and all its contents will be deleted.
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Jul 8, 2025 |
|
| 3183388 |
Applications Using Code Interface Nodes Cannot Run With LabVIEW 2025 Q3 Run-Time EngineIf you build an application in LabVIEW 2025 Q3 that uses Code Interface Nodes (CINs), it will not execute. Also, if you install the 2025 Q3 LabVIEW Run-Time Engine on a system where an application uses both CINs and the setting to allow future versions of the LabVIEW Runtime to run this application, the application will no longer execute.
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Jul 8, 2025 |
|
| 3188618 |
LabVIEW for Linux in Docker Container Exits After LabVIEWCLI OperationWhen LabVIEW 2025 Q3 for Linux is running in a Docker Container, LabVIEW closes after running a LabVIEWCLI operation. This causes the following behaviors:
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Jul 18, 2025 |
|
| 3192873 |
Password Authentication for OpenSSH SSH and SFTP VIs on Windows Fails with Error 42When using OpenSSH with SSH and SFTP functions, using password authentication will fail and return error 42. Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Jul 18, 2025 |
|
| 3192981 |
LabVIEW Crashes After Using Ctrl+Shift+Mouse Wheel Over a Flat Sequence StructureWorkaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q1 | LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Jul 18, 2025 |
|
| 3193066 |
VIs Can Be Placed In Wrong Folders When Building ApplicationsBuilt VIs can be in unexpected destinations after building an application or library that includes an already-built Packed Library. This might include VIs being placed into a destination folder other than their caller.
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Jul 18, 2025 |
|
| 3208367 |
VI Sometimes Erroneously Broken When Calling Property Node of a LabVIEW ClassWorkaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Aug 4, 2025 |
|
| 3192961 |
LabVIEW Sometimes Displays Error Message When Searching With NigelIf you use "Search with Nigel" in a VI toolbar before logging in to your ni.com account in the Nigel AI Advisor chat window, you will see a message that instructs you to log in. After logging in and using "Search with Nigel" again, you might see an error message that says: "Not enough memory to complete this operation."
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Aug 1, 2025 |
|
| 3195661 |
LabVIEW Options Dialog Erroneously Display Search CategoryThe Tools»Options dialog erroneously contains a Search category. Changing the settings in this category does not affect your LabVIEW settings.
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Aug 1, 2025 |
|
| 3206439 |
LabVIEW Does Not List All Methods and Properties from .NET 8.0 Parent InterfacesWhen you are configuring Invoke and Property nodes with .NET 8.0 assemblies, you might not see methods and properties from parent interfaces.
Workaround: Fixed in LabVIEW 2025 Q3 Patch 2.
|
Reported Version: LabVIEW 2025 Q3 Resolved Version: LabVIEW 2025 Q3 Patch 2 Added: Aug 1, 2025 |
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.