Local Security Authority LabView 2024 Q3

[Darren]

Yes, that's also correct. The Sys Config installer installs those (previously) problematic DLLs. So any machine that runs your LabVIEW EXEs will need Sys Config 2025 Q2, installed either manually, or as part of your LabVIEW-built installer.

[Mads]

@GabeJ replied "Correct" to this 

@Mads wrote:

I assume this (the System Configuration 2025 Q2 update) will fix the mDNS issue regardless of whether the installers you make afterwards actually include the System Configuration component...correct?

So, when you @Darren say that any machine running your LabVIEW exes will need Sys Config 2025 Q2 there seems to be a contradiction:

Is it sufficient that the installer of the exe was made one a machine that had Sys Config 2025 Q2 installed, or do we actually have to include Sys Config 2025 Q2 as a component in all installation sets that risk including mDNS (i.e. an exe that requires VISA e.g and so gets mDNS included, but not Sys Config itself)?

[rolfk]

You may have to to make sure to specifically select the NI System Configuration 2025Q2 installer in the Installer Build Specification. That Build setting often lets you select different versions of packages if they were ever installed on your computer, since they reference the installers themselves that are cached, not the installed files on your system (of which you can only have one version installed when it is about drivers like System Configuration).

[Mads]

Just did a quick test now using a clean virtual Win 11 machine comparing an installer made with LabVIEW 2025 Q1 with System Config 2025 Q2 installed: First with an installer without that component included and then with (well, I chose to include the component: System Config 2025 Q2 RunTime only, which added 140 MB to the installer size)...

Both installers install what seems to be the exact same mDNS dll; Dated 11 Feb 2025 and signed with a ceritificate dated 23. June 2024...

I then used an old installer created prior to the SysConfig 2025Q2 install on the development machine (still LabVIEW 2025 Q1 though) and it installed an mDNS dll from 2023. So things did change, and including the System Config 2025 component does not seem required for that change...

(My test machine in this case did not complain either way though, so whether the new DLL / certificate is OK was not clarified. I'll need a different test machine setup that recreates the original issue for that...).

[GabeJ]

11 Feb 2025 is the correct date for that DLL.  Look more closely at the signatures, though.  There is an NI signature on there that was applied on June 23, 2023.  The important thing, though, is the second signature, from Microsoft, that was applied on December 16, 2024.  That certificate has the Windows Software Extension Verification EKU, which is what should allow this DLL to load in a secure LSA context.