This document contains the LabVIEW known issues that were discovered before and since the release of LabVIEW 2024 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 |
|---|---|---|---|
| 2786419 |
Palette Categories Are Visible Even When EmptyAll the palette categories are visible by default. Workaround: On a pinned palette, go to Customize > Change Visible Palettes, and select or deselect palettes to show or hide them. |
Reported Version: LabVIEW: 2024 Q3 Resolved Version: N/A Added: Jul 17, 2024 |
|
| 2781966 |
Unexpected Save Dialogs When Maintaining Projects in Older Save VersionLabVIEW may prompt you to save changes when editing VIs in a project maintained in an older version. For example, using DQMH for operations such as creating Private Events or validating a DQMH module will trigger a prompt to save VIs, indicating that the VI's source save version has changed. Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW: 2024 Q3 Resolved Version: N/A Added: Jul 17, 2024 |
|
| 2785983 |
LabVIEW Sometimes Prompts You to Save Unedited VIsLabVIEW may prompt you to save VIs that reference shared libraries, including some VIs in the Electrical Power Toolkit. If you do not save the VIs, deployment to Real-Time targets can fail. Workaround: Save the VIs when prompted. You may need to modify the VI permissions or run LabVIEW as an administrator to save the VIs. |
Reported Version: LabVIEW: 2024 Q3 Resolved Version: N/A Added: Jul 17, 2024 |
|
| 2798144 |
MATLAB Script Nodes Break VIsVIs containing MATLAB Script Nodes are broken because the script support DLL is not found. Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW: 2024 Q3 Resolved Version: N/A Added: Jul 17, 2024 |
|
| 2799931 |
Command Prompt Window Appears Briefly During Launch of LabVIEW on WindowsWorkaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW: 2024 Q3 Resolved Version: N/A Added: Jul 17, 2024 |
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