[New Feature] Log Unwired Errors

[Christina_R]

In LabVIEW 2025 Q3, you have the option to record unwired errors in a log file, independent of whether you enable the Automatic Error Handling dialog to report them.

Known Issues

1. The Explore button is the wrong style and remains “pressed in” after clicking it.
2. The Log file for current session path doesn’t populate when you first enable Log unwired errors.
3. The log may contain errors generated by VIs that are part of the LabVIEW IDE.

[Cloedu72]

Is the functionality also supported in an executable or in PPL (debug version)? 

Can the keyword also be entered in the INI file of the exe?

[Janaki.M]

All these issues are resolved. Please check the functionality in LabVIEW 2025 Q3 latest build.

[Janaki.M]

Log unwired errors feature is supported in exe and PPL.
Yes, you need to set the token in the exe .ini file

[Christina_R]

---

@Janaki.M wrote:

Log unwired errors feature is supported in exe and PPL.
Yes, you need to set the token in the exe .ini file

---

LogUnwiredErrors=True

[hunter_jki]

This seems like a giant security risk. I can open any LabVIEW exe, go modify the ini next to it, then get access to explicitly unwired error messages that may include sensitive data, property information and call chains. I want to be able to indelibly disable this at runtime, since checking the messages of every unwired error in every corner case is not feasible.

This is the guidance I am providing customers in our cyber security Software Development Plan

Unwired Error Leaks New for LabVIEW 2025 In the LabVIEW Options on the Block Diagram tab there is a new option to `Log Unwired Errors`. This option is also available in executables via the ini file next to the built exe. Setting the ini key LogUnwiredErrors=True means unwired errors will be dumped to disk. This is a potential security risk as it could leak internal data and call chains, and it can be modified by end users.