Avast 2015.2.2014 not working with Sandboxie

Avast Free Antivirus / Premium Security
1

I posted in the sticky for the new version, but dodn’t know if everyone checks there, so I’ll post here also.

Neither of my browsers, Opera nor Firefox, work with Sandboxie after I updated this morning to the lasted version of Avast 2015.2
.2014.

They are ok if not sandboxed.

Can anyone verify if they are also having any problems?

I get pop ups stating the the site is blocked because the certificate is invalid etc

2

Yes, I can confirm this !

I only use Sandboxie with the Tor browser, so I didn’t test it with other browsers which I use the Avast! Sandbox for.
But there is a problem with Sandboxie and Firefox. Disabling HTTPS scanning in the Webshield “solves” it for now.

Thank you for reporting.

Greetz, Red.

3

Exactly as Rednose said. We are working on this issue, but for now disable the HTTPS scaning.

Thanks

4

What would the security hit be for disabling HTTPS?

5

That the Webshield doesn’t scan HTTPS ( encrypted ) connections. All HTTP ( non encrypted ) connections will be scanned though.
As you still have the Realtime shield, and a Sandbox you run your browser in, the security risk is an absolute minimum imo.

Greetz, Red.

6

Having the same problem here…started after installing latest version of Avast!

7

Hi haggisfarmer2, welcome to the forum :slight_smile:

Yes, it is a bug that Avast is working on. All you can do for now is disable HTTPS scanning.

Greetz, Red.

8

Thank you Rednose

9

Im having the same problem

10

Funny as they say that it fixed issues with expired certificates. Well im getting infinite expired certificates using sandboxie!

11

Same problem with more details:
Outside the sandbox I can access all web pages, especially *.google.com, *.yahoo.com, *bing.com
Inside the sandbox my Browsers say: Page not found for *.google.com and www.yahoo.com
Avast message pops up = Avast web shield has blocked access because the following certificate is unvalid:
*.google.com and www.yahoo.com
Inside the sandbox *bing.com is found, no problem

Tested with both, Firefox36.0.1 and Internet Explorer 11.
Latest versions of Sandboxie-4.16(64bit) and Avast-free-2015.10.2.2214 under Windows7-64.
Remove and Clean install of both Sandboxie and Avast does not help.

No problem with older version of Avast, Avast-free-2015.10.0.2208 (and same Sandboxie-4.16(64bit), same firefox).
Has anyone tested to reinstall OLD VERSION 2015.10.0.2208?

12

only the latest version of avast has the problem. ive tested it.

13

Is there any update on when this might get fixed?

Thanks

14

Not that I know, but I will try to find out.
But it is weekend, so be patient :slight_smile:

Greetz, Red.

15

Rolled back to 2015.10.0.2208 AIS after experiencing the same issues above, used System Restore to do that. Also noted that the avast! sandbox also has issues with certificate validation as the browser window for Firefox 36.0 is very slow to open and then hangs with a black window; then FF will proceed to load without certificate blocks. Otherwise, certificate blocks will be announced with Sandboxie 4.16 and either IE 11 or Firefox and no internet access is possible. I’ve seen as many as 14 blocks on one website alone when running Sandboxie.

Updated via GUI to see what would happen, just so you know.

Running Win 7 SP1 64-bit, now 2015.10.0.2208 AIS installed. Internet is accessible with .2208 with both sandboxes but not with .2214, one does not work, and noticeable hangs with avast! Sandbox, also with version .2214, for both IE 11 and FF 36.0.1.

So the .2214 version ssl certificate validation issue appears to also affect AIS Sandbox to some degree.

Did check for operation running both browsers normally (no sandbox) and did not see any problems running .2214.

Interestingly, using System Restore also caused an issue with an avast! failed start on reboot, even though a step was taken to untick the box for the self-defense module in Troubleshooting before running the first System Restore on avast! install. Here, self-defense was unticked prior to running the GUI web update.

Workaround for that was to go to Troubleshooting, check to see if self-defense was enabled on reboot. It was. Unticked that box, and clicked “Fix All” and all was fixed without doing an avast repair. So, restoring to .2208 caused an unexpected issue.

Can’t run .2214 as things stand now, as proper ssl certificate validation is crucial to privacy and user security.

[EDIT:] Corrections made to avast! versions, changed from .2008 to .2208, and .2014 to .2214.

16

Avast team.

Please update?

17

See: https://forum.avast.com/index.php?topic=167908.msg1194060#msg1194060

18

FIXED :slight_smile:

Greetz, Red.

19

I’ve still got the same problem…am I missing something?

Cheers

20

No, I made a mistake. It is not fixed yet. Sorry :-[

Greetz, Red.