04-22-2025 04:55 PM - edited 10-30-2025 10:23 AM
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
05-06-2025 12:29 AM - edited 05-06-2025 12:29 AM
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?
06-09-2025 12:49 AM
All these issues are resolved. Please check the functionality in LabVIEW 2025 Q3 latest build.
06-09-2025 12:52 AM
Log unwired errors feature is supported in exe and PPL.
Yes, you need to set the token in the exe .ini file
07-08-2025 01:01 PM
@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
10-21-2025 03:20 PM - edited 10-21-2025 03:26 PM
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
11-04-2025 07:13 AM
@hunter_jki wrote:
I want to be able to indelibly disable this at runtime.
Hi Hunter,
You can have your application set the Application property "LogUnwiredErrors" to False to disable logging in the app. This property overrides the INI token.
Do you believe this is sufficient, or do you recommend additional mechanisms to disable the error logging?
Thanks,
Christina