Unable to start, uninstall or install labview

[bibaHull!]

Hi,

when we boot up the PC in our lab we get the error message shown in the attachment.

When we try to start labview via the start menu or by opening a .vi file, nothing happens.

When we try to uninstall via apps and features, nothing happens.

When we try to reinstall Labview via the install.exe, nothing happens.

This seems to be the case ever since installing python via anaconda.

Is there any way to fix this without resetting the whole pc?

Thanks for the help.

[Dobrinov]

---

@bibaHull! wrote:

Hi,

when we boot up the PC in our lab we get the error message shown in the attachment.

When we try to start labview via the start menu or by opening a .vi file, nothing happens.

When we try to uninstall via apps and features, nothing happens.

When we try to reinstall Labview via the install.exe, nothing happens.

This seems to be the case ever since installing python via anaconda.

Is there any way to fix this without resetting the whole pc?

Thanks for the help.

---

The error in the error message indicates that the problem lies with VIPM, i.e. the VI Package Manager. Boot the machine into safe mode and uninstall that first. Reboot normally and see how it goes from there.

For critical machines I'd advise to always make a complete system backup before making bigger changes and in regular intervals afterwards. Properly partiotioning the drive can minimize the backup size too.

[billko]

---

@Dobrinov wrote:

---

@bibaHull! wrote:

Hi,

when we boot up the PC in our lab we get the error message shown in the attachment.

When we try to start labview via the start menu or by opening a .vi file, nothing happens.

When we try to uninstall via apps and features, nothing happens.

When we try to reinstall Labview via the install.exe, nothing happens.

This seems to be the case ever since installing python via anaconda.

Is there any way to fix this without resetting the whole pc?

Thanks for the help.

---

The error in the error message indicates that the problem lies with VIPM, i.e. the VI Package Manager. Boot the machine into safe mode and uninstall that first. Reboot normally and see how it goes from there.

For critical machines I'd advise to always make a complete system backup before making bigger changes and in regular intervals afterwards. Properly partiotioning the drive can minimize the backup size too.

---

The error message shows that VIPM is looking for the runtime in a corrupted path (there are two backslashes together and this is where the version number of the runtime should be).  This is likely to be caused by a corrupt LabVIEW install.  This going to be very difficult to fix, now that NI has implemented NIPM.

[Dobrinov]

---

@billko wrote:

---

@Dobrinov wrote:

---

@bibaHull! wrote:

Hi,

when we boot up the PC in our lab we get the error message shown in the attachment.

When we try to start labview via the start menu or by opening a .vi file, nothing happens.

When we try to uninstall via apps and features, nothing happens.

When we try to reinstall Labview via the install.exe, nothing happens.

This seems to be the case ever since installing python via anaconda.

Is there any way to fix this without resetting the whole pc?

Thanks for the help.

---

The error in the error message indicates that the problem lies with VIPM, i.e. the VI Package Manager. Boot the machine into safe mode and uninstall that first. Reboot normally and see how it goes from there.

For critical machines I'd advise to always make a complete system backup before making bigger changes and in regular intervals afterwards. Properly partiotioning the drive can minimize the backup size too.

---

The error message shows that VIPM is looking for the runtime in a corrupted path (there are two backslashes together and this is where the version number of the runtime should be).  This is likely to be caused by a corrupt LabVIEW install.  This going to be very difficult to fix, now that NI has implemented NIPM.

---

My assumption is that VIPM is running at startup and in its attempts to start its service is preventing the NI Package Manager from doing anything. In the worst case one just boots into safe mode and manually deletes everything NI related, cleans the registry (that was always fun) and installs everything all over. Wouldn't wish it to anyone, but in the worst case it worked for me. Or at least it did years ago when I had to do it myself for the last time (no VIPM back then).

[billko]

---

@Dobrinov wrote:

---

@billko wrote:

---

@Dobrinov wrote:

---

@bibaHull! wrote:

Hi,

when we boot up the PC in our lab we get the error message shown in the attachment.

When we try to start labview via the start menu or by opening a .vi file, nothing happens.

When we try to uninstall via apps and features, nothing happens.

When we try to reinstall Labview via the install.exe, nothing happens.

This seems to be the case ever since installing python via anaconda.

Is there any way to fix this without resetting the whole pc?

Thanks for the help.

---

The error in the error message indicates that the problem lies with VIPM, i.e. the VI Package Manager. Boot the machine into safe mode and uninstall that first. Reboot normally and see how it goes from there.

For critical machines I'd advise to always make a complete system backup before making bigger changes and in regular intervals afterwards. Properly partiotioning the drive can minimize the backup size too.

---

The error message shows that VIPM is looking for the runtime in a corrupted path (there are two backslashes together and this is where the version number of the runtime should be).  This is likely to be caused by a corrupt LabVIEW install.  This going to be very difficult to fix, now that NI has implemented NIPM.

---

My assumption is that VIPM is running at startup and in its attempts to start its service is preventing the NI Package Manager from doing anything. In the worst case one just boots into safe mode and manually deletes everything NI related, cleans the registry (that was always fun) and installs everything all over. Wouldn't wish it to anyone, but in the worst case it worked for me. Or at least it did years ago when I had to do it myself for the last time (no VIPM back then).

---

Well, it's easier to uninstall/reinstall VIPM than trying to uninstall/reinstall LabVIEW with NIPM, that's for sure.  You can easily leave your machine in an unbootable state if you screw anything up.  It's even more difficult to uninstall/reinstall now than it was when you last tried it!  😞

I agree that it could be VIPM not finding the runtime could be a VIPM issue, but it could also be a bad LV install.

[Bob_Schor]

From a few very sad experiences I had with LabVIEW 2017 (and NIPM), which I tried to "fix", I think you may be looking at doing as careful and complete a backup as possible, wiping the hard drive, and reinstalling everything (starting, of course, with Windows).  I found that the more I tried to "fix" the problem, the worse it became ...  At least, now I know how to safely remove NI software without disturbing anything else (but it doesn't sound like that's an option for you ...).

Bob Schor