Home Support Documentation Bugs

TestStand 2026 Q3 Known Issues

Created Aug 6, 2026

Overview

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

TestStand silently crashes when generating a test report for a large amount of data

When executing a test that generates a large amount of report data, TestStand may silently crash if you terminate the test after a significant amount of report data has been generated.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2020

Resolved Version:

N/A

Added:

Oct 11, 2021
1530687

Execution report information for Sweep loop records do not match with the runtime values for capture value parameter

If a Sweep Loop step contains a parameter configured as a Capture Value parameter (Use Existing parameter prior to TestStand 2021), and a step within the Sweep Loop modifies the variable associated with the parameter, the updated value for this parameter is not reported in the execution report.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand: 2019

Resolved Version:

N/A

Added:

Oct 11, 2021
3040732

Mismatch error in DMM IO session parameters in sweep loop steps

Numeric representation mismatch error occurs when using the DMM IO session parameter within a sweep loop. This happens during run-time in Python adapter when the sweep loop step includes the DMM driver’s IO session variable as a parameter.

    Workaround:

    There is currently no known workaround for this issue.

    Reported Version:

    TestStand: 2023 Q4 | TestStand: 2024 Q4 | TestStand: 2025 Q2

    Resolved Version:

    N/A

    Added:

    Apr 10, 2025
    3043763

    Edit LabVIEW VI Call dialog in C++ (MFC) or LV UI becomes not editable

    When user uses TestStand C++ (MFC) or LabVIEW UI along with installed LabVIEW, the Project Path and VI Path fields in the 'Edit LabVIEW VI Call' dialog become un-editable after adding multiple LabVIEW Action Steps.

    Workaround:

    The fields will be un-locked after switching focus away from the UI and bringing it back.

    Reported Version:

    TestStand: 2023 Q4 | TestStand: 2024 Q4 | TestStand: 2025 Q2

    Resolved Version:

    N/A

    Added:

    Apr 10, 2025
    3051525

    Crash and Exception in .NET Modules from Specify Module Dialog

    In Full Feature UI - Create Code or Edit Code from the Specify Module dialog for .NET steps causes a crash or throws an exception. This issue is not seen in Sequence Editor.

      Workaround:

      There is currently no known workaround for this issue.

      Reported Version:

      TestStand: 2025 Q2

      Resolved Version:

      N/A

      Added:

      Apr 10, 2025
      3058226

      Objects Not Released Properly when exiting TestStand

      You may encounter TestStand object leaks in certain scenarios when closing TestStand. Affected scenarios:
      Dragging and dropping a Boolean variable multiple times into a step (Ex. Statement Step).
      Similarly, opening the Configure Property Node dialog in a LabVIEW Action step (after setting the call type to Property Node Call).
      Problem occurs when using the Sweep Loop feature—simply opening the sweep loop table, clicking Export to CSV, and then closing the dialogs.
      When the user creates a new watch expression during a paused execution at a breakpoint.
      Add Goto Step in a sequence file.
      Opening the Property Selector tab after changing a Source Type in the Import/Export tool

      Workaround:

      There is currently no known workaround for this issue.

      Reported Version:

      TestStand: 2025 Q2

      Resolved Version:

      N/A

      Added:

      Apr 10, 2025
      3207514

      In TestStand, the XML help for a .NET method that includes generic data type parameters appears empty for all parameters.

      The TestStand .NET Adapter's XML Help fails to properly parse Generic Data Types resulting in blank XML Help for all parameters.
      XML help is shown when the Generic Data type is removed from the parameter list of the method.

      Image



      Workaround:

      Users should skip using generic parameters in their .NET class function calls,

      Reported Version:

      TestStand: 20.0.1 | TestStand: 2019 f4 | TestStand: 2020 | TestStand: 2021 | TestStand: 2021 SP1 | TestStand: 2022 Q4 | TestStand: 2023 Q4 | TestStand: 2024 Q4 | TestStand: 2025 Q2 | TestStand: 2025 Q3

      Resolved Version:

      N/A

      Added:

      Sep 22, 2025
      3943069

      Linux Graphics Rendering Issue in TestStand Blazor UI

      On some Linux configurations, the TestStand Blazor UI may show graphical rendering issues when running in Electron.
      Users may observe visual corruption or display inconsistencies caused by Electron GPU rendering behavior.

      Workaround:

      1. Open a command line terminal.
      2. Navigate to the TestStand Blazor UI installation directory: /opt/TestStandBlazorUI
      3. Run: ./TestStandBlazorUI --disable-gpu-compositing

      Reported Version:

      TestStand: 2026 Q3

      Resolved Version:

      N/A

      Added:

      N/A
      3909394

      Hidden Execution Dialogs Cause UI Blocking on Linux

      On Linux systems, execution dialogs and pop-up windows can appear behind the main TestStand Blazor UI window instead of staying in the foreground. This affects both TestStand-managed modal dialogs and independently launched windows. When this occurs, users cannot interact with the hidden dialog, and the application may appear unresponsive until the main window is moved or minimized.

      Workaround:

      If the UI appears unresponsive, minimize or move the main TestStand Blazor UI window to locate the hidden dialog, then bring that dialog to the foreground.

      Reported Version:

      TestStand: 2026 Q3

      Resolved Version:

      N/A

      Added:

      N/A
      3949014

      Missing PDF Output in Report Path Reports

      When multiple PDF reports are generated at the same time, some reports may fail to generate.

      This can occur when:

      • Multiple result processors have PDF generation enabled
      • Parallel or Batch process models generate one report per test socket, UUT, or batch

      Workaround:

      There is currently no known workaround for this issue.

      Reported Version:

      TestStand: 2026 Q3

      Resolved Version:

      N/A

      Added:

      N/A
      3962272

      Report Indentation Lost in Simple User Interface

      In the TestStand Simple User Interface, execution report content may not appear indented as expected during the initial execution. As a result, the report hierarchy and step structure are not displayed correctly, which reduces readability.

      This issue occurs only during the first execution.


      Workaround:

      • Restart the execution. After restart, the report view appears as expected.

      Reported Version:

      TestStand: 2026 Q3

      Resolved Version:

      N/A

      Added:

      N/A
      3977068

      MDS does not currently support concurrent executions

      When running a sequence file using the Parallel process model, may intermittently fail while generating system metadata for concurrent executions.

      The same sequence runs successfully with the Sequential process model.

      Include relevant system information, steps to reproduce, and any workarounds.

      Workaround:

      There is currently no known workaround for this issue.

      Reported Version:

      TestStand: 2026 Q3

      Resolved Version:

      N/A

      Added:

      N/A

      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

       

      Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

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