[VIPM 2020 doesn't start]

@Jim Kring @Yann Report from my adventures with IT.

Short term solution: We found that it was the Cybereason ActiveProbe service that caused the run error. If that service was disabled, VIPM can launched without issue.

Long term solution: IT assigned a policy to my machine that disabled some Cybereason monitoring for .NET (they were vague). I was then able to use VIPM while ActiveProbe was running.

That's as specific as they were willing to get. Hope this helps!

[VIPM 2020 doesn't start]

Did whitelisting those folders fix the issue? If not, did you find a fix? I'm running into the exact same issue, and I've confirmed that disabling Cybereason fixes it. Would love to have a fix that I could take to IT to implement.