« previous next »
Pages: [1]   Go Down

Author Topic: Odd behaviour that began this past week  (Read 1602 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
Odd behaviour that began this past week
« on: May 22, 2017, 03:33:19 AM »
Over the past week or more I have had a situation start where I would get a message that a file in AppData/Local ... was stopped just prior to execution.  This is happening even after a fresh reboot without running any applications.  It indicates the need to do a local scan as well as a boot scan.  In almost every situation no virus is found on the standard scan and nothing ever shows up on the boot scan.

I have some files isolated should you want to view them to see if it is a false positive.  Many of these files are given nonsensical names, have no extension, and no proxy is found running or installed that would execute these files to the best of my knowledge. 
Logged

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31079
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Odd behaviour that began this past week
« Reply #1 on: May 22, 2017, 07:11:52 AM »
A start would be providing the log files > https://forum.avast.com/index.php?topic=194892.0
Logged

REDACTED

  • Guest
Re: Odd behaviour that began this past week
« Reply #2 on: May 23, 2017, 06:06:58 AM »
here you go...115 items after running Avast continuously??!!

Logged

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31079
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: Odd behaviour that began this past week
« Reply #3 on: May 23, 2017, 06:50:51 AM »
If you look, you will see they are all PUP's.
If avast detects them depends on the setting you have for them.
By default (for legal reasons) PUP  detection is off.
Logged
Pages: [1]   Go Up
« previous next »