No Option To Disable Behavioral Blocker On Windows XP x64 [M961]

Comodo Internet Security - CIS Resolved/Outdated Issues - CIS
#1

A. THE BUG/ISSUE (Varies from issue to issue)
[ol]- Summary - Give a clear summary in the topic subject, NOT here.

  • Can U reproduce the problem & if so how reliably?:
    Yes, every time.
  • If U can, exact steps to reproduce. If not, exactly what U did & what happened:
    1:Install CIS on Windows 64 bit
    2:Start installing a software which will be sandboxed
    3:Note that the software will be sandboxed. However, if you go to the settings anywhere in CIS there is no option to even disable the Behavioral Blocker.
  • If not obvious, what U expected to happen:
    I expected that there would be some way to at least disable the Behavioral Blocker, even if it’s not possible to have granular control on Windows XP x64.
  • If a software compatibility problem have U tried the conflict FAQ?:
    NA
  • Any software except CIS/OS involved? If so - name, & exact version:
    NA
  • Any other information, eg your guess at the cause, how U tried to fix it etc:
    I navigated the COMODO Forums and found that another user has posted a registry tweak that completely disabled auto-sandbox. However, an average user would not be able to do this. Therefore, this is a bug.
    [/ol]

B. YOUR SETUP
[ol]- Exact CIS version & configuration:
CIS 7.0.315459.4132

  • Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
    Default
  • Have U made any other changes to the default config? (egs here.):
    Yes, the registry tweak suggested here:
    https://forums.comodo.com/install-setup-configuration-help-cis-b137.0/-t98972.0.html
  • Have U updated (without uninstall) from CIS 5 or CIS6?:
    No, this was a fresh install of CIS.
    [li]if so, have U tried a a clean reinstall - if not please do?:
    NA
    [/li]- Have U imported a config from a previous version of CIS:
    No - fresh install.
    [li]if so, have U tried a standard config - if not please do:
    NA
    [/li]- OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
    Windows XP 64 bit. All Windows Updates installed.
  • Other security/s’box software a) currently installed b) installed since OS, including initial trial security software included with system:
    a=None b=None
    [/ol]

[attachment deleted by admin]

#2

[b]What I would love:
Even the most simple of features, like in the CIS HIPS settings have a Sandbox section with one tick box to enable/disable it.

CIS Task Manager to work.[/b]

I would like much more than this, but this seems like the bare minimum.

I absolutely positively guarantee TONS of windows xp 64 users get extremely frustrated with this upon installing and just assume COMODO is not on top of things.
The surely uninstall and tell everyone they know not to use COMODO. This makes me sad as COMODO is top notch.

I know from experience that COMODO is a good company and is on top of things, but for some reason this issue has been GREATLY undervalued in previous posts.

Many users like myself refuse to upgrade Windows until the new OS is stable and secure. I don’t plan on leaving XP for a long time to come and I am sure I am not the only one. XP 64 is the only way to take advantage of the extra RAM options. XP 32 is weak in that regard. Look how they are still patching XP… there are surely TONS of things in newer versions of Windows that will take years of patching, if ever be patched.

Thx for taking the time to read! Hopefully COMODO doesn’t let me down :-TU

#3

Are you saying that you do not even get a popup which says that the app was automatically sandboxed, and gives you the option to not sandbox it again?

#4

Thanks for the fast reply. I usually get the popup, but sometimes with full screen installations I don’t see/notice the popup.
Additionally, the “do not sandbox again” option seems to be hit or mis.
Additionally, some installers freeze upon being sandboxed and require me to force shutdown and reboot.

#5

Also, there is a timer on the popup and only so much time to notice/answer it.
And, I would like it to ask me before sandboxing, or for there to be an official method of disabling sandbox features other than me editing my registry.

#6

Please change the main screen of CIS to Advanced View. Then take a screenshot and upload it to your next reply.

Also, have you tried reinstalling by following the advice I give in this topic? If not, please do. It seems unusual that you are experiencing so many issues, and many may be able to be fixed if CIS is reinstalled by following the methods I advise.

Thanks.

#7

I installed CIS freshly on a fresh install of Windows.
This is far from the first time having this issue with CIS on Windows XP 64 Bit.
It is the same issues everyone else has with CIS on Windows XP 64 Bit it seems.
I attached the image, but it is no different than the one the other user uploaded in the forum post I linked up top.

CIS simply randomly sandboxes things without first asking the user or giving the user an option to disable the sandbox (until it is too late).
I believe then COMODO implemented this on XP 64 Bit that it was not tested thoroughly enough.

[attachment deleted by admin]

#8

And again, thanks for the fast replys!
CIS Task Manager:

[attachment deleted by admin]

#9

Say for example someone were trying to install Adobe Creative Suite (big, long install) and everything was going along just fine, until 99% in the install COMODO sandboxes something (without asking the user) and the entire Adobe Creative Suite install must then be reverted. Then the user must make sure all related processes are closed, or reboot, then re-install again (HOPING nothing else will be sandboxed).

HIPS being disabled, learning, clean pc mode, nothing effects the sandbox.

There needs to be some sort of setting that allows the user to regulate the sandbox features, even if it is a simple on/off switch.

I promise you that if you were a XP 64 Bit user and has CIS while you were trying to install software that you would get my point!

#10

I have attached a pic of what I’m asking for a screenshot of.

Please attach a pic of your main screen as well so I can see what it looks like. However, first make sure it’s in Advanced View, like mine is.

Thanks.

[attachment deleted by admin]

#11

Just to show KillSwitch works fine (in comparison to CIS Task Manager):

[attachment deleted by admin]

#12

Here you go sir:

[attachment deleted by admin]

#13

Also, the task manager included in CIS shows the tasks which CIS is doing. It is not meant to show you all of the processes running on the computer. It’s just named in a bit of a confusing way. However, if you start a CIS task, such as a scan, you should see that the scan then shows up in the task manager.

Thanks.

#14

Ahh, I see! You are correct and it works as intended. I suggest it be renamed :slight_smile:
I remember older versions of CIS having something similar to KillSwitch built in, that is maybe what confused me.

[attachment deleted by admin]

#15

As for the BB also missing from the front screen, I had forgotten it was removed from there as well. Sadly, the devs also seemed to indicate that they would not be able to add it there as well. Therefore, I cannot submit a new bug report for the same issue, which they have already responded cannot be fixed.

I think the only way to proceed would be to alter this bug report to be aimed at having some way to turn the BB off and on, even if no granular control is available. Would trying the bug report in that way work for you?

Thanks.

#16

Just noticed that opening/closing KillSwitch caused ‘blocked intrusions’ in CIS. Should I post that in a new thread?:

[attachment deleted by admin]

#17

What does BB stand for?

In my initial post I did ask for a way to enable/disable sandbox options, so my post should still apply?

I did read the other forum thread that I linked above and realize the issue here.

My issue is that there is no way to enable/disable sandbox options other than via regedit.

Edit: (Behavior Blocking) = Sandbox?

#18

Unless it is causing issues with the functioning of the computer I think it’s intended that opening and closing KillSwitch causes ‘blocked intrusions’. This is probably caused by the CIS self-defense. It will automatically prevent any program (even trusted) from interacting with its protected files and processes, which is probably what KillSwitch tries to do. Unless you are seeing issues I wouldn’t worry about it.

#19

Sorry, BB stands for Behavioral Blocker. I will modify your first post. Once I’m done I’ll ask you what you think of it.

Thanks.

#20

The main concern here is not for myself (as I now know the registry tweak required to disable auto-sandbox), but for any potential future users of CIS / those having the issue but don’t care enough to create a forum post.

The way CIS is setup now, everything goes along just fine, until you happen to install something that gets sandboxed, then it is too late.

I believe I understand why COMODO did it this way, because they did not fully implement sandbox/kiosk in 64bit version for XP, but…

If anything, it should not auto-sandbox by default, this way users have to manually enable it and should be warned of potential issues it could cause.

With the auto-sandbox disabled CIS works just fine.

It is just frustrating when at the end of a long installation something in the installation is sandboxed and the entire installation is often rendered useless.

Quite often the software installed will not auto-revert the installation and will assume it is installed. Quite often the software that was installed will not repair/uninstall at this point either.