Possible solution on win xp sp3. Rename Adwcleaner_5.021.exe to Adwcleaner.exe. This may also work on versions 18 and up. It may have to do with Avira safe search interfering with it. Once I removed Avira safe search from registry (IE browser entries) using adwcleaner.exe it would then run adwcleaner_5.021.exe.
Hope this works for you. May be worth trying on other OS versions.
Bonjour
Non, absolument pas... relis STP
rien modifié sur celui qui plantait en 5.018 et 5.019 ... alors pourquoi 5.20 passe ???
rien modifié sur celui qui passait en 5.018 et 5.019 ... alors pourquoi 5.20 passe pas ???
tous mes PC passent en 5.017 (et avec la dernière base)... MABM + AVG + ZHPdiag et ZHPcleaner Ok
non y'a qq chose qui coince dans votre soft... désolé mais ce que j'écris plus haut confirme que ce n'est pas du aux PC.
Merci.
Once again and this time in english my suggestion for the UI/language
While in English is a distinctly difference between "Cleaning" and "Uninstall", in the german translation the words "Löschen" (Delete) and "Deinstallieren" (Uninstall) are not so different and many people misunderstand this. After a scan they often choose "Deinstallieren" (and the similar Icon with the red bug reinforces the error) because they think, that this uninstalls the malware but in fact it deinstalls AdwCleaner.
Please change that.
Bonjour.
Pareil pour la version 19 sous XP, Elle a fonctionné au début mais désormais refuse de se charger (alors qu'une version précédente ne présente pas de problème, je soupçonne une mise à jour de signatures de avira ?
(Fichier LOG dans EventDB ? Tout au moins avec la version 18 qui m'avait fait le même coup jusqu'à ce que ça se rétablisse tout seul quelques heures plus tard.)
Et merci quand même pour l'efficacité.
Version 5.017 konnte installiert werden und die Software hat auch ihren Job gemacht & 2 Einträge wurden in der regedit gefunden und behoben.
Version 5.018 & Version 5.019 konnte ich nicht installieren, es kam die tüpische Windowsfehlermeldung.
PC Windows XP Pro 32 Bite, ZoneAlarm
I DISAGREE ! Just cleaned my PC with the latest update and i had no BSOD nor errors whatsoever !!
You're doing it wrong ▼
Version 5.019 Funxt bei Win XP Pro 32 Bite nicht
Bonsoir
Depuis la version 5.018, j'ai ce message d'erreur sur 1 de mes 3 PC :
"Adwcleaner a rencontré un problème
et doit fermer"
et le soft ne se lance pas... même punition avec la 5.019...
Par contre si je relance la 5.017 (en refusant la MAJ), tout se passe normalement et elle ne trouve aucune clé ou fichier suspect. J'ai complété le test par ZHPdiag et ZHPcleaner qui sont tous deux négatifs aussi.
Merci.
TESTIMONIAL For AdwCleaner -- World's Best Free Cleaner for Treacherous Malware
I discovered AdwCleaner at the Malwarebytes forums. It is one of the primary tools used by the AV experts there.
I used AdwCleaner for several years whenever I believe my active PAID AV protection failed to detect a threat.
AdwCleaner saved my PC SEVERAL times from Virus Hell!
THANK YOU EVER SO MUCH FOR AdwCleaner, Mr. Xplode.
(WARNING for Novice Users: Unless you are very knowledgeable about the Windows Registry, think twice about using AdwCleaner to delete potentially infected registry keys. If AdwCleaner says you have infected registry keys, go to the Malwarebytes forum and ask for a second opinion from an expert before messing with your Windows Registry.)
URGENT -- Attn: AdWare Developer -- MAJOR Bug Report for v5.019
I just downloaded and attempted to run the current version...but AdWare fails to run and crashes before opening.
Here is what happens:
1. Open File window opens after clicking on the .exe file.
2. Clicking Run on Open File window results in a window opening with an error message.
3. The error message simply states AdWare Cleaner encountered an unknown problem, etc. The error window offers a Debug button. I simply closed it out.
4. I ran version 4.2xx. It opened and worked fine.
NEXT ISSUE: v4.2xx identified about 11 registry keys as a threat. After manually locating each registry key, all registry key were associated with variations of "Download.SwInstaller" and "NCTAudioFile2.DLL". Extensive Google searching didn't uncover any meaningful info about the nature of those two 'things'. So, I didn't let Adware delete them. DO YOU KNOW WHY ADWARE PEGGED THOSE REGISTRY KEYS AS THREATS?
*** Sir Xplode, I wish to profusely thank you for sharing Adware with the world. Your Adware saved my PC more than once over the years. Bless you!
