LabVIEW runtime engine won't install

LabVIEW runtime engine won't install

Post by travispap » Fri, 25 Apr 2008 13:10:05


I have a customer who has a problem where the LabVIEW 8.5 Runtime Engine refuses to install.  I have built an installer that includes my program, LabVIEW 8.5 Runtime Engine, and the NI-VISA Runtime and whenever she tries to run the installer, she gets the message "no software will be installed or removed".
 
When I take her into Add/Remove programs, she can uninstall my program, but there is no National Instruments or LabVIEW-related items in her list.  (If we go ahead and uninstall my program it does uninstall [and we can verify that it is gone by browsing with Windows Explorer], the next time that we try to run the installer, it does install my program, but it makes no mention of LabVIEW Runtime Engine nor NI-VISA Runtime.)
 
Apparently, she has been flailing with this for several weeks now with another tech support guy in my company.  I'm not sure what all he has had her try, but there is another really weird symptom in all of this.  When she runs the installer and gets to the install paths page of the wizard, it shows the appropriate path for my part ("C:\Program Files\<My Program Folder>"); however, for the NI stuff it wants to install everything to her desktop by default!  Appearantly she has done this in the past, because she said that she "keeps finding this folder called shared on my desktop.  I keep deleting it."
 
Since we don't have the ability to properly uninstall the NI stuff, I had her delete the Shared folder again off her desktop.  I had her tell me what else she saw on her desktop and I didn't hear anything else that sounded like stuff that belongs in "C:\Program Files\National Instruments".  I then had her empty her recycle bin.  I then had her download an install CCleaner in the hopes that when we cleaned her registry that it would clean up the mess.  When she scanned her registry, it did find a large list of National Instruments related things to remove.  I had her back it up and remove everything in the scan list.
 
We then rebooted the computer and tried to reinstall--no luck.  Same problem: "no software will be installed or removed".
 
I also had her download the 95 MB version of the National Instrument 8.5 Runtime Engine directly from ni.com--again, no luck.  I had her try to do the install with the default configuration and it did not install the Runtime Engine.
 
She has McAfee software w/ firewall and Ad-Aware installed on her computer and uses them and it doesn't sound like she had had any other issues with her computer.  (The only thing she mentioned was trouble getting Skype to work so she uninstalled it.)
 
So my questions are why does LabVIEW 8.5 Runtime Engine want to install to her desktop by default and what do I have to do to her computer (via phone and email) to let National Instruments stuff get installed on it?
 
Thanks
 
 
 

LabVIEW runtime engine won't install

Post by tst » Fri, 25 Apr 2008 16:40:09

I'm not sure if this will help, but you can try searching the forums for a program called MSIBlast.exe. It's supposed to allow you to remove any NI related software completely. I don't know if it will work better than CCleaner, but it's probably worth a shot.

 
 
 

LabVIEW runtime engine won't install

Post by travispap » Sat, 26 Apr 2008 01:10:07

Thanks for the tip on the MSIblast--we'll give that a try. 
 
 
 

LabVIEW runtime engine won't install

Post by Karunya_ » Sat, 26 Apr 2008 06:10:06

Is that the only computer where this problem is happening? MSIBlast does not remove references to registry keys. It just run uninstallers. I have attached a doc that lists the steps to remove NI software. Try that out as well.


Clean Reinstall Procedure.doc:
http://www.yqcomputer.com/
 
 
 

LabVIEW runtime engine won't install

Post by travispap » Sat, 26 Apr 2008 13:40:09

Thanks--MSIBlast did the trick.
 
After cleaning up with MSIBlast, the installer wanted to install NI things to "C:\National Instruments Downloads", which is better than the desktop but not what the default should have been.  But all's well...