Local Security Authority LabView 2024 Q3

[aeastet]

I updated to 2025 Q4 on Friday. I am still seeing this error in my event log. I do not think you guys have fixed this completely yet:

[GabeJ]

Are you still seeing the LSA pop-up?  The Microsoft signature on nimdnsNSP.dll will permit the DLL to load in the local security authority context and will eliminate any warnings or pop-ups related to lsass.exe.  It won't prevent warning logs if something attempts to load that DLL in another security context (in this case, some particular instance of svchost.exe).

[aeastet]

We do not see the popup, but the issue we are having is that windows defender is not allowing a few of our computers to boot. If we uninstall the NI software from our computers it will boot. When we put LabVIEW and the drivers back on no boot and blue screen. IT seems to have narrowed it down to the NI dll. I was hoping that updating to a version that was signed my Microsoft would help. It does seem that we can bitlocker the computer to get it to boot but we have to do that every time. 

[GabeJ]

😧

Yes, that's far worse than just an error in the event logs! Would you mind sharing more info here or through official support channels (text from the blue screen, memory dumps if available, exact version of Windows, etc.)?

[aeastet]

Yep let me see if I can pull that together. We have seen two of our systems do this out of many (150ish). It is a little strange that we have so many computers running but we only see this issue on two of them. They are all running Windows 11 but I will get the exact version on the two we are seeing issues with. I will also try to get the rest of the info you asked for. 

[aeastet]

---

@GabeJ wrote:

😧

Yes, that's far worse than just an error in the event logs! Would you mind sharing more info here or through official support channels (text from the blue screen, memory dumps if available, exact version of Windows, etc.)?

---

Here is the power point that we sent to IT. Keep in mind I did try installing the 2025 Q3 core components after this power point was made. We did not realize that this tread was out here so he had not tried upgrading at that point. It did not help and we are still having the issue of the dll singing issue. I will try to get the rest of the info as it comes available.

[GabeJ]

Thanks for that info.  I'm curious why ELAM would be involved at all.  nimdnsNSP.dll is a user-mode DLL; I wouldn't expect it to be loaded in a boot-start driver context.  Did the blue screen actually call out nimdnsNSP?