This is rippling it's way across the net. Apparently some businesses run this stuff on systems that they should not. Of course, there's no one there on the weekends so it's taking out their stuff by sucking all of the memory up on the systems. This is going to make the news ... probably in a few days once it all percolates up and the total impact is realized.
I've disabled the service. Hopefully I can update MBAM's database with the service killed so I can get around this. If I turn the service back on, I'm not sure I can get the update loaded before my systems eat themselves.
How does something like this go out without being tested? I think someone was perhaps asleep at the wheel. It's not OS specific either ... it has killed Win7, Win8, and Win10 machines in my house.