Comodo Internet Security 6 final release
- Thread starter Shadowave
- Start date
- Status
raxa707 said:
You can't ; Online Armor is a firewall with HIPS, CIS has a firewall with HIPS; so they will conflict. choose one of them not both.
- Aug 5, 2012
- 473
Not a huge fan of the UI, but it seems to be alright to navigate once some shortcuts are moved around.
For me the first full scan took about 47 minutes, the second full scan took about 3 minutes and the third and final scan I ran was about 10 seconds faster than the previous one. They sure were not kidding when they said "Second scan speed improvements are dramatic". Has anyone else experienced such radical scan speed improvements like that?
For me the first full scan took about 47 minutes, the second full scan took about 3 minutes and the third and final scan I ran was about 10 seconds faster than the previous one. They sure were not kidding when they said "Second scan speed improvements are dramatic". Has anyone else experienced such radical scan speed improvements like that?
Rompin Raider
New Member
- Jan 7, 2012
- 5
- Aug 10, 2012
- 474
How to get the "full virtualization" on recently released COMODO Internet Security 6 (v. 2013)
Press Windows + R, type "regedit" and press Enter.
Navigate to the registry key HKEY_LOCAL_MACHINE \ SYSTEM \ Software \ Comodo \ Firewall Pro
Create Dword key with name EnableDefaultVirtualization
Set the DWORD value = 1
Note: The next version of Comodo will integrate the GUI and no need to complicate us with editing registry keys.
Source : http://www.faravirusi.com
Press Windows + R, type "regedit" and press Enter.
Navigate to the registry key HKEY_LOCAL_MACHINE \ SYSTEM \ Software \ Comodo \ Firewall Pro
Create Dword key with name EnableDefaultVirtualization
Set the DWORD value = 1
Note: The next version of Comodo will integrate the GUI and no need to complicate us with editing registry keys.
Source : http://www.faravirusi.com
terene said:
This is not true. The developers feel that full virtualization of the auto-sandbox will cause more problems than it will solve.
They added this "feature" at users request, but they definitely only want the users that know what they're doing to utilize this feature. Anyone that is comfortable with editing their registry is likely to be able to understand the issues that may stem from enabling full virtualization, so the plans are to keep it as a registry modification.
Could you explain the problems of Full Virtualisation of the Auto-Sandbox, in brief?
HeffeD said:
Earth said:
There are too many applications that aren't going to work if they are shuffled off into a virtualized file system. With the manual sandbox, it's not that difficult to find applications that will not run inside it. If an application relies upon standard .dll's in the OS or other resources that are outside the sandbox, the application isn't going to work.
If this happened automatically, the average user isn't going to know what went wrong. All they'll know is that the application doesn't work with CIS installed. So they'll just uninstall CIS instead of trying to figure out what the problem is. There are already applications that aren't happy when the auto-sandbox just institutes the default partially limited access restrictions. Virtualizing them would just increase the breakage potential.
And what happens when a user isn't aware that something has been running in the sandbox and they delete the sandbox contents? They could lose data they weren't prepared to lose.
So when faced with the possibility of breaking countless applications and having millions of users uninstalling their product, they decided the full virtualization auto-sandbox wasn't worth the risk for mass consumption.
- Status
