LabVIEW VI Analyzer Toolkit 2026 Q3 Bug Fixes

Overview

The following items are notable issues fixed between the release of LabVIEW VI Analyzer Toolkit 2026 Q1 and LabVIEW VI Analyzer Toolkit 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 VI Analyzer Toolkit.

Bug Number

Legacy ID

Description

Details

Broken VIs in VI Analyzer Toolkit: Gen align vertical.vi and Gen align horizonal.vi fail to load 'Merge Errors' node

The vi’s Gen align vertical.vi and Gen align horizonal.vi located in the llbtoanalyze.llb file under the VI Analyzer Toolkit examples folder fail to load correctly due to a broken dependency on the 'Merge Errors' function.

Steps to Reproduce:

1. Open LabVIEW.

2. Navigate to LabVIEW 2025Q3\examples\VI Analyzer Toolkit\llbtoanalyze.llb.

3. Open Gen align vertical.vi or Gen align horizonal.vi.

4. Observe the broken run arrow and error message indicating a missing or broken 'Merge Errors' node.

Workaround:

Manually replace the broken 'Merge Errors' node with a new instance from the Functions palette and rewire the connections. This resolves the issue and restores VI functionality.

Image

Image

Reported Version:

LabVIEW VI Analyzer Toolkit: 2025 Q3

Resolved Version:

LabVIEW VI Analyzer Toolkit: 2026 Q3

Added:

Jul 15, 2025

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