Author Topic: Why r u keeping plsql prevented???  (Read 2615 times)

0 Members and 1 Guest are viewing this topic.

dloves

  • Guest
Why r u keeping plsql prevented???
« 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

dloves

  • Guest
Re: Why r u keeping plsql prevented???
« Reply #1 on: February 28, 2012, 03:04:52 AM »
if I disable avast, everything seems to be fine  >:(

dloves

  • Guest
Re: Why r u keeping plsql prevented???
« Reply #2 on: February 28, 2012, 03:21:18 AM »
Anybody here?

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88895
  • No support PMs thanks
Re: Why r u keeping plsql prevented???
« Reply #3 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.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

dloves

  • Guest
Re: Why r u keeping plsql prevented???
« Reply #4 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.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88895
  • No support PMs thanks
Re: Why r u keeping plsql prevented???
« Reply #5 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.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline AntiVirusASeT

  • Poster
  • *
  • Posts: 462
Re: Why r u keeping plsql prevented???
« Reply #6 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)

dloves

  • Guest
Re: Why r u keeping plsql prevented???
« Reply #7 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...

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88895
  • No support PMs thanks
Re: Why r u keeping plsql prevented???
« Reply #8 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..
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security