Re: False Positive v7?

dans AdwCleaner par JoshRoss

Interesting development. Thanks for the logs, as expected they are clean. Successful removal could indicate that Adwcleaner stopped the threat further or was a false positive. Honestly, everything related to Yahoo is a massive security hole for me, and I would avoid it as much as possible. 

Upon further investigation, this looks like malware's registry file that wasn't removed correctly, but t...

Re: False Positive v7?

Sure, here they are:

# AdwCleaner 7.0.2.0 - Logfile created on Sat Aug 26 17:05:27 2017 # Updated on 2017/29/08 by Malwarebytes  # Database: 08-25-2017.1 # Running on Windows 8.1 (X64) # Mode: scan # Support: https://www.malwarebytes.com/support

***** [ Services ] *****

No malicious services found.

***** [ Folders ] *****

No malicious folders found.

***** [ Files ] *****

No malicious fil...

Re: My First Post: Are These Internet Explorer\ActiveX Compatibility Entries False Positives

dans AdwCleaner par JoshRoss

A quick bump up the post to get admins/mods here to confirm and double check my concerns.  Also, the other thread hasn't been confirmed by admins/mods as well. We will see how it turns out, could be just another bug with Adwcleaner.

Re: False Positive v7?

dans AdwCleaner par JoshRoss

Can you post the full logs? Also, try downloading the newest beta version of Adwcleaner and see if that helps you out? In addition to that, try doing the scans in Windows "Safe mode with networking" as well as add Hitman Pro to your program list. That way you can be certain that the threats are removed. In theory, it should work.

Re: PUP.Legacy.Optional

Hi,

Don't panic, this is a classic "aggressive (scam) advertising" and a (real) false 'Zeus' alert! None zeus virus is present on your computer!

https://www.bleepingcomputer.com/virus-removal/remove-zeus-virus-detected-popups

https://blog.malwarebytes.com/threat-analysis/2017/06/the-numeric-tech-support-scam-campaign/

I've not seen yet MalwareBytes, ADWCleaner, HitmanPro, uBlock, adblock, a...

Re: version 5.016 ..... FP with Spyware blaster active x registry entries

dans AdwCleaner par Sigge

I'm running adwcleaner version 7.0.1.0 and this is an issue even now and has been in the last few versions of adwcleaner.

It started with the version where you changed the programs interface.

Most of the time Adwcleaner finds five internet explorer active x registry entries but sometimes it can be over a hundred and the next time it's back to five again even though I have not done anything th...

Re: Cannot get AdwCleaner to work on Windows 10 64bit

dans AdwCleaner par p060477

if you read carefully all my 3d linked you should know that the last NON buggy is the vers 6

upt to the new vers 7, also the last stable 7.0.1 one is BUGGY

for the quarantine behaviour

and for the events list behaviour

 

2 BIG BUGS not only showed and witness by my self but also from other users

 

cheers

Re: False Positives V7

dans AdwCleaner par notnats

Since V7 I've been getting false positives on all my machines - often ones reported by others.  I suspect they are down to using SypwareBlaster.  This is an old but quite safe program which puts kill bits in the registry to prevent undesireable stuff running.  I think it would be worth installing SpywareBlaster then "enabling all protection", then see what ADWCleaner makes of it.  Thanks.


SWB...

False Positive v7?

Today I stumbled upon this detection whilst using Adwcleaner 7.0.1.0:

***** [ Registry ] *****

PUP.Optional.YahooChrome, [Key] - HKLM\SOFTWARE\Yahoo\SS

Afterwards I scanned with other virusscanners (Malwarebytes, MBAR, and Roguekiller) and none of them detected aforementioned registery key. Thus, it seems like a false positive generated by adwcleaner. 

Can someone confirm this?

Kind regard...

Re: Cannot get AdwCleaner to work on Windows 10 64bit

dans AdwCleaner par notnats

now the tool is -buggy- with win 10 64bit

see:

https://toolslib.net/forum/viewthread/12568-vers-70/?p=3#!messageId-13159

 

still UNSOLVED


p060477, 2017-08-26 19:09:12 (UTC)

You are aware, I assume, that the buggy version is the BETA version, 7.0,2.0. The current  version 7.0.1.0 works perfectly well with Windows 10 64bit. Unless you are a BETA testor you should not be using TEST versions.