Sign in with
Sign up | Sign in
Your question

Failed boot after automatic update

Last response: in Windows XP
Share
Anonymous
December 20, 2004 10:05:03 AM

Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

I have had 2 clients report that their computers will not boot after the
latest Window XP updates were installed last week. (Both PCs already had
service pack 2 installed.)

The first PC reported that it was unable to load the OS after reboot. I
attempted to fix the error using the restore console. Check drive would only
get through about 30% and report that there were unrecoverable errors. On
further investigation through console I discovered that the MBR had been
corrupted. Attempting to fix the MBR had no effect. After about the 5th
reboot the BIOS would not recognize that a hard drive was even installed. (I
believe the drive has been damaged beyond repair.)

The second PC goes through the normal boot sequence and just hangs with a
black screen. When the PC rebooted the first time it reported that a windows
DLL file was not compatible.

I have since heard that several other people have been experiencing problems
with their PC after this latest pack of updates were installed last week.
(Perhaps Microsoft should look into what is causing this problem on some PCs
and not others.)

Anyone have any ideas as to what is going on here? Or better yet, how to fix
it?
December 20, 2004 1:23:10 PM

Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

I had a problem last week with autoupdates like yours, i had 5 machines that
could not be accessed by user or admin, even locally !! I booted to "last
good known" and removed the updates from comtrol panel, fixed all problems.
do not have much faith now in autoupdates however !!

Steve

"SAG Admin" wrote:

> I have had 2 clients report that their computers will not boot after the
> latest Window XP updates were installed last week. (Both PCs already had
> service pack 2 installed.)
>
> The first PC reported that it was unable to load the OS after reboot. I
> attempted to fix the error using the restore console. Check drive would only
> get through about 30% and report that there were unrecoverable errors. On
> further investigation through console I discovered that the MBR had been
> corrupted. Attempting to fix the MBR had no effect. After about the 5th
> reboot the BIOS would not recognize that a hard drive was even installed. (I
> believe the drive has been damaged beyond repair.)
>
> The second PC goes through the normal boot sequence and just hangs with a
> black screen. When the PC rebooted the first time it reported that a windows
> DLL file was not compatible.
>
> I have since heard that several other people have been experiencing problems
> with their PC after this latest pack of updates were installed last week.
> (Perhaps Microsoft should look into what is causing this problem on some PCs
> and not others.)
>
> Anyone have any ideas as to what is going on here? Or better yet, how to fix
> it?
Anonymous
December 21, 2004 11:39:03 PM

Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

I also had the same problem, now my computer is sitting on the floor with 2
years worth of photos that probably can't be recovered. Computer just would
not reboot, did not reconize operating system.

"SAG Admin" wrote:

> I have had 2 clients report that their computers will not boot after the
> latest Window XP updates were installed last week. (Both PCs already had
> service pack 2 installed.)
>
> The first PC reported that it was unable to load the OS after reboot. I
> attempted to fix the error using the restore console. Check drive would only
> get through about 30% and report that there were unrecoverable errors. On
> further investigation through console I discovered that the MBR had been
> corrupted. Attempting to fix the MBR had no effect. After about the 5th
> reboot the BIOS would not recognize that a hard drive was even installed. (I
> believe the drive has been damaged beyond repair.)
>
> The second PC goes through the normal boot sequence and just hangs with a
> black screen. When the PC rebooted the first time it reported that a windows
> DLL file was not compatible.
>
> I have since heard that several other people have been experiencing problems
> with their PC after this latest pack of updates were installed last week.
> (Perhaps Microsoft should look into what is causing this problem on some PCs
> and not others.)
>
> Anyone have any ideas as to what is going on here? Or better yet, how to fix
> it?
Related resources
Anonymous
December 22, 2004 5:31:34 PM

Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

Gentlemen,

Best thing to do is recover files and start from scratch... This is just my
personal opinion... I fear issues like this where they are
indistinguishable... I trust a newly installed system... Use a utility to
recover the files, then reimage the machine(s)...

To recover your files you could use a third party product (assuming you have
one that will access your drives), you could remove the hard drive, place it
in another machine and recover the files that way, or you could try Bart's
PE boot disk with network support you could run a psuedo WinXP shell off of
CD and recover your files to network drive... The quickest way it to remove
the drive and access it from another computer...

Stew Basterash

"SAG Admin" <SAG Admin@discussions.microsoft.com> wrote in message
news:A571EFD1-32C9-4DB5-8142-5CA1CDBA953D@microsoft.com...
>I have had 2 clients report that their computers will not boot after the
> latest Window XP updates were installed last week. (Both PCs already had
> service pack 2 installed.)
>
> The first PC reported that it was unable to load the OS after reboot. I
> attempted to fix the error using the restore console. Check drive would
> only
> get through about 30% and report that there were unrecoverable errors. On
> further investigation through console I discovered that the MBR had been
> corrupted. Attempting to fix the MBR had no effect. After about the 5th
> reboot the BIOS would not recognize that a hard drive was even installed.
> (I
> believe the drive has been damaged beyond repair.)
>
> The second PC goes through the normal boot sequence and just hangs with a
> black screen. When the PC rebooted the first time it reported that a
> windows
> DLL file was not compatible.
>
> I have since heard that several other people have been experiencing
> problems
> with their PC after this latest pack of updates were installed last week.
> (Perhaps Microsoft should look into what is causing this problem on some
> PCs
> and not others.)
>
> Anyone have any ideas as to what is going on here? Or better yet, how to
> fix
> it?
Anonymous
December 22, 2004 7:45:04 PM

Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

This is probably going to sound silly, but how can you access a hard drive if
it is removed fom the computer?

"Stewart Basterash" wrote:

> Gentlemen,
>
> Best thing to do is recover files and start from scratch... This is just my
> personal opinion... I fear issues like this where they are
> indistinguishable... I trust a newly installed system... Use a utility to
> recover the files, then reimage the machine(s)...
>
> To recover your files you could use a third party product (assuming you have
> one that will access your drives), you could remove the hard drive, place it
> in another machine and recover the files that way, or you could try Bart's
> PE boot disk with network support you could run a psuedo WinXP shell off of
> CD and recover your files to network drive... The quickest way it to remove
> the drive and access it from another computer...
>
> Stew Basterash
>
> "SAG Admin" <SAG Admin@discussions.microsoft.com> wrote in message
> news:A571EFD1-32C9-4DB5-8142-5CA1CDBA953D@microsoft.com...
> >I have had 2 clients report that their computers will not boot after the
> > latest Window XP updates were installed last week. (Both PCs already had
> > service pack 2 installed.)
> >
> > The first PC reported that it was unable to load the OS after reboot. I
> > attempted to fix the error using the restore console. Check drive would
> > only
> > get through about 30% and report that there were unrecoverable errors. On
> > further investigation through console I discovered that the MBR had been
> > corrupted. Attempting to fix the MBR had no effect. After about the 5th
> > reboot the BIOS would not recognize that a hard drive was even installed.
> > (I
> > believe the drive has been damaged beyond repair.)
> >
> > The second PC goes through the normal boot sequence and just hangs with a
> > black screen. When the PC rebooted the first time it reported that a
> > windows
> > DLL file was not compatible.
> >
> > I have since heard that several other people have been experiencing
> > problems
> > with their PC after this latest pack of updates were installed last week.
> > (Perhaps Microsoft should look into what is causing this problem on some
> > PCs
> > and not others.)
> >
> > Anyone have any ideas as to what is going on here? Or better yet, how to
> > fix
> > it?
>
>
>
Anonymous
December 22, 2004 7:45:04 PM

Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

This is probably going to sound silly, but how can you access a hard drive if
it is removed fom the computer?

"Stewart Basterash" wrote:

> Gentlemen,
>
> Best thing to do is recover files and start from scratch... This is just my
> personal opinion... I fear issues like this where they are
> indistinguishable... I trust a newly installed system... Use a utility to
> recover the files, then reimage the machine(s)...
>
> To recover your files you could use a third party product (assuming you have
> one that will access your drives), you could remove the hard drive, place it
> in another machine and recover the files that way, or you could try Bart's
> PE boot disk with network support you could run a psuedo WinXP shell off of
> CD and recover your files to network drive... The quickest way it to remove
> the drive and access it from another computer...
>
> Stew Basterash
>
> "SAG Admin" <SAG Admin@discussions.microsoft.com> wrote in message
> news:A571EFD1-32C9-4DB5-8142-5CA1CDBA953D@microsoft.com...
> >I have had 2 clients report that their computers will not boot after the
> > latest Window XP updates were installed last week. (Both PCs already had
> > service pack 2 installed.)
> >
> > The first PC reported that it was unable to load the OS after reboot. I
> > attempted to fix the error using the restore console. Check drive would
> > only
> > get through about 30% and report that there were unrecoverable errors. On
> > further investigation through console I discovered that the MBR had been
> > corrupted. Attempting to fix the MBR had no effect. After about the 5th
> > reboot the BIOS would not recognize that a hard drive was even installed.
> > (I
> > believe the drive has been damaged beyond repair.)
> >
> > The second PC goes through the normal boot sequence and just hangs with a
> > black screen. When the PC rebooted the first time it reported that a
> > windows
> > DLL file was not compatible.
> >
> > I have since heard that several other people have been experiencing
> > problems
> > with their PC after this latest pack of updates were installed last week.
> > (Perhaps Microsoft should look into what is causing this problem on some
> > PCs
> > and not others.)
> >
> > Anyone have any ideas as to what is going on here? Or better yet, how to
> > fix
> > it?
>
>
>
December 22, 2004 7:59:58 PM

Archived from groups: microsoft.public.windowsxp.security_admin (More info?)

Misty wrote:

> This is probably going to sound silly, but how can you access a hard
> drive if it is removed fom the computer?
>
You slave the drive in a working computer.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
!