Hello,
It has been fixed with the current update. It was harmless to delete this key, so nothing to worry if you pressed the (Clean) button with this element ticked.
Best regards,
Hello,
It has been fixed with the current update. It was harmless to delete this key, so nothing to worry if you pressed the (Clean) button with this element ticked.
Best regards,
Funny enough, I have this issue as well.
I was about to post a thread just like it.
Same here, have posted to 2 other forums to see if anyone finds. My findings : Avira crashes but I suspect the last update to be the cause MBAM, ZHPdiag, rKill don't find anything Windows defender says it has found something butI have to wait until the end (loooong) of the scan to know what it is, so that'll be tomorrow morning. Really hoping it's a false positive
Hey hey hey! same here too. Puzzled me a great deal. So what is it and why is it coming up ?
Exact same issue here.
cc
Hi there,
I have exactly the same result since this evening... Glad i'm not the only one here :)
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...
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: