Home Support Documentation Bugs

TestStand 2025 Q3 Known Issues

Updated Feb 6, 2026

Overview

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

Nov 10, 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:

Nov 10, 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:

    Oct 4, 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:

    Oct 4, 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:

      Oct 4, 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:

      Oct 4, 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
      3263807, 3375868

      Unable to select multiple Types in TS at the same time

      If the user has multiple local variables selected in the variable pane, right-clicking one of them deselects all but the one the user clicked. This behavior prevents the user from performing actions on multiple items.

      Workaround:

      Hold the Ctrl or Shift key while right-clicking and selecting actions to ensure all selected variables remain highlighted.

      Reported Version:

      TestStand: 2025 Q2 | TestStand: 2025 Q3

      Resolved Version:

      N/A

      Added:

      May 2, 2026

      Final Time Issue Listed

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

      Bug Number

      Legacy ID

      Description

      Details
      3047421

      CVI Editor UI Title Changes to a Different Language on Sequence Execution with Errors

      If the user is using CVI Editor UI and encounters an error during execution of the sequence file, the title changes to a different language other than English.
      This issue occurs in following case:
      Configure -> Station Option -> Execution Tab -> On Run-Time Error - Select Show Dialog Box.

        Workaround:

        If user perform any action that essentially refreshes the title then it goes back to English. One of the example of such action is to open a new sequence file.

        Reported Version:

        TestStand: 2022 Q4 | TestStand: 2023 Q4 | TestStand: 2025 Q2

        Resolved Version:

        N/A

        Added:

        Oct 4, 2025

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