LabVIEW 2025 Q1 Known Issues

Overview

This document contains the LabVIEW known issues that were discovered before and since the release of LabVIEW 2025 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

JKI Dragon 2024 Q3 Cannot Open LabVIEW 2025 Q1 Projects

The version of JKI Dragon that is included in the LabVIEW 2025 Q1 installer (version 2024 Q3) cannot open projects in LabVIEW 2025 Q1.

Workaround:

Open the JKI Dragon application and check for updates.

Reported Version:

LabVIEW 2025 Q1

Resolved Version:

N/A

Added:

Jan 30, 2025

2954341

Invoke Node Calling .NET 8 Method Returns Error 1782 if Optional Parameter is Not Wired

Workaround:

Provide a value to the optional parameter.

Reported Version:

LabVIEW 2025 Q1

Resolved Version:

N/A

Added:

Jan 30, 2025

2963459

Python Node Returns Error 1667 When Module Path Contains Unicode Characters

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2023 Q1 | LabVIEW 2025 Q1

Resolved Version:

N/A

Added:

Jan 27, 2025

2972983

Select .NET Core Constructor Dialog Incorrectly Reports No Public Constructors For Classes Not Part of Any Namespace

If 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:

Declare your .NET classes as part of a namespace.

Reported Version:

LabVIEW 2025 Q1

Resolved Version:

N/A

Added:

Jan 30, 2025

2930247

Mass Compile Slower Because LabVIEW Does Not Save VIs in LVAddons

When 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:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2024 Q1 | LabVIEW 2025 Q1

Resolved Version:

N/A

Added:

Jan 27, 2025

3019996

Bookmark Manager Does Not Display All Bookmarks in Projects Created from Templates

If you create a project from a template which contains VIs with bookmarks, the Bookmark Manager doesn't display those bookmarks until you modify them.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2025 Q1

Resolved Version:

N/A

Added:

Feb 26, 2025

3011141

Tree Alternating Row Color is Incorrect on First Row if Column Headers Not Visible

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2025 Q1

Resolved Version:

N/A

Added:

Mar 24, 2025

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

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

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).