The implementation and roll-out of the SANDBOX feature in CIS is probably fantastic for machines with a fresh install – the kind of machines that coders and computer scientists use that have only two or three apps on top of the operating system, and virtually no accumulated data files. However, for an existing system which has an abundance of previously installed applications, and a superabundance of accumulated user files, it sucks!
The Sandbox has grabbed my machine by the you-know-what, and is squeezing it hard. It is interfering with things that constitute routine tasks for me, such as printing the screen to a .pdf-creating printer driver, and then really printing to a real printer Users should be introduced to the Sandbox with some explanation that printer drivers may become dysfunctional, and some examples of the kinds of problems that commonly exhibit themselves when sandboxed apps cannot communicate with non-sandboxed applications.
Tasks which have never given me any problems are suddenly failing to perform, and without any error message or anything to alert me to the failure. Programs which automatically are put into the Sandbox and are supposedly being checked by Comodo for safeness, just sit there in the line to be checked. And this is happening with programs on my machine which have been on the market for years. Clearly, Comodo’s whitlelist was developed by a kindergartner, and the company is using its customers as guinea pigs to build its whitelist for it. If they are actually checking applications to determine their “safeness,” I see no evidence of it.
There should be a knowledge base with KNOWN ISSUES on display. When CIS and Sandbox are installed onto a machine with applications in place, users should be shown a list of applications on their machine with explanatory details such as KNOWN SAFE, UNKNOWN, KNOWN HAZARD, etc., so that users can get some sense of how harshly their computer experience is going to be handled by COMODO’S SANDBOX, and some advisories about how to best manage the transition to having the Sandbox squeeze less harshly.
I could keep on with suggestions, but if this rollout had not been handled by persons who are clearly indifferent to existing customers with mature, fully built-out systems, it would be unnecessary for me to be forced to waste my time holding their hands.
Their management is clearly not up to the task of handling a rollout as complicated as what the Sandbox is.
The same is also true of the Comodo AntiVirus. Simple things – like self-extracting zip files which I have created and stored – are all, each and every one, being identified as potential problems when a scan is done by the Anti-virus checker. Absurd to identify a self-extracting zip file as a virus, without letting the user specify that such a class of files should be skipped and presumed to be desirable, at least when they are located in certain folders. Major things, like invisible system restore points, are being identified as infected with no clue as the crucial significance of those files being cleaned" or “quarantined.”
A user who is doing an upgrade of Comodo needs to be warned that CIS is going to take control of their machine and possible refuse to let it perform productively in ways that have become routine for the user, and safely so.