Sandboxie can't open Google Chrome after upgrading Bitdefender 2017 to 2018 [SOLVED]

[Kematica]

After upgrading to Bitdefender 2018 I am having problems launching Google Chrome inside Sandboxie, the icon on the tray shows the red dots in it indicating Sandboxie is working but the browser is not showing.

No pop up messages show up at any time to show error codes, etc.

Opening task manager shows an instance of Chrome running but no resources being used.

I visited the known conflicts FAQ https://www.sandboxie.com/index.php?Kno ... itdefender to check what else I could be missing however the options in the new user interface of Bitdefender 2018 don't match those choices in there.

After looking around in Bitdefender under Protection | View Features | Advanced Threat Defense | Gear Icon (to access other settings) you can white-list applications in there.

I added the 11 .exe files in the Sandboxie folder including the one in Sandboxie\32 but the problem remains.

The next step was to disable the Advanced Threat Defense feature in Bitdefender and that allows you to open Google Chrome and launch it inside the sandbox per usual.

After doing that I got curious and re-enabled Advanced Threat Defense but this time launched Firefox and it opens inside Sandboxie without a problem.

Any help with this problem will be greatly appreciated, thank you in advance.

-Ken

Windows 10 - Version 1703 OS Build 15063.483
Sandboxie Version 5.20 (64-bit)
Google Chrome Version 59.0.3071.115 (Official Build) (64-bit)
Firefox Version 53.0.3 (32-bit)
Bitdefender Total Security 2018 - Build 22.0.8.114 | Engine Version 7.72279

[Barb@Invincea]

Hello Kematica,

The next step was to disable the Advanced Threat Defense feature in Bitdefender and that allows you to open Google Chrome and launch it inside the sandbox per usual.

So the steps provided in Known Conflicts section worked? If that's the case, then that's how you need to go about it.

As another option, you can try this (The users using that workaround reported a specific error message, however)
viewtopic.php?f=11&t=21539&start=165#p128854

Regards,
Barb.-

[Kematica]

Hello Barb,

The steps in the known conflicts section work only if you want to sacrifice the functionality of Advanced Threat Defense which includes their ransomware protection and threat defense.

In other words previous versions of Bitdefender had more control within their modules to turn on or off specific things but this one doesn't, so you must decide between allowing Sandboxie to work but have no ransomware protection or enable the feature but Sandboxie and Chrome won't work correctly.

With that said in the Advanced Threat Defense module I also whitelisted Chrome and that makes the browser launch inside Sandboxie, I am making mention of this so if someone else has the same problem in the future they understand how to fix it.

Per your suggestion I read and also implemented the additional setting in the configuration file (listed below) and that works too. **Note** to make sure it worked I removed the whitelist rule of Chrome inside Advanced Threat Defense.

"Open Sandboxie Control --> Configure --> Edit configuration Paste the following at the end of [GlobalSettings] WriteFilePath=C:\Program Files\Bitdefender Antivirus Free\*"

The only difference for me since I am using the paid version of Bitdefender was to modify the path like this "C:\Program Files\Bitdefender\*"

**Suggestion** Perhaps adding the instructions for the "[GlobalSettings] WriteFilePath=C:\Program Files\Bitdefender Antivirus Free\*" in the known conflicts for Bitdefender would be good and could potentially eliminate future support requests.

As far as I know the problem is fixed on my end but I don't know if you guys want to find out why Sandboxie and Firefox work without making any of the above modifications but you need to make changes if you decide to use Sandboxie and Chrome instead.

Thank you very much for your response and guidance, have a fantastic day!!

-Ken

[Barb@Invincea]

Hello Kematica,

The steps in the known conflicts section work only if you want to sacrifice the functionality of Advanced Threat Defense which includes their ransomware protection and threat defense.

There are several security programs that do not play well with Sandboxie. Typically, the options involve disabling a feature, adding Sandboxie to the white-listed files, or even removing the antivirus completely (you can find more info in the Known Conflicts section).
We keep a track of user provided workarounds, as well as tech support ones in the Antivirus thread I provided above.

Antivirus Workarounds may end up becoming part of the Sandboxie templates. But, this may take a while as they are not high priority and the devs need to look into them to see if there's any other way around it before adding them to Sandboxie.

Regards,
Barb.-

[nicknomo]

If anyone sees this, this is required in the global configuration:

ClosedFilePath=*BitDefender*actuf*.dll


Also, its the advanced threat defense that is causing an issue. This can be turned off. I've also made exceptions in the settings of Advanced Threat Defense for all of the executables in C:\program files\Sandboxie\ .