LabVIEW 2024 Q3 Bug Fixes

Overview

The following items are notable issues fixed between the release of LabVIEW 2024 Q1 and LabVIEW 2024 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

2599334

WebDAV, HTTP, and SMTP Functions Fail to Use Certificates from Files

Configure SSL (WebDAV), Asynchronous Configure SSL (WebDAV), ConfigSSL (HTTP Client), and Config TLS (SMTP) functions fail to use certificate files but do not return errors.

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2023 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

Offline Help for LabVIEW 2024 Q1 Chinese and Korean Versions Contains Content from LabVIEW 2023 Q3

In LabVIEW 2024 Q1 localized to Chinese or Korean, the offline help included the same contents as the LabVIEW 2023 Q3 help.

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2645388

Building a Packed Library May Fail Due to Incorrect Path to .NET DLL

In LabVIEW 2024 Q1, building a packed library can fail because LabVIEW incorrectly resolves a relative path to a .NET DLL.

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2714418

LabVIEW Sometimes Cannot Display File Dialog After Creating Override Methods in a Class

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2023 Q3

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2717959

LabVIEW Controls Do Not Receive Mouse Wheel Event with Ctrl Key Pressed

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2023 Q3

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2742395

LabVIEW Crashes When Comparing VIs with Different Passwords

When comparing VIs that are protected with different passwords, LabVIEW crashes after you enter the passwords.

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2748388

Compare VIs Does Not Report Difference When Label Changes Attached Object

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2752615

LabVIEW Editor Responds Slowly with Navigation Window Open and Block Diagram Zoomed

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2767151

Mass Compile Does Not Update Cache for Some VIs Installed in LVAddons

Mass compile doesn't update the compile cache for VIs installed in the shared LVAddons folder if the VIs are in read-only LLBs. Without an updated cache, TestStand cannot run the VIs using the LabVIEW Run-Time Engine.

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

221246 718006

LabVIEW Does Not Propagate Type Definition Changes to Containers, Causing Unexpected Run-Time Behavior

After you change a type definition's qualified name (for example, by removing it from a class), LabVIEW may fail to apply such change to event refnums or other container data types that include that type definition. VIs that references the affected container data type won't show as broken, but may have unexpected run-time behavior.

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2016

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

812117 520215

Find Parallelizable Loops Does Not Analyze VIs Under Targets

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2009 SP1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2597746

LabVIEW Fails to Create Probe for Cluster that Contains IMAQ Image

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2023 Q3

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2663212

VI Block Diagram Wires Sometimes Draw Incorrectly on Ubuntu

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2675593

LabVIEW (64-bit) Sometimes Gives Incorrect Results When Converting Timestamps to Strings with Fractional Seconds Exceeding 19 Digits

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2023 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2682003

Resizing Loops Sometimes Moves Tunnels Unnecessarily

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2687156

Compare VIs Does Not Report Differences in Window Transparency Values

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2023 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2694996

Quick Drop Shortcuts Do Not Work When Placing VIs Shipped with LabVIEW

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2695155

LabVIEW Can Display the Wrong Portion of a VI Block Diagram During Debugging When Diagram is Zoomed In

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2707687

In Multi-Monitor Systems, LabVIEW Sometimes Fails to Display the Review and Update from Type Def. Dialog

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2023 Q3

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2713392

Compare VIs Does Not Report Adding a Custom Run-time Menu on a Control as a Difference

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2016

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2731705

On Property and Invoke Nodes, the Right-click Help Menu for the Selected Property or Method is Missing

Workaround:

Fixed in LabVIEW 2024 Q3.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3

Added:

Jul 17, 2024

2786419

Palette Categories Are Visible Even When Empty

All the palette categories are visible by default.

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 1.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 1

Added:

Jul 17, 2024

2798144

MATLAB Script Nodes Break VIs

VIs containing MATLAB Script Nodes are broken because the script support DLL is not found.

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 1.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 1

Added:

Jul 17, 2024

2811695

LabVIEW Class Becomes Corrupted After Editing Private Data Control and Saving from Unsaved Changes Dialog

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 1.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 1

Added:

Aug 7, 2024

2800868

LabVIEW Numeric Control Fails to Paste Values Copied from Microsoft Outlook or Word

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 1.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3 Patch 1

Added:

Aug 7, 2024

2781966

Unexpected Save Dialogs When Maintaining Projects in Older Save Version

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

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Jul 17, 2024

2799931

Command Prompt Window Appears Briefly During Launch of LabVIEW on Windows

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Jul 17, 2024

2782815

LabVIEW Reports the Variable Configuration is Invalid After Deploying a Shared Variable

A shared variable with Bind to Source setting enabled and configured to bound to a network variable can be corrupted when a project loads. Deployment reports that the variable configuration is invalid.

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2024 Q1

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Oct 14, 2024

2771439

Slow Editor Responsiveness When Editing VIs in LabVIEW for Linux

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2023 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Oct 14, 2024

2818129

LabVIEW Sometimes Erroneously Reports It Cannot Save to Previous Versions When Using Packed Libraries with LabVIEW Classes

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Oct 14, 2024

2826505

LabVIEW Crashes When Using Custom VI Menus and Actor Framework

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Oct 14, 2024

2840560

LabVIEW Sometimes Crashes When Building Build Specifications With VIs That Use Sets or Maps of Classes

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Oct 14, 2024

2849639

LabVIEW 2018 Crashes When Opening Some VIs Edited in LabVIEW 2024 Q3

When saving a VI for previous to LabVIEW 2018, the VI can become corrupted such that LabVIEW 2018 crashes when opening it. This happens when the VI contains an Error Constant wired to the selector of a Case Structure.

Workaround:

Fixed in LabVIEW 2024 Q3 Patch 2.

Reported Version:

LabVIEW 2024 Q3

Resolved Version:

LabVIEW 2024 Q3 Patch 2

Added:

Oct 14, 2024

Additional Patch Information

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.

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).