I'm afraid I got the same problem.
AdwCleaner version 7.0.3.1 stops working directly after the update phase.
The solution you offer is irrelevant since the program doesn't make it to the clean phase.
Lapo90, 2017-10-01 11:58:37 (UTC)
Same problem. Program doesn't make it to the clean phase.
Hello,
Thanks for the details. We'll look into it.
I'm afraid I got the same problem.
AdwCleaner version 7.0.3.1 stops working directly after the update phase.
The solution you offer is irrelevant since the program doesn't make it to the clean phase.
Greetings,
Sorry for the late answer.
Try to uncheck every registry element detected before pushing the Clean button. Then, it should work as expected.
This issue is known and will be resolved with the release of the 7.1 version.
Regards.
I tried using AdwCleaner version 7.0.3.1, but every time it stopped working.
I already tried "Mode > Debug", "Database > Local", Uninstalled AdwCleaner and running it as admin.
I'm using Windows 10 Pro with Bitdefender Antivirus Plus 2018 (no warnings from Bitdefender).
I disagree for no support for xp because i have 2 computer (one on xp and 1 with seven) but on xp pos ready i have update until 2019 ( i write this answer on xp) so why stopping support for adwcleaner now ?
Greetings,
Can you please try with the latest version of AdwCleaner: https://toolslib.net/downloads/finish/1-adwcleaner/
Thanks.
Whenever I try to scan for Adware after about 75% of the bar is finished it randomly stops and pops up a message AdwCleaner has stopped working
Please help
Regards.
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...
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...
