Chrome won't open in sandboxie

[BoredNow]

FYI...Chrome won't open in sandboxie

This has happened a couple times in the past, and I usually just install the latest Beta of Sandboxie and it fixes the problem...but Beta 5.13.5 doesn't fix this problem.

popup window says.....

SBIE2318 DLL Initialization failed for advapi32.dll
SBIE2303 Could not hook CreateProcessWithTokenW (1)
SBIE2203 Could not communicate with Sandboxie Service

Also - I get a popup window that says the same thing when I open Firefox, except that it doesn't say "SBIE2203 Could not communicate with Sandboxie Service" --- and then Firefox opens as usual (??)

FYI - I just tried to open Vivaldi and it won't open either.

[Craig@Invincea]

What 3rd party security and or antivirus programs are you running?

Sounds like you're running one that does not work with SBIE.
Anything on this list?
http://www.sandboxie.com/index.php?KnownConflicts

When you first install SBIE, you're notified what may be an issue. Otherwise you can run program compatibility again from Sandboxie control.

[BoredNow]

I run Comodo Cloud AV and I have Sandboxie/Start.exe listed in my "exclusions" - it's never been a problem - like I said, usually the latest beta of Sandboxie fixes the problem.

When I installed the beta I turned off the AV and Comodos sandbox

I noticed that Chrome updated itself on the 18th and that's when it started misbehaving.

I would use RollBack RX to roll back my computer but I know Chrome will just update itself without my permission.
I really wish Google would give us a choice as to when to update.

[Craig@Invincea]

latest beta of Sandboxie fixes the problem

What you are describing is a classic issue with an offending security program.

Our betas have nothing to do with Comodo. We don't adjust SBIE for the benefit of a 3rd party security product.
Nothing in the beta's address that. beta.sandboxie.com for change logs)

Usually, you have to work around it, or better yet, remove the offending product. (beta.sandboxie.com for change logs)

Comodo is a known conflict. While some of the exclusions may work, there is no guarantee. Usually, we'd recommend you remove it. We won't troubleshoot issues with those programs, extensions, etc installed or disabled. They should be removed to have an adequate look. But, without that product, we know that Chrome, FF, Vivaldi, IE, etc works. We do not test extensions, add ons normally.

You can try the tips for Comodo here http://forums.sandboxie.com/phpBB3/view ... 11&t=21539

The newest Chrome works just fine with SBIE. We test up to Canary.

-Remove any addon's, extensions in Chrome, FF for Comodo.
-Run FF in safe mode with all add ons/extensions off.
-Delete the contents of your SB.
-Create a new SB.

Chrome should be updated outside of the sandbox, Then the contents of your sandboxes deleted, and then the updated version of Chrome run in the now clean sandbox.

Google forces updates for security reasons.

Invincea/Sandboxie recommends Windows Defender if you choose to use an Antivirus product.

[BoredNow]

Yeah, I know you don't address 3rd party AVs and that's understandable.

I have had no problem with the Sandboxie/Comodo running along side each other for years - but - I'm 99% certain I could survive with just Sandboxie alone.
I've been using Sandboxie since 2009.

I'm going to "roll back" my PC to the 16th of August (before Chromes last update) to see if it will open in Sandboxie while Comodo is running.

Am I wrong to think that if nothing has changed on my PC except Chrome - that Chrome is the problem?
You can just answer yes or no, you don't have to waste your time explaining why, I'll take your word for it.

Thanks

[BoredNow]

Ok, I uninstalled Comodo Cloud AV and Chrome started normally.

It must have something to do with the latest version of Chrome + Comodo because everything was working before the update.

As I said earlier, in the past, when Chrome wouldn't open, I would just update to the latest beta and it fixed it.

Thanks