devilsminion
13-08-2003, 06:59
I usually do the critical updates on my XP and as I work for Canadas biggest ISP on Tues we were hit with thousands of calls about this nasty little bug.
From what I have experienced I went after about a million calls home and went to d/l the patch where I received that NT w32 shut down procedure so I turned on the XP firewall and was able to d/l the patch. I went and then went to symantec and did a scan for this culprit and was found to be clean. I then turned off the XP firewall and all is well.
I am about to check my registry as the culprit leaves a little note for Bill, something about fix your windows.
Anyone else with any advice???
From what I have experienced I went after about a million calls home and went to d/l the patch where I received that NT w32 shut down procedure so I turned on the XP firewall and was able to d/l the patch. I went and then went to symantec and did a scan for this culprit and was found to be clean. I then turned off the XP firewall and all is well.
I am about to check my registry as the culprit leaves a little note for Bill, something about fix your windows.
Anyone else with any advice???