Piriform Community Forums > New Spybot does not have an entry in CCleaner

Full Version: New Spybot does not have an entry in CCleaner

Piriform Community Forums > Piriform Software > CCleaner Discussion

Anthony A

Feb 28 2008, 07:31 PM

The new Spybot S&D does not get cleaned by CCleaner. Maybe there could be a winapp2.ini entry made for it untill/if it is added again to CCleaner

JDPower

Feb 29 2008, 02:27 AM

QUOTE (Anthony A @ Feb 28 2008, 07:31 PM)

The new Spybot S&D does not get cleaned by CCleaner. Maybe there could be a winapp2.ini entry made for it untill/if it is added again to CCleaner

The detect key for the Spybot entry is currently wrong, it should be:

HKCU\Software\Safer Networking Limited\SpybotSnD

Not:

HKCU\Software\PepiMK Software\SpybotSnD

Anthony A

Feb 29 2008, 03:02 AM

QUOTE (JDPower @ Feb 28 2008, 09:27 PM)

The detect key for the Spybot entry is currently wrong, it should be:

HKCU\Software\Safer Networking Limited\SpybotSnD

Not:

HKCU\Software\PepiMK Software\SpybotSnD

So are suggesting to just edit the winapp.ini with the entry you provided or just pointing out why Spybot doesn't get detected?

JDPower

Feb 29 2008, 03:11 AM

QUOTE (Anthony A @ Feb 29 2008, 03:02 AM)

So are suggesting to just edit the winapp.ini with the entry you provided or just pointing out why Spybot doesn't get detected?

That is entirely up to you, I was just pointing out to the MrG or anyone else why it's not working. Should be ok to edit the winapp yourself (but I've not tested it myself and accept no responsibility for any damage it may cause

)

JDPower

Mar 1 2008, 03:16 AM

Just tested it with the changed detect key and it works fine. Incidentally if you use The Gimp the winapp2 entry for that is wrong too, I reported it a while back but it's not been fixed. Should be:

CODE

[*GIMP 2.4]
LangSecRef=3021
DetectFile=%userprofile%\.gimp-2.4\gimprc
Default=True
FileKey1=%userprofile%\.gimp-2.4|documents

fredvries

Mar 1 2008, 07:06 PM

My (working) SpyBot entries:

CODE

[SpyBot Search and Destroy]
LangSecRef=3024
Detect=HKCU\Software\Safer Networking Limited\SpybotSnD
Default=True
FileKey1=%commonappdata%\Spybot - Search & Destroy\Logs|*.*
FileKey2=%ProgramFiles%\Spybot - Search & Destroy|advdebug.txt
FileKey3=%commonappdata%\Spybot - Search & Destroy|Statistics.ini
FileKey4=%windir%\All Users\Application Data\Spybot - Search & Destroy\Logs|*.*
FileKey5=%windir%\All Users\Application Data\Spybot - Search & Destroy|Statistics.ini
FileKey6=%commonappdata%\Spybot - Search & Destroy\Backups|*.log

JDPower

Mar 1 2008, 09:59 PM

QUOTE (fredvries @ Mar 1 2008, 07:06 PM)

My (working) SpyBot entries:

CODE

That's the same as what I've got and working apart from the the last line, filekey6, I assume you added that yourself. As I said the detect key is currently wrong, has been since Spybot 1.5 came out AFAIA, and needs changing to the above.

jc836

Mar 2 2008, 05:06 AM

I just changed the Key and did see Spybot SnD on the menus. The way I redid the key was to use a second copy of the winapi file and rename the original winapiold. Works fine and Spybot SnD is being seen and cleaned. CCleaner runs fine otherwise, btw.

JDPower

Mar 2 2008, 05:08 AM

QUOTE (jc836 @ Mar 2 2008, 05:06 AM)

I just changed the Key and do not see Spubot SnD on the menus. The way I redid the key was to use a second copy of the winapi file and rename the original winapiold. Am i missing something here? CCleaner runs fine otherwise, btw.

Just change the reg key in the winapp.ini, you don't need to make new copies of it. OR add the entire entry posted above into winapp2.ini

jc836

Mar 2 2008, 05:14 AM

Thanks. Works fine. I'll delete the winapiold file. I've already renamed the good version

fredvries

Mar 2 2008, 08:16 AM

@ JDPower:

QUOTE

That's the same as what I've got and working apart from the the last line, filekey6, I assume you added that yourself.

Yes, I added that one myself (and reported it to MrG). I works perfectly on my system.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.