LabVIEW executable files don't launch in W11

[moseulr]

Hello everybody

I have issues with launching LabVIEW executable files. The following is my computers history:

• In LV 2018 SP1 and W10 everything worked fine.
• Upgraded the PC from W10 to W11, while keeping all programs and data.
• Previously built executable files (built with LV 2018 SP1) still run fine.
• Errors appeared when I tried to build new executable files from changed VIs, using LV 2018 SP1. Found a workaround: Build offline (with the absence of LAN / WLAN / Mobile Network).
• Checked the compatibility between LV 2018 SP1 and W11 and found out that LV 2018 SP1 is not officially supported.
• Uninstalled LV 2018 SP1 and installed LV 2025 Q3.
• Building executable files now works flawlessly.
• When trying to launch the executable, I get the error "Auf das angegebene Gerät bzw. den Pfad oder die Datei kann nicht zugegriffen werden. Sie verfügen ggf. nicht über ausreichende Berechtigungen, um auf das Element zugreifen zu können."
• The English translation of this error is: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item".
• Side effects: Icon changes in the Windows explorer and file properties details (such as File description, copyright, Product version) disappear or get deleted.
• Interestingly, after building offline (with the absence of LAN / WLAN / Mobile Network), executable files can be launched. As soon as connected to the network, executable files begin to get corrupt again.

Does anybody have the same or a similar issue?

Does anybody have an idea how to resolve this?

Thank you for any hints in advance!

[Kyle97330 · Accepted solution]

You're making it sound like something is modifying the binary EXE file after it's created.  If this is truly happening, it's pretty bad.  That's the sort of thing a virus would do (or, in a weird "best case" scenario, an antivirus set to automatically "repair" infected files silently, and it's flagging your LabVIEW EXE files).  Do you have an antivirus installed?

I would recommend trying an experiment.  Get a program that can get hashes from files such as HashTab or HashCheck.  Then go offline, create a working EXE, test it, and get its hashes which you then save somewhere.  

Then go online, wait for it to stop working, and re-check the hash.  If it's changed, there is something on your system or your network that is altering your EXE files.

[moseulr]

Dear Kyle97330

Thanks for your suggestion, which I tried out with PowerShell and MD5 hashes. The result is, that as soon as the exe-File gets "corrupted", it is no longer possible to access it at all, so the MD5 hash code can no longer be calculated.

In the meantime, I have looked into MS Windows Defender logs and found out that there exist log-entries like the following:

2025-08-28T13:29:24.244 Engine-HIPS:Block on rule 0x1443614-..., State=1, Type=0x121, Inheritance=0x0, Process="C:\Windows\explorer.exe", ProcessCmdline="C:\WINDOWS\Explorer.EXE", Target="C:\Data\LabVIEW64bit\AIVRecKopie20250822\builds\AIVRecConcatenate.exe", TargetCmdline="", InvolvedFile="", SigSha=5bfb8c2f6f29850ab22083d57c2fa6def0dc4664

It seems that this has to do with HIPS (Host Intrusion Prevention System) and ASR (Attack surface reduction). I guess its related to our own company's policy, otherwise many other LabVIEW users would already have run into this problem.

So, I'll have to clarify with our company's IT department.

Thanks again for your post and best regards!

[Yogesh_Redemptor]

Looks this issue is related to PC/OS Settings.
I have faces similar issue, while the exe and relevant files are kept in C Drive or Desktop.

Try to move the executable to D Drive and Move the configuration/reports files to Drive (Or create all base folders manually and give full access to the files - in C Drive).

[moseulr]

You cannot cure this problem by assigning access rights as suggestedby Yogesh_Redemp. Access seems to be denied by Windows Defender directly. 

[bshvartsman]

Hello did you somehow resolved this issue?

[moseulr]

After some time I noticed that the exe-Files are no longer blocked. Either an exception* granted by my company's IT department or simply the elapsed time made it work. I don't know which of the two.

* I asked my company's IT department for such an exception

[Xonmyth]

---

@moseulr wrote:

• Errors appeared when I tried to build new executable files from changed VIs, using LV 2018 SP1. Found a workaround: Build offline (with the absence of LAN / WLAN / Mobile Network).
• Interestingly, after building offline (with the absence of LAN / WLAN / Mobile Network), executable files can be launched. As soon as connected to the network, executable files begin to get corrupt again.

Does anybody have the same or a similar issue?

Does anybody have an idea how to resolve this?

---

We run into this a 100% of the times. For us though, it is mostly on the customer's end. Internally, we have some Sentinel antivirus installed on the network itself ( I do not know how all that works). But any time were are connected to the company network, it makes our LabVIEW application go kuku.

It is a pain. I know some of our European customers also experience the same, but they are not on any corp wifi, their standard ISP seem to have some default-builtin security. 

Some times adding exception for ports accessed by LabVIEW helps and other times it is just a dead end. Only solution is to boot up the applications without the internet/ Install when offline etc.

Our IT also changes somethings every now and then but they do not share it with the engineering team, something that a  smart person would do. 

I would really like to see a oneshot solution for this, something that works across the board. 

[bshvartsman]

For me i fixed it with the call to the IT and they made the exeption on the specific folder.

But i keep it in mInd to build the .exe offline. Thank you.

I would wish that NI could fix it. I already ran in multiple issues which are known, but NI is not interested to fix it.

[MartinNilsson]

Have a look at your Microsoft Defender security rules.

Intune-Name: Executables that don't meet a prevalence, age, or trusted list criteria

Configuration Manager Name:Block executable files from running unless they meet a prevalence, age, or trusted list criteria

GUID: 01443614-cd74-433a-b99e-2ecdc07bfc25

• AsrUntrustedExecutableAudited
• AsrUntrustedExecutableBlocked

I've had the same problem for some time now and I saw in my recent defender actions, that my newly compiled Labview software was blocked from the administrator due to these rules. As age is a criteria, I figured out that if I wait a day or two the compiled software.exe works just fine again. I first considered asking for a work around from my IT department, but as I just have to wait a while, it is in my case a manageable nuisance and I'll just leave it at that.

@moseulr

This behaviour would eventually also explain your experience with the no longer blocked exe files.