anyone notice a difference between labview eve run on Windows 11 vs 10?

[mysticfree]

I wrote and compiled a program using LabVIEW 2016 64-bit under Windows 10 and it runs great.  When I run the EXE under Windows 11, it takes about 3~4 minutes before the main window appears.  I tried recompiling with LabVIEW 2024 Q3 64-bit under Windows 10 and get the same delayed opening under Windows 11.  So I tried compiling on the Windows 11 machine using LabVIEW 2024 Q3 64-bit, but that didn't help the delayed opening of the program.

I'm using the 64-bit version because the program reads large CSV files for data analysis that the 32-bit wouldn't handle.

Has anyone else has slowed opening of their EXEs under Windows 11?

[altenbach]

All my LabVIEW programs built as executables run equally well on windows 10 or 11.

Are you running any unusual antivirus or other "security" software?

(On a side note, I think you are talking about "building" an executable. A LabVIEW program is always "compiled", even if run in the development system. Most edit operation force an instant recompile)

[mysticfree]

Yes, you are absolutely correct - I'm building EXEs. I've been using LabVIEW for a couple of decades so I should have caught that.  So embarrassing.  

Anyway, both OS systems are within my company's network which is using Sentential Security.   So far, I've installed my program on 2 Windows 10s and 2 Windows 11 machines.  The programs run on Window 11s have the startup delay, which I thought was odd.  I check with IT to see if they have something special running on Windows 11 computers .... which would not surprise me.

Thank you for responding,

Ron

[rolfk]

Are you reading the large CSV files during startup? If so try to disable that for a test!

[softball]

Hi

A reason could be that a virus scanner kicks in when you first time try to access a network resource.

It is a well known problem in Windows 11 when you try to mount an ISO file from a NAS. You just wait and wait. As an example.

There is a procedure to bless your computer from this behavior. See this blog entry :

https://www.reddit.com/r/windows/comments/oz3g4r/why_has_image_mounting_become_so_slow_on_windows/

Regards

[mysticfree]

My program simply open a windows that will display the data and a secondary window that prompts the operator to select the file group.  So no data is initial read.

[softball]

Hi

Just came to remember this proxy issue, which a nice video by Doering mentioning slow file exchange with a myRIO and explained how to fix :

Turn the Automatically detect settings to OFF.

Regards

[mysticfree]

Thanks, softball.  I tried disabling the automatic proxy setup, reboot, but still had the same delay in startup. 

However, I did get a chance to run Sysinternal's "process monitor".  For the first 6 minutes, my application had a lot of "process profiling" operations intermixed with "thread create" and "thread exit".  After that, my program took about 20 seconds to set up and run.  This is definitely has to be interference from IT's aggressively paranoid security.

More troubleshooting needed ...