Mourning the loss of our friend, WhitPhil.
There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
Search
 
General Security
Tag Cloud
access audio blue screen boot bsod connection crash dell desktop driver dvd email error excel firefox hard drive hardware hijackthis internet keyboard laptop malware monitor motherboard network networking outlook problem processor ram recovery router safe mode screen slow sound spyware tdlwsp.dll trojan upgrade vba video virus vista vundo windows windows 7 windows vista windows xp wireless
Search
Search for:
Tech Support Guy Forums > Security & Malware Removal > General Security >
Solved: Weird warning from Spybot on computer startup

Tip: Click here to scan for System Errors and Optimize PC performance
[ Sponsored Link ]

Closed Thread
 
Thread Tools
josephpolk's Avatar
Member with 44 posts.
 
Join Date: Dec 2004
Location: Pittsburgh, PA
Experience: Advanced
07-Aug-2008, 07:44 PM #1
Solved: Weird warning from Spybot on computer startup
Everytime I turn my computer on, I receive the following warning from SpyBot (please click on the link to see the error message):

http://img149.imageshack.us/my.php?i...rderrorxs1.gif

I'm having a hard time finding anything about this error anywhere. Everytime it comes up, I "deny it" and then tell Spybot to remember it -- but it still comes up on each booting of my computer.

Has anyone else seen this before? If so, what did you do to fix it?

Thanks in advance for any and all help!!!
Elvandil's Avatar
Computer Specs
Moderator with 36,830 posts.
 
Join Date: Aug 2003
Location: Vermont
07-Aug-2008, 07:54 PM #2
The BootExecute key in the registry determines what gets executed at boot time (one of the places). Typically, entries made there are for running chkdsk at boot time or for defraggers to run a boot-time scan. If a scan is scheduled and runs, then the key will be changed to remove the entry so it won't run on the next boot.

Take a look at the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager:BootExecute. It should have entries for autochk and maybe your defragger.

Those changes need to be allowed.

If nothing is scheduled, the entry should be:

autocheck autochk *

If it has more than that, edit it. You may have an infection if it returns.
__________________
Microsoft MVP
Windows Shell/User
josephpolk's Avatar
Member with 44 posts.
 
Join Date: Dec 2004
Location: Pittsburgh, PA
Experience: Advanced
08-Aug-2008, 12:11 AM #3
That fixed it!
Elvandil:

That did it! Thank you SO MUCH for your help with this. I fixed a problem and learned something in the process!
Elvandil's Avatar
Computer Specs
Moderator with 36,830 posts.
 
Join Date: Aug 2003
Location: Vermont
08-Aug-2008, 12:26 AM #4
What worked? Did you need to edit it?

The real question is, "Where did that entry come from?" Was some bad guy trying to start up?
Closed Thread Bookmark and Share

THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Smart Search

Find your solution!



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.

Thread Tools


You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -5. The time now is 03:37 AM.
Copyright © 1996 - 2009 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2009, Jelsoft Enterprises Ltd.
Powered by Cermak Technologies, Inc.