labview runtime - slow pc start up

[Neil.Pate]

Hi Luke,

Resurrecting this old thread, I have tried the method you describe, but not having much success.

I can see the correct ProviderID in the registry, I can see how it should be re-shuffled to get the GUID, but I cannot actually run the command you described.

I have tried by coping the GUID directly from the nimdnsNSPTool.exe -list output, but it does not seem to work, I get FAILED (10013) response. Do you have any tips on what may be wrong here? 

EDIT: it seems I have to run this from a command prompt that has been opened with Administrator priviliges

[Luke_W]

Hey Neil,

Did the workaround end up being successful?

[ABachmann]

Nice to see that this problem got "priority" in 2012 (http://forums.ni.com/t5/LabVIEW/labview-runtime-slow-pc-start-up/m-p/2263060#M716777). Today is 2015 - and it's still present and can be solved by the same method (disabling the NI mDNS component).

[johnny_icon]

I can also confirm this registry fix. I use a lot of virtual machines, and it took me a long time to track this down. It started manifesting on a LabVIEW 2012 virtual machine, but it was inconsistent across several instances of that VM on various hosts. It also happened on LabVIEW 2013 and 2014 VMs, again, inconsistently across various hosts. Even after thinking I fxed it, it would re-appear.

This registry fix definitely did the trick. The symptom was slight different on a VM using VMWare Player. I experienced that the VM would boot as normal (fairly quick), but the Start Button/Orb and taskbar were missing for about 15-30 minutes, and then would eventually appear. After implementing the registry fix, I have rebooted various VMs on various hosts and have not seen the problem again.

[JosSaxion]

Breating some new life in this topic I come here with the concluding answer (especially for 64-bit):

The executable to use is nimdnsNSPTool.exe

These lines you can include in your deployment:

"C:\Program Files\National Instruments\Shared\mDNS Responder\nimdnsNSPTool.exe" -remove "981DF75B-898E-4c0c-B01C-5F181F817889"
"C:\Program Files (x86)\National Instruments\Shared\mDNS Responder\nimdnsNSPTool.exe" -remove "981DF75B-898E-4c0c-B01C-5F181F817889"

This will remove both instances of the problematic Service and make sure you can log out and in in an orderly fashion.

Cheers!

[Tesla1977]

I would love to use this method because we are installing 70 computers in the next weeks and always have to do a manual regedit afterwards.

Where can I include those lines in the deployment? I did find "Start program after installation", but i can only start one program and have to include this program into the project. Is there anything I'm missing? Using LV 2013.

[Luke_W]

depending on how you need to run them, you may be able to string together a couple executables in a batch file:

http://digital.ni.com/public.nsf/allkb/ED185175604CAA86862579BA00593002

[JosSaxion]

Hi,

We are using these lines in our installation:

(this is just a small part of the installation script)

**********************************************

:: Removing nimdnsNSP

set nimdnsNSPTool=National Instruments\Shared\mDNS Responder\nimdnsNSPTool.exe
if not exist "%ProgramFiles%\%nimdnsNSPTool%" goto nop
echo .
echo Removing nimdnsNSP
"%ProgramFiles%\%nimdnsNSPTool%" -remove "981DF75B-898E-4c0c-B01C-5F181F817889"
if not %errorlevel%==0 goto error
if not exist "%ProgramFiles(x86)%\%nimdnsNSPTool%" goto end
echo .
echo Removing nimdnsNSP (32-bit instance)
"%ProgramFiles(x86)%\%nimdnsNSPTool%" -remove "981DF75B-898E-4c0c-B01C-5F181F817889"
if not %errorlevel%==0 goto error
echo Done!
goto end

**********************************************

[JosSaxion]

Scratch the above, we've made it much simpeler. Also this is compatible for 32-bit and 64-bit:

:: STOP AND DISABLE nimDNSResponder Service
NET STOP /Y nimDNSResponder >NUL 2>&1
SC CONFIG nimDNSResponder START= DISABLED >NUL 2>&1

Easy and fast!

[JosSaxion]

Hm, just stopping the service doesn't quite cut it.

Tried it twice here now (damn that install takes long)

Fixxing it now so we will have a decent installer soon!