If it is such a usability issue, then why does Microsoft block interpreters itself?
How often are cscript, wscript, or powershell needed during install or uninstall routines? Less than 1%? Less than 0.1%?
There is no whack-a-mole needed.
The list of core Windows processes abused by threat actors on unmanaged (home) desktop systems has not changed in a long time. The "new" OneNote "malware" would have been stopped before it got started by the Microsoft default blocklist.
The mechanism of auto-sandboxing is easier, but then the Comodo sandbox gives no feeback whatsoever to the user about what is running inside the virtual environment. There is the potential (likely a small one given the type of user who will actually use Comodo) for a user to whitelist a file because it "appears" to do nothing malicious inside the sandbox.
But I do agree with you, with CF configured with your recommended settings it is so easy for those that know Comodo. As far as "ease-of-use." Meh. Just look at the hundreds of users that come here to MT and have to ask questions about Comodo. Your configuration videos are easy enough for a user to follow, and yet still, it is not so easy for some users.
All that said, it is up to the user to decide which solution works best for them personally.
