Local Security Authority LabView 2024 Q3

[josborne]

Lots of us are experiencing this issue. Has anyone contacted NI to report it?  I don’t have an active subscription or SSP. 

[crossrulz]

---

@josborne wrote:

Lots of us are experiencing this issue. Has anyone contacted NI to report it?  I don’t have an active subscription or SSP. 

---

I just sent Darren a private message to make sure at least he is aware.

[Darren]

This issue has already been reported to NI R&D as Bug 367869.

For now, the workaround is to delete the DLL. Your NI software should still function properly without it.

[_Bryan]

---

@Darren wrote:

This issue has already been reported to NI R&D as Bug 367869.

For now, the workaround is to delete the DLL. Your NI software should still function properly without it.

---

Darren, quick question on deleting the DLL file(s). 

I noticed there are 2 of them, 1 in Program Files and 1 in Program Files (x86).  I am guessing that I should delete both of them?

My problem is that when I try to delete either file I get a message saying it is in use or open in another program.  I have stopped all the NI processes and services that I can find, but it still says file can't be deleted.  But I will note that I am using remote software to work on this computer, so that could be the issue.  The machine is in another state, but it could be possible to get someone local to the machine to help if needed.  

Any ideas?

[Darren]

I didn't realize there was a 32-bit version of the file as well. Yes, I think it does make sense to remove both.

The only way I've found to be able to delete the file is to reboot Windows into Safe Mode. After doing so, the file wasn't locked and I could delete it.

Make sure to keep a backup of both DLLs, just in case.

[josborne]

>>The only way I've found to be able to delete the file is to reboot Windows into Safe Mode

Oh wow that is a serious hassle.  

[Darren]

---

@josborne wrote:

Oh wow that is a serious hassle.  

---

I completely agree. I've pointed R&D to this forums thread and asked them to prioritize getting a fix/workaround implemented.

[josborne]

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.

[_Bryan]

I was just wondering if all my machines running executables are going to start having issues if Win 11 updates.  Production will not be happy about that.

[Frozen]

---

@Darren wrote:

I didn't realize there was a 32-bit version of the file as well. Yes, I think it does make sense to remove both.

The only way I've found to be able to delete the file is to reboot Windows into Safe Mode. After doing so, the file wasn't locked and I could delete it.

Make sure to keep a backup of both DLLs, just in case.

---

I was able to rename (not delete) both files with out jumping through any hoops. I have not noticed the pop up in the last couple days.

The pop-up specifically says "the module could not be loaded". I assume if you cannot delete it because it is in use, I suspect you should not see the pop-up. Conversely, if you are seeing the pop-up, you should be able to delete (rename) it since it is not being use.