PDA

View Full Version : spybot fails to start on reboot



degreen
2005-12-20, 19:36
spybot finds issues in which it needs to run after a reboot of the system, but never runs on startup. This machine also has issues with the removal of spy sheriff.

md usa spybot fan
2005-12-20, 21:47
Is the account that you are running the scan from a Limited account or a Computer Administrator account? Are you running any software that may prevent the addition of a "RunOnce" startup registry entries?

In order for the program to be run once at the next system startup the following entry must be placed in the registry:


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce]
"SpybotSnD"="\"C:\\Program Files\\Spybot - Search & Destroy\\SpybotSD.exe\""
If the user does not have authority to change the registry or that entry is being blocked by TeaTimer, Microsoft AntiSpyware, etc., Spybot will not run at startup.

degreen
2005-12-21, 18:02
Thanks but the value fails to stay once closing the registry

md usa spybot fan
2005-12-21, 18:16
As an alternative you can try to run Spybot-S&D in Safe mode and see if it will clean up your problems.
Reboot your system in Safe mode and run Spybot-S&D.
Starting your computer in Safe mode (http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2001052409420406?OpenDocument&src=sec_doc_nam)

degreen
2005-12-21, 18:32
ill try that again

Here is what is listed
Command Service: Settings (Registry key, fixing failed)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cmdService

Command Service: Settings (Registry key, fixing failed)
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\cmdService

Command Service: Settings (Registry key, fixed)
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\cmdService

Windows Security Center.AntiVirusDisableNotify: Settings (Registry change, fixed)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\AntiVirusDisableNotify!=dword:0


--- Spybot - Search & Destroy version: 1.4 (build: 20050523) ---

2005-05-31 blindman.exe (1.0.0.1)
2005-05-31 SpybotSD.exe (1.4.0.3)
2005-05-31 TeaTimer.exe (1.4.0.2)
2005-12-16 unins000.exe (51.41.0.0)
2005-05-31 Update.exe (1.4.0.0)
2005-05-31 advcheck.dll (1.0.2.0)
2005-05-31 aports.dll (2.1.0.0)
2005-05-31 borlndmm.dll (7.0.4.453)
2005-05-31 delphimm.dll (7.0.4.453)
2005-05-31 SDHelper.dll (1.4.0.0)
2005-05-31 Tools.dll (2.0.0.2)
2005-05-31 UnzDll.dll (1.73.1.1)
2005-05-31 ZipDll.dll (1.73.2.0)
2005-12-16 Includes\Cookies.sbi (*)
2005-12-16 Includes\Dialer.sbi (*)
2005-12-16 Includes\Hijackers.sbi (*)
2005-12-16 Includes\Keyloggers.sbi (*)
2004-05-12 Includes\LSP.sbi (*)
2005-12-16 Includes\Malware.sbi (*)
2005-12-16 Includes\PUPS.sbi (*)
2005-12-16 Includes\Revision.sbi (*)
2005-12-16 Includes\Security.sbi (*)
2005-12-16 Includes\Spybots.sbi (*)
2005-02-17 Includes\Tracks.uti
2005-12-16 Includes\Trojans.sbi (*)

md usa spybot fan
2005-12-21, 19:08
The following problem was fixed:

Windows Security Center.AntiVirusDisableNotify: Settings (Registry change, fixed)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\AntiVirusDisableNotify!=dword:0
If it returns after a reboot it may be because your antivirus is resetting the flag. Are you running Norton or McAfee antivirus?

If Spybot fails to fix the Command Service detections, consider requesting assistance in the Malware Removal forum and have one of the helpers there take a look at your system.

To post in the Malware Removal forum follow the instructions here:
Before you post a log
http://forums.spybot.info/showthread.php?t=288
Then post in the following forum:
Malware Removal
http://forums.spybot.info/forumdisplay.php?f=22

degreen
2005-12-21, 19:19
Thanks I will try that and then check with the other group