Don't Use Automatic Update on Windows 2000, It's Not Safe and Crashed my Machine

[Critical Popperian]

Don't Use Automatic Update on Windows 2000, It's Not Safe and Crashed my Machine

I rebooted after an automatic update and it gives me a text message
Blue Screen of Death of CONFIG_INITIALIZATION_FAILED at start-up.

Nothing online has helped and Microsoft hasn't answered the problem, so,
I assume I've got to trash it.

It's kind of funny. We've been inching towards Linux little by little
with a couple dual-boot boxes and things, but we always expected to
"choose" Linux, not be forced onto it because our Windows boxes all
became unbootable.

What a pain in the butt. Anyway, if anyone knows how to get around this crash,
let me know. I may just hose Windows once and for all, Debian Unstable is
finally good enough.

 

[Steve N.]

Can you boot into Safe Mode and remove the updates you did?

Steve

 

[Greg Stigers]

Stop code 0x67? Isn't that normally due to a hardware failure? Or, possibly
a device driver problem? (You * did * take a look at what updates you were
allowing, didn't you?) There are a few articles at
<http://search.microsoft.com/search/results.aspx?na=81&st=a&View=en-us&qu=&q
p=CONFIG_INITIALIZATION_FAILED&qa=&qn=&c=&s=0> that are probably worth
looking at.

 

[BeamGuy]

Last night my home win2kpro system told me an automatic update was availiable - maybe I was
lucky I did not install it then...

Today there is no update for my work system - both were up to date will all the latestest updates
on Friday.

Where is the update that my home system wanted to install on Sunday afternoon? Was one released
then or not? I have both a hardware and software firewall at home, so the popup was not unsolicited.
But are there other ways to fool the system?