> Microsoft has been secretly adding more powerful features than Process Hacker via their SAC product – SAC has no security whatsoever by design – they're clearly targeting the project not because of any actual technical issues but rather because we're more popular than their products, so they're using the same (illegal and anti-competitive) tactics they used against Netscape Navigator to eliminate competition but also labeling the project malicious in an attempt to mislead the competition regulators.

Yet another example of a trillion dollar tech company stifling competition and innovation with anti-competitive tactics.

Both Microsoft and Apple require developers to sign software in order for their apps to run on Windows or macOS. Developers must pay to buy and renew their certificates regularly and must remain in good standing with either company if they want their apps to run on either OS. At any time, and for any reason, Microsoft or Apple can revoke your certificates and prevent Windows or macOS from running your apps at all.

The control over what apps can run on Windows or macOS is all about securing profits for either company, first and foremost. Actual security is just an afterthought.

Both companies take it one step further and are locking developers out of kernel space. Apple stills signs a few third-party .kexts, like macFUSE, but everyone else is out of luck. Microsoft needs to sign kernel-mode drivers or situations like the one in the OP will occur.

This is certainly different than, but reminiscent of, the situation with AppGet and Microsoft's clone, Winget[1].

[1] https://keivan.io/the-day-appget-died/