Processes to close before start with MS-XP update

P

Pierpi

New member
Dear all,

I have to update my Windows XP Home with SP3.
I tried but with an error code (0x8024400D) that could be related to a registry "protected" by SpyBot.
Since I have to retry without antivirus, firewall etc, my question is:
which are the processes related to SpyBot that can I kill before the update to SP3 in order to be shure that Spy Bot is completely turned off?

My current version is 1.6.0.

Thanks.
Pierpi
 
Pierpi:

There are two active protections associated with Spybot. The SDHelper (which is a Browser Helper Object (BHO)) and TeaTimer. To disable these features, go into Spybot > Mode > Advanced Mode > Tools > Resident. Under the heading "Resident protection status" you will see:
  • Resident "SDHelper" (Internet Explorer bad download blocker) active.
  • Resident "TeaTimer" (Protection of over-all system settings) active.
Uncheck both, then exit Spybot. To make sure that SDHelper is no longer active, either:
  • Reboot the system.
    --- or ---
  • Exit all Windows Explorer and Internet Explorer sessions.
________

After the installation, go into Spybot > Mode > Advanced Mode > Tools > Resident and check the following:
  • Resident "SDHelper" (Internet Explorer bad download blocker) active.
  • Resident "TeaTimer" (Protection of over-all system settings) active.
 
Last edited:
Interesting. I originally came here looking for a solution to my Spybot not being able to update itself. The manual link is apparently dead, btw, unless this workaround somehow would affect that, which I doubt. While looking around, I came upon this and, since my Windows Update had stopped in the middle after re-installing Spybot, wondered whether it could have something to do with the Spybot update, as well.

Sure enough, I did as you suggested here, re-booted my machine, and after that Spybot was able to perform its updates.

Is it possible that your software is keeping ITSELF from updating, as well? I noticed there was a TeaTimer update in there; is this issue addressed in that update, by any chance?

I'm going to leave TeaTimer and SDHelper disabled until I get a response of some sort.

Thanks for your time, guys.
 
Last edited:
TheJedi

TheJedi said:
... The manual link is apparently dead, btw, unless this workaround somehow would affect that, which I doubt. ...
Click to expand...
The manual update link is working fine.

TheJedi said:
... Is it possible that your software is keeping ITSELF from updating, as well? ...
Click to expand...
Possible but highly improbable since you are the only one to have reported such a incident. Most likely rebooting the system solved the problem that you were having with both the integrated updates and the manual updates and not the fact that you disable the real time protections.
 
Cool. I will go ahead and re-enable the real-time protections, then. I like that extra level of security. Thanks.
 
You must log in or register to reply here.
Back
Top