Bug Unity Launches into Safe Mode due to PlasticSCM Launch Tool Error

Some info:

Unity 2021.3.6f1
Version Control Package 1.15.18
I was affected by the Microsoft Windows Defender Update/Bug on Friday 1/13/23

I'm getting a weird error after I restarted Unity :

Library\PackageCache\com.unity.collab-proxy@1.15.18\Editor\PlasticSCM\Tool\LaunchTool.cs(362,13): error CS0103: The name 'BringWindowToFront' does not exist in the current context

I removed and reinstalled the Version Control Package, same error.

PlasticSCM will not work at all. If I remove the Version Control package, this error goes away (but I don't have SC)

Anybody have an idea what's happening? AFAIK, I didn't do anything on my end.

 

I will check with my IT dept. A month ago they revoked all admin privileges, so it may take me a while to get them to investigate.

Also, the PiXYZ plugin appears to have lost some functionality as well. Crap.

 

In the meantime, I removed Version Control, Shut down the Editor and my machine. Then I re-launched the Editor and re-installed the latest Version Control. This appears to be working. The PlasticSCM tab is back now.

I had removed the Version Control package, but I think I also needed the Editor restart. Still not sure what's up with PiXYZ...that probably needs a fresh install as well.

 

No, I had 1.15.18 already installed. The Microsoft issue with Windows Defender had to do with blocking actions that were triggering a false positive for malicious activity. The main result was many desktop/taskbar/start menu shortcuts were automatically deleted. I think the Version Control and PiXYZ somehow got roped into that (I had been using both regularly the day of the Bug).

Ultimately, it's MSFT's fault, not Unity's . I believe I'm all good. The problem didn't affect every user. But it did affect a lot of people (probably 20% of all employees in my large company).