VI Package Manger will not launch

[jfuchsdmp]

I cannot get VI Package Manager to open on my machine since installing LabVIEW 2020.

I have searched the knowledge base, forums, and google for an answer, and found no direct result.

Whenever I launch VIPM, all I get is the icon on the taskbar and the task in task manager, but it never opens a splash screen or anything.

I also get a small error splash that appears behind labview's main launch screen, which I assume is related.

I just expanded the memory on my laptop, hoping that would alleviate the issue, but there was no change.

I apologize if this is the wrong forum, I searched for topics about VIPM and them in this directory.

My machine is running windows 10.

[FireFist-Redhawk]

Have you tried running VIPM as admin? I've also had issues at times with getting it to load, and that was a solution at least once so I decided a while back to run it as admin every time.

[jfuchsdmp]

There is no change when running as Admin.

I have tried un-installing & re-installing the entire environment twice with no effect as well.

My IT department has given up at this point trying to figure it out, so I am hoping someone on the interwebs has seen this before.

[FireFist-Redhawk]

Hardcore longshot, but what antivirus software do you have? My entire company is going through this huge kerfuffle because we use an AV software called Cybereason and recently it got an update to where it blocks all .NET calls from all compiled LabVIEW executables. Had to set up an exclusion list of PCs because there's no other solution at the moment. VIPM was one of the programs that would not work with Cybereason fully enabled.

[jfuchsdmp]

At the moment we run Sophos. I'll see if I can get it whitelisted and if that makes a difference.

[FireFist-Redhawk]

Why on earth is the error showing your path to the exe as starting with C:\:\ ?

I've never seen anything like that... Is it supposed to be that way?

Then there's the random zzzzzzzzzz subfolder. What's going on there?

[jfuchsdmp]

Thus part of the confusion, I can't locate that directory anywhere, and I haven't figure out why VIPM is trying to look there.

[billko]

---

@jfuchsdmp wrote:

Thus part of the confusion, I can't locate that directory anywhere, and I haven't figure out why VIPM is trying to look there.

---

That's a malformed Windows path.  It's no wonder you can't do anything with it.  I doubt you'll even be able to uninstall it.  Truthfully, it appears that someone botched the install - badly.  At this point, there are no suggestions that I am willing to make.