Does the new MS Security patch hose your computer?

BlvdKing

Golden Member
Jun 7, 2000
1,173
0
0
I have tried installing the new security patch for WinXP that just came out and it completely hoses my computer. It downloads and installs fine, but when I reboot, the computer will start to load Windows and then start shutting down almost immediatedly. It does this forvever. I had to repair my installation using the WinXP CD to get it too work. A friend of mine with a Dell (totally differnent config) had this problem as well.

Does this happen to you?

My system:
TBird 1200
Giga-byte 7zx (KT133)
384MB SDRAM @ 133 Cas 3
VT GF3 Ti 200
Audigy


This is the place to discuss the latest computer hardware issues and technology. Please keep the discussion ON TOPIC, and covering computer hardware ONLY.




AnandTech Moderator

 

corkyg

Elite Member | Peripherals
Super Moderator
Mar 4, 2000
27,370
240
106
No problems here with any of the 4 XP criticals to date. ???
 

robg1701

Senior member
Feb 12, 2000
560
0
0
Dunno yet, i aint installing it until im already gona be formatting :)

Ive test run XP for a couple months now to get it all sorted out and find my ideal setup...in a couple days ill be nuking it, moving over to NTFS again, getting it up to a base state i want to return to when needed, and then make up my cd's.
 

Cybordolphin

Platinum Member
Oct 25, 1999
2,813
0
0
Yes...

I too started to have major error problems.. and had to reformat and reinstall on my systems. I believe it was due to a combo of the downloads and overclock settings. I have backed everything down.... and reinstalled. Now I am back to a very stable setup.

I am a tad reluctant to redownload the updates myself.

 

BFG10K

Lifer
Aug 14, 2000
22,709
3,003
126
Keep your firewall up and you won't need the patch. It's on by default anyway, that's why I suspect no-one's been affected.
 

kyoshozx

Senior member
Jun 16, 2000
588
0
0
It happened to me, after the patch windows XP refused to boot. I would get the blue screen, and it was caused by ati driver, since I was using the beta driver I figured that was the cause.