Hello!
I have Microsoft Windows 10 Professional 64-bit.
Every time I am running QuickDiag in either mode (Xspeed, Quick or Extended) and (even in Safe Mode), it hangs at the exact same file: C:\Windows\Installer\3ef7a91.msi
This is the error message: "Line 7859 (File "C:...
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.
Bonjour,
Cela vient d'être corrigé. La suppression de cette clé est néanmoins sans danger.
Cordialement,
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, je retrouve ce résultat à chaque fois que je scanne le système, est-ce un faux positif? Merci
***** [ Registre ] *****
Clé trouvée : HKLM\SOFTWARE\Classes\CLSID\{0002DF01-0000-0000-C000-000000000046}
Пожалуйста, для просмотра документации на русском языке, перейдите по ссылке на SafeZone.
Bonjour !
C'est tout bon de mon côté, excepté ce dossier :
C:\Users\client\AppData\Local\CrashRpt
Je 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: