Executable Internal Warnings

[ShockHouse]

I'm getting issues with executable's that work in LabVIEW 2019-2025 Q1, but now issue warnings when using 2025 Q3 Beta.

Example 1: One application (both 32 and 64-bit) shows the following warning. After the warning the application appears to work just fine. This is the TASC_32 log attached below.

Example 2: One application (both 32 and 64-bit) shows the following warning. After the warning the application appears to work just fine. This is the TestPointConfigEditor log attached below.

Actually looks like it's not just the EXE, but also when I open the PPLs built in previous versions I get the same "LVCPUFunctions.cpp" error. I've attached a PPL (NIPM_API.lvlibp in zip file) that was built in 2019, but when opened in 2025 Q3 Beta 64-bit, you will get a Warning. It has no other PPL dependencies. Note that if you open LabVIEW, then open the PPL, you will get the warning. If you close the PPL, and then open it again without closing out LabVIEW, you won't get a warning a 2nd time. Only on the first instance.

[ShockHouse]

VI Package Manager is another executable that will give the "LVCPUFunctions.cpp" warning using VIPM 2025 Q1 version.

[Christina_R]

Thanks for testing the Beta and for reporting this issue! I've filed Bug 3122204.

[Christina_R]

These warnings will not be displayed in the released version of the LabVIEW 2025 Q3 run-time engine.

The VIProperties warning is letting us know that you're using a deprecated property. 

The LVCPUFunctions warning is letting us know that your system has an unexpected CPU configuration.

We don't believe either of these will have adverse effects. (We just have a Beta be more aggressive about reporting potential issues than we do with a released version)