Local Security Authority LabView 2024 Q3

[Basilgeuse]

This is all valid. I suppose I made some assumptions on how users are deploying these NI applications.

In the context of my environment, I work in an organization with managed devices. Our machines are managed with Intune. Users are are only able to install applications in Company Portal, and are unable to install applications without Administrator credentials. When packaging this application within Intune, I simply added 2 lines in the install script to install 2 separate self-signed certificates for the dll files in both the Program Files and Program Files (x86).

However, I did share in your concerns. Shortly after our first interaction, I decided to work on an AppLocker profile to whitelist the dll files deployed via a custom OMA-URI policy in Intune. The trouble here is the way AppLocker and WDAC handle whitelisting of dll files. As far as I know, there isn't a way to allow 2 specific dll files, rather what happens when the policy gets pushed to the machine, it ONLY allows those 2 dll files... blocking all required dll files Windows uses to operate.

The solution there is to allow default dll rules, which essentially whitelists every dll file in Program Files, Program Files (x86), and Microsoft Windows dlls. Obviously this is it's own security risk in an unmanaged environment, just blanket allowing ANY dll file that exists in the Program Files folders, but I believe it to be the lesser of 2 evils.

[rolfk]

---

@Basilgeuse wrote:

However, I did share in your concerns. Shortly after our first interaction, I decided to work on an AppLocker profile to whitelist the dll files deployed via a custom OMA-URI policy in Intune. The trouble here is the way AppLocker and WDAC handle whitelisting of dll files. As far as I know, there isn't a way to allow 2 specific dll files, rather what happens when the policy gets pushed to the machine, it ONLY allows those 2 dll files... blocking all required dll files Windows uses to operate.

---

That looks like a glaring bug to me right there! Adding entries to the white list should absolutely and definitely not make it forget its default Windows DLLs at all. Either you overlooked a setting when creating that white list, or this Intune application is not even worth the paper it is written on. Ohh wait there is no paper!

[AndrejValand]

Also had this problem since LabView 2024 Q3 install.

Renaming nimdnsNSP.dll to nimdnsNSP.dll.bak solved it for me. No need to go to Windows save mode to do it. I found this to be the simplest solution.

But its not a nice quick-fix. Some part of LabView is needing this probably something that i don't use but its not 100% functional because of it now... 

Hope Emerson fixes this in the next update with a proper signed file or whatever is needed...

[Testtech99]

I just installed 2025 Q1.  Since I am on this thread, we can assume this is not fixed yet.

[jyoung8711]

I also encountered this issue after installing 2025 Q1.

Renaming the dll worked for me.

[Yamaeda]

---

@josborne wrote:

Thank you, Darren.  

It's especially annoying that a Windows Update caused the issue, because its not something in my own code or something I could have foreseen.  I have customers around the globe (as does NI) that might suddenly start experiencing this issue now.

---

Unfortunately this is neither the first nor the last time a Windows Update or an AV messes up a LV install ...

[josborne]

I want to point out that this issue was first reported in these forums on 09-15-2024.  That as 4.5 months ago.  No patch yet.

[AustinMan@NI]

Hello Everyone,

A note to let you know there are multiple R&D developers actively working to resolve this issue. I am not qualified to set expectations on what the solution will be, or when it will be published. As soon as we have more news an update will posted. Thanks for your patience. 

Regards,

David Corney

Principal Technical Support Engineer.

[AllenInIowa]

What are the odds that a fix will be released for LabWindows as well? I reinstalled LabWindows/CVI 2017 the other day and got that alert -- had never seen it before. 

[AustinMan@NI]

Allen, I have informed the R&D developers you are seeing this issue with LW/CVI. 

Still no concrete date when a release will available. Based on the comments, progress is being made.