Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: dloves on February 28, 2012, 03:03:27 AM

Title: Why r u keeping plsql prevented???
Post by: dloves on February 28, 2012, 03:03:27 AM
It's freaking me out!
When I start up plsql 9.0 with avast services on, plsql will start up for 2 or 3 secs, and then crashed (with red margins for plsql window)
BTW, it happens after I upgrade my avast from 6.X to 7.0.1407
Title: Re: Why r u keeping plsql prevented???
Post by: dloves on February 28, 2012, 03:04:52 AM
if I disable avast, everything seems to be fine  >:(
Title: Re: Why r u keeping plsql prevented???
Post by: dloves on February 28, 2012, 03:21:18 AM
Anybody here?
Title: Re: Why r u keeping plsql prevented???
Post by: DavidR on February 28, 2012, 03:38:36 AM
It is being caught by the autosandbox.

From the avastUI, Additional Protection, AutoSandbox, Settings, Set it to Ask, that will throw up a screen, suggesting you run sandboxed. Choose Run Normally and check the Remember my answer for this program (or words to that effect).

Or you can go into the same place and add an exclusion for the executable, if you are confident it is clean, and from a legit source, etc.

Personally I would set it to Ask so it doesn't make a decision for you.
Title: Re: Why r u keeping plsql prevented???
Post by: dloves on February 28, 2012, 03:49:19 AM
It's so kind of you, David. Followed your instruction and it works fine. Having been using avast for years, it's really a great product.
BTW, the auto-sandbox might not be as convenient as it's supposed to be:)  -- just FYI.
Title: Re: Why r u keeping plsql prevented???
Post by: DavidR on February 28, 2012, 04:07:55 AM
You're welcome.

Well it is pretty sensitivity at the moment and in the past it wasn't sensitive at all, so much so people were wondering if it was worth using. So it is a difficult balancing act between too much and not enough and probably the biggest problem is trying to make the decision for the user, as most how to respond if it were set to Ask by default.

That's me for the night, after 3am here.
Title: Re: Why r u keeping plsql prevented???
Post by: AntiVirusASeT on February 28, 2012, 04:51:31 AM
it could be plsql is not well known in the Avast! community yet thus trigger filerep-->triggering autosandbox

u can read up on the new filerep here: http://www.avast.com/pr-avast-software-detection-is-faster-when-filerep-knows-all-the-clean-files

i like the idea of the filerep and autosandbox working in sync. but there will be collateral damage like in ur case.
also unknown developers trying to create new programmes will face a lot of problems if their customers use Avast!

since this feature is still new, i am hopeful that Avast! will find a sutable solution to this problem (its small but significant)
Title: Re: Why r u keeping plsql prevented???
Post by: dloves on February 28, 2012, 05:16:38 AM
Just as what David said, when it's auto-sandboxed, it well be better to let the user knows, in some way...
Title: Re: Why r u keeping plsql prevented???
Post by: DavidR on February 28, 2012, 01:57:32 PM
Just as what David said, when it's auto-sandboxed, it well be better to let the user knows, in some way...

Yes, there should be some notification, as the red border isn't immediately that it is running in a sandbox unless your are aware of the significance of the red border..