G
Guest
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?
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?