VeriStand 2025 Q4 Known Issues

Overview

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

DisconnectFromSystem API undeploys on windows target even though undeploy_system_definition is set to false

When the DisconnectFromSystem API is called with undeploy_system_definition set to false, it undeploys the system on a windows target instead of disconnecting, causing subsequent call to the ConnectToSystem API to fail with an unexpected error.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

VeriStand 2023 Q4 | VeriStand 2024 Q1 | VeriStand 2024 Q2 | VeriStand 2024 Q3 | VeriStand 2024 Q4 | VeriStand 2025 Q1

Resolved Version:

N/A

Added:

Jan 24, 2025

2949201

The system definition deployed to the VeriStand Project Explorer Gateway gets undeployed when the project is opened in the VeriStand application

When a system definition is deployed to the VeriStand Project Explorer Gateway by a VI, .NET, or Python program, it will become undeployed if the project is subsequently opened in the VeriStand application.

Workaround:

If the Gateway Project services are not needed, start the Gateway by running veristand-server before performing the deploy operation.

Reported Version:

VeriStand 2023 Q4 | VeriStand 2024 Q1 | VeriStand 2024 Q2 | VeriStand 2024 Q3 | VeriStand 2024 Q4 | VeriStand 2025 Q1

Resolved Version:

N/A

Added:

Jul 15, 2025

3039128

Numeric control Decimal Value Min, Max value displayed out of range

The VeriStand numeric control for Integer Decimal values currently supports a practical range of -999,999,999,999,999 to 999,999,999,999,999 (15 digits), despite displaying the theoretical 64-bit integer range (-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807).

Workaround:

There is currently no known workaround for this issue.

Reported Version:

VeriStand 2025 Q1

Resolved Version:

N/A

Added:

Jul 15, 2025

3156806

FMU Execution Causes Segmentation Fault on Linux RT when Stack Size Limit Is Exceeded

Running an FMU model in VeriStand on Linux Real-Time targets results in a segmentation fault if the default stack size limit of 256 KB is exceeded, due to a stack overflow.

Workaround:

For VeriStand 2023 or later, increase the thread stack size by editing the lvrt.conf file located at /etc/natinst/share and setting:
PosixThreadStackSizeLimit = 2048
This increases the stack size to 2 MB, helping prevent overflow during FMU execution.

Reported Version:

VeriStand 2024 Q4

Resolved Version:

N/A

Added:

Jul 17, 2025

3271315

Incorrect deployment status shown in VeriStand UI on disconnecting the deployment on RT Target

When a System Definition is disconnected using the DisconnectFromSystem .NET API or the VeriStand Disconnect step with undeploy set to false,  VeriStand UI incorrectly changes the status from 'Connected' to 'Idle'. This misleading status may suggest the System Definition has been undeployed, although it remains deployed.

Workaround:

This is only a UI display issue; the disconnect workflow itself is not impacted.

Reported Version:

VeriStand Steps for TestStand 2025 Q1 | VeriStand 2025 Q2 | VeriStand 2025 Q3

Resolved Version:

N/A

Added:

Oct 9, 2025

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

 

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