XP Home Boot Loop

[ezman604]

Sorry for double posting. I think I posted in a general discussion forum, not
the correct one.
Working on a box that is loaded with XP Home Edition. Complaint of slow
performance and pop-ups. Sure enough, after loading a couple of AV & AS
programs, I find and delete several spywares, Trojans and various viruses.
Part of the cleaning process called for a reboot. That worked fine and all
nasty stuff was gone.
To finish the servicing of this unit, I ran an MS update check. There were a
few critical updates including IE7. After completing the install of the
updates, it called for another system reboot. Now it goes into a boot loop. I
get the Windows XP splash screen and then reboot.
I have gone in and attempted a boot in safe mode, Last Known Good and safe
with networking. None of these will boot, same loop going on. I've booted
from XP cd and from the repair screen, ran chkdsk /r. This found and fix some
issues but still have the same loop. I've booted into Safe with Command
Prompt and it gets to Drivers\Mup.sys before rebooting, which I think is
telling me there is a driver issue from the MS update.
Is there a way I can revive this box to a state before doing the last MS
update? There is a lot of data files on this unit and I do not want to
rebuild it and possibly lose them. I do have the option available of pulling
the hard drive and slaving into another machine to access files and folders.
Maybe there's a corrective action I can take through that avenue?
ANY suggestions and help will be greatly appreciated!!!!!

 

[Mark L. Ferguson]

Since chkdsk was successful, a 'repair' setup isn't going to do anything to
your ability to scalp the data if you fail to repair.
315341 - How to Perform an In-Place Upgrade (Reinstallation or Repair) of
Windows XP: http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
In your case, you will probably need to have the IE 7 install files handy
--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
..

 

[ezman604]

hanks for the speedy reply Mark.
I've opened the in-place upgrade page but I'm not seeing on the box what the
web page indicates. I booted from XP disk, selected setup XP, F8 to accept
EULA and it then comes to thye partition list. There are 2 on this Sony VAIO
desktop, C: & D:. I'm assuming D: is a virtual drive for a restore partition.
Anyway, the instructions say to make sure the proper partition is highlighted
and then hit "R" to repair. I only have the options to Enter to continue
Windows XP setup, C to create a new partition and D to delete selected
partition. I've select Enter to continue and there is no "R" for repair
option on the next screen either.
I'm holding off doing anything else till I hear back.
I am not taking a chance on messing it up any further.
Again, THANKS!!!

 

[Mark L. Ferguson]

I suspect the registry is so damaged that the repair offer is not possible.
This article goes into a repair try that may make data recovery easier,
anyway. You may even find a restore point this way.

How to Recover from a Corrupted Registry -config-system:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q307545
--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
..

 

[ezman604]

Well, going from bad to worse on this one.
I followed the procedures on the link you gave to recover from a corrupt
registry. I've done this procedure before. I took the first set of commands
and created a .txt file and ran the batch regcopy1.txt like it says. Then
you're supposed to reboot and go under Safe mode and look for the folder
where the restore points are stashed. However, after running the first batch
and exiting repair, system reboots and gives the message:
Windows can not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM

 

[Mark L. Ferguson]

If that fails, I'm afraid I have to say you will save more lost time just
scalping the data. That technique should work, if any will.

--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
..

 

[db.·.. >]

what may have happened is
that some of the system files
could have been substituted
with malware in order to
integrate themselves into
the o.s.

then when the av and as
deleted the corrupted
system files, they were
not replaced with the
genuine ones, thus the
likely cause of the issue
at hand.

however, barring a repair
installation log into your
disk system via the
recovery console again
and try the command

fixboot

 

[ezman604]

Thanks for the suggestion. Just tried that also.
Was asked if I was sure I wanted to do that and I said yes and let it run
the process. Reboot, same message about missing or corrupt Config\System
file. May have to attempt a Windows OS replacement.

 

[db.·.. >]

there are a number of
reasons why the registry
can become corrupted.

there are a couple of ways
to repair the registry.

the link below and
provided to you
by mark provides you
with the instructions:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q307545

the instructions seem
pretty intimidating at
first so print them out
if you can and spend at
least 30 minutes to
understand the steps.

it sounds like you have
a mind for fixing computers
so you should learn the
procedures provided
by microsoft.

basically, repairing a corrupted
registry as per the link above
entails using the recovery console
(which you have done already).

however, you will use it to
access the system folders to
access and replace the
corrupted registry hive
with a basic one that is
safely stored.

after the machine and windows
become functional again, you
can then replace the basic
registry hive with a registry that
is up to date and store safely
in your computer (this step
is part 2 of the link above).

------------------------

another option is to "repair
the o.s." and not replace it
as you mentioned.

a repair installation simply
compares the files on the
harddrive to the setup cd
and any files that are missing
will be replaced by those on
the genuine windows cd.

good luck and let us know!

 

[Mike]

Hello, I too am having a problem with a boot loop after attempting to do a
system repair with the XP installation disk. I came across this threat while
researching a solution. I am prepared to try this bootfix in the recovery
console, but don't want to do anything that detroys the data on my hard
drive. Not as long as there is any hope that I can still save it, and I
don't think I've exhausted all options yet.

Can you tell me what will happen if I run this command in the recovery
console? Will it wipe out my data or reformat my drive?

Thanks