Anyone else fighting MS Defender false positives (Supma.A & Wacatac) after the overnight cloud updates?
Once again, we walked into the office this morning to find yet another surprise overnight update to our cloud-hosted ConnectWise stack—and yet another round of broken tools.
This time, Automate got hit. The unexpected release is causing Microsoft Defender to completely block the Solutions Center from opening, flagging it as Trojan:Win32/Supma.A.
This comes right on the heels of the absolute nightmare from the last fortnight, where we've been battling Defender nuking active ScreenConnect Agents after that botched update (the one they finally halted rollouts for because it was wiping out working deployments as Trojan:Script/Wacatac.C!ml). We are still fighting that fire, and now this.
Seriously, when will ConnectWise release a patch for the tools we pay them to host that doesn’t break existing functionality or silently yank features? No advance warnings, zero communication during the fallout, and non-existent support when we're left trying to piece our environments back together.
Is everyone else just writing global exclusions at this point, or has anyone actually managed to get a straight answer out of support?