Comodo's Auto Containment is Blocking Roboform in Chrome only.

For some reason, Roboform is being blocked in Chrome by Comodo Firewall Auto Containment feature. I’ve looked into settings and have tried to make sure that all instances of Roboform are not being blocked, but the problem persists. The fine folks at Roboform dialed in and couldn’t figure out the issue either.
The only way to get Roboform to work in Chrome is to permanently disable Auto Containment.
By the way, Roboform works just fine in FireFox with Auto Containment enabled.
Windows 10 Pro.
Any ideas?

Can you export your containment log and upload the .html file here?

I tried to attach the containment log to this reply, but I got this error:

containment log.html.
You cannot upload that type of file. The only allowed extensions are txt,doc,jpg,gif,mpg,png,zip,mp3,rar,jpeg,xls,sdb,md5,7z,log,cbu,pdf,mp4.

Is there another way to get the log to you?

Edit the file extension to .txt or just put it in zipped folder.

Here it is in a Zip file.
Hope it gives you a clue why Comodo is blocking Roboform.
Thanks for the help.

Can you make sure that all of your containment rules have the ‘log when this action is performed’ checked?

Then again try to run Roboform and see if it gets blocked. If so please take a screenshot of the Auto-Containment logs and post here.

Hi Big Dawg,

Thank you for Reporting.We will check this issue and notify you.


Roboform is not being blocked, the Windows command prompt is being blocked because of the default auto-containment rule to block cmd.exe when being executed by the web browsers file group. Chrome extensions shouldn’t be trying to run windows commands, but this is the issue with the chrome extension architecture, whereas firefox doesn’t have this issue with extensions needing to access the system or communicate with the local system.

So is there a solution for this behavior in Chrome?
Can I just say ignore cmd.exe in Comodo or is that dangerous to do?

You can change the rule from block to ignore if you want, it is only dangerous if a web browser is exploited to run commands using the command prompt.