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...
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
Hello,
Windows10 Chrome -- month ago got a malware popup when on tunein radio. Along with the following popup, a voice came on and said "your pc is infected with Malware, do not ignore this, etc:
** Zeus Virus Detected - Your Computer Has Been Blocked **
Error: Trojan Backdoor Hijack #365838d7f8a4fa5
---------------------------------------------------------------------
After running adwcl...
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...
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...
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.
now the tool is -buggy- with win 10 64bit
see:
https://toolslib.net/forum/viewthread/12568-vers-70/?p=3#!messageId-13159
still UNSOLVED
just to let you know that yr latest 7beta vers of 16hours ago has the
same -BUGS-
Well, thanks, but I confess to not getting on with Tweaking.com. using it ususally ends up with things more worse than they were before. But thanks for suggestion.
My problem was solved a year ago and closed I thought.
You really need to start your own thread so that it will be seen.
