what if instead of sandboxing, comodo could install a secure user account. The purpose of said user account the same as virtual desktop as I have noticed, comodo tries to prevent everything from windows update to installing device drivers as you plug them in.this creates a problem from the user experience end and not the security. If comodo were to have its own user account, it could run a windows account with the same security potential as the virtual desktop butinstead of doubling or tripling the processing power required by running the virtualizing process on top of the windows desktop, instead, the main user account would be the base of the comodo user account (like the current virtual desktop), but the virtual desktop would be run as the desktop of the comodo user account instead of the windows desktop and would be controlled from the main user account should the user need to log into that account to change anything. I am not sure if this is possible, but just by comodo with nothing else open right now, it already makes typing difficult because I can not see what I am typing due to the large amount of resources comodo requires, even though I easily have double what the program is supposed to require. The issue to adddress for another user account would probably be accessibility to the operating system, like virtual desktop minimizes access to, but if comodo were preventing without interfering as claimed, this would be a large boost toits user base while providing the same functions as the current security
I would appreciate feedback on the idea
alternatively, instead of the complications above, comodo could offer to sandbox applications it doesn’t recognize but ultimately put the user in charge of what applications executed or etc are sandboxed. being unable to use mouse, keyboard, webcam, etc because comodo sandboxed an important part of the operating system (or at least that’s what I can only hope happened since it was a clean install) makes security pointless when the user can not “use” their computer