Bonjour !
C'est effectivement un faux positif.. Il sera corrigé sous peu !
@fr33tux
Thanks!!! ... for any reason the database didn't update itsself the last days after activating the "Scan" button ... but now it worked and the tracing key disappeared
For you folks probably a simple question: how do I get the latest database update?
Bonjour ,
Lors d'une désinfection, j'ai fait passé AdwCleaner dont voici le rapport
http://www.cjoint.com/c/FFhiJVUVSBo
J'ai fait procédé à un test par Virus Total du profile de Firefox via Zoek qii m'a montré par contre qu'il était clean
C:\Users\Faouzia\AppData\Roaming\Mozilla\Firefox\Profiles\xn6lqjv2.default-1443437980926\prefs.js https://www.virustotal.com/file/0186CB3EE6CBDEE68F4E51C...Greetings,
I have got 5.119 which is the latest update and it still detects that registry key ...
ToineMPSI, 2016-06-07 11:15:27 (UTC)
it's not related to AdwCleaner's version, you need to get the latest database updates.
Regards.
I am bad at this kind of stuff, so apologies if I am missing something obvious.
Today in a scan a "tracing key" is detected after a scan with adwcleaner, deleted it and right after restart I scanned again. Same key was detected again. Malwarebytes scan didn't detect anything. After 2 more deletions with adwcleaner I thought I would ask here for help since it still keeps popping up in adwcleane...
Bonjour !
C'est tout bon de mon côté, excepté ce dossier :
C:\Users\client\AppData\Local\CrashRptJe vous invite à le décocher dans la liste des résultats, ce faux-positif est déjà corrigé pour la prochaine version.
Cordialement,
AdwCleaner v5.119 - Rapport créé le 03/06/2016 à 23:27:25
# Mis à jour le 30/05/2016 par Xplode
# Base de données : 2016-06-03.1 [Serveur]
# Système d'exploitation : Windows 10 Home (X64)
# Nom d'utilisateur : client - MARIETTE
# Exécuté depuis : C:\Users\client\Desktop\adwcleaner_5.119.exe
# Option : Scanner
# Support : http://toolslib.net/forum
***** [ Services ] *****
***** [ Dossiers ] ...Hello,
We'll release a test version in the coming days for the users that face this issue, we are making a good progress to fix it.
Thank you for your help,
It seems that when run on a domain joined computer, I get this error on 5.119. It worked ago on many prior versions and on tens of cleaned systems. This fix seems to work well: