01-17-2025 09:23 AM
Has anyone seen this before (see attached video) and know what the root cause is or how to get rid of it?
I first noticed that a new application I had built in LabVIEW 2024Q3 32 bit on Windows 11 would show the outline of a window just after launch that would then go away...This happened no matter how simple the program was made, it did not need to have anything in it at all (a VI with an event structure alone e.g.).
However I see now that this actually happens when launching LabVIEW as well. The content of the popup window does not render so I am unable to get any hints from that on what the window is (in cases where an application e.g. searches for a dll during bootup you can normally grab a video of the window and slow it down to see what is going on, but in this case there is nothing actually shown in the window).
Solved! Go to Solution.
01-17-2025 02:44 PM
Copying and running one of these LabVIEW built applications to another machine with a LabVIEW 2024Q3 installation that did not have this issue beforehand copied the problem to LabVIEW on that machine too...(!)
So unless something in the build application is actually affecting something in the whole LabVIEW environment it is beginning to look like a virus/malware of some sort...but it only affects LabVIEW applications this way so that is a bit strange 😖
01-17-2025 03:00 PM
One additional observation is that if LabVIEW or the LabVIEW made application is run as admin the pop-up window is never shown 😮
01-17-2025 03:07 PM - edited 01-17-2025 03:20 PM
For LabVIEW-made executables, I already had a similar issue that was caused by my top-level VI simply being in an lvlib. Taking it out of any library made the flicker disappear.
See these threads:
https://forums.ni.com/t5/LabVIEW/2015-Fast-File-format-disrupts-Window-Run-Time-Position/m-p/3238306
For LabVIEW itself, I don't know, maybe you have a toolkit with a project provider that runs when LabVIEW starts?
EDIT: I just noticed the second linked thread was started by you, so that may not help you much 🙂 ...
Regards,
Raphaël.
01-17-2025 05:32 PM
An update of LabVIEW from 2024Q3 f1 to fix 2 seems to have removed the issue on both machines...not sure what the issue really was, but hopefully it will stay away from now on.