Local Security Authority LabView 2024 Q3

[Edinson1209]

El mensaje indica que Windows ha bloqueado la carga del módulo nimdnsNSP.dll, que pertenece a National Instruments y está relacionado con el servicio mDNS Responder.

Si tienes privilegios de administrador, abre Símbolo del sistema (cmd) como administrador y usa:

regsvr32 "C:\Program Files\National Instruments\Shared\mDNS Responder\nimdnsNSP.dll"

Esto intentará registrar la DLL nuevamente en el sistema.

Asegúrate que el archivo se encuentre en esta ruta, de lo contrario debes poner la ruta correcta en el (cmd) 

[Cinou]

Apparently the 2025 Q1 version of LV does not fixe the issue. It's surprising that NI hasn't solved this issue  with Win11 in the last year! For my part, I simply checked the "don't show this message again" box.

[ooth]

I hope when they do put out a fix it isn't just for the latest version. It should be for all versions because I'm running LV2021 on Win 11. Or at least versions supported on Win 11.

[josborne]

This is a worry of mine also. 

Some of us with active SSP’s still have lots of customers around the globe using legacy code from older versions of LV. These deployments need patches, too.  

---

---

@ooth wrote:

I hope when they do put out a fix it isn't just for the latest version. It should be for all versions because I'm running LV2021 on Win 11. Or at least versions supported on Win 11.

---

fact that customers can

[Darren]

---

@Cinou wrote:

For my part, I simply checked the "don't show this message again" box.

---

I'm curious... is this workaround (selecting 'don't show again') not working for some of you on this thread?

[josborne]

I'm curious... is this workaround (selecting 'don't show again') not working for some of you on this thread?

Yes, that is a workaround.  But I have hundreds of customers around the globe.  When they get this warning message, its bad for business.  It leads people to suspect that our software is malicious.  

[Frozen]

---

@Darren wrote:

---

@Cinou wrote:

For my part, I simply checked the "don't show this message again" box.

---

I'm curious... is this workaround (selecting 'don't show again') not working for some of you on this thread?

---

From what I recall, it did not work. It kept coming back... just like that cat.

[AllenInIowa]

---

---

From what I recall, it did not work. It kept coming back... just like that cat.

---

With our LabWindows 2017, it does indeed come back "the very next day."

Initially, I reported it to our IT group, thinking it was something potentially malicious.

[Bob_Schor]

I know this is a serious problem, but several recent responders obviously know the song "The Bug Came Back", whose chorus goes ---

   The Bug Came Back,

   the very next day --

   We thought it was a goner

   but the Bug Came Back

   and it would not stay awayyyy.

(with apologies to G.K.)

Bob Schor

[Mads]

When you build an installer you can choose to not include mDNS Responder....

I erroneously expected that to be the easiest workaround as we do not really need it for anything in our applications.The problem though is that the mDNS Responder service still gets installed 😫 . It is not listed as a component under NI Software in programs and Features, but it shows up as an installed service.

The culprit that causes this to happen in our case is the need to install the VISA RunTime. If we remove that, no mDNS Responder is installed. So for those that do not need that, you may have a solution for the DLL error...

PS.
I had not really noticed before that if you install an application built in LabVIEW on a 100% clean machine and then uninstall it, it will not uninstall the support components that came with it, even if there are no other applications depending on them. To get rid of the support files you manually have to find the NI Software entry under Programs and Features and uninstall all those too. At the very least there should be a dialog when you uninstall a or the last LabVIEW-built application asking the user whether to uninstall them as well.