XP update won't reboot

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Last week I ran update on my XP Home system, and all went well till it rebooted. It then failed and I had to return to the last good installation. Unfortunately I didn't keep track of just what was installed. This has happened to me once before, and I just wonder if anyone else has had a similar problem.

Harvey
 
If you're asking if someone else had the same problem and you don't want to
solve the problem please ignore the rest of the post.

What error did you recive when it "failed" ?
Did you install critical updates or did you install driver and windows as
well ?
Do you now have all the critical updates installed ?

--

------------------------------------------------------------
For direct e-mailing remove "-spam" from my e-mail address
--
Best Regards,
Matija Hrovat
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services


Harvey said:
Last week I ran update on my XP Home system, and all went well till it
rebooted. It then failed and I had to return to the last good installation.
Unfortunately I didn't keep track of just what was installed. This has
happened to me once before, and I just wonder if anyone else has had a
similar problem.
 
Matija:

I don't recall any specific error. It just aborted the boot, and put up the screen which allowed me to return to the last good system. As to what I loaded, it was whatever MS said was needed. I think it was just 3 critical updates. They're not installed now, since I returned to the previous state.

I was wondering whether this is a known problem, so that it'll be fixed and I'll be able to update in the future. Or perhaps someone knows which of the updates is responsible, and I can install the others.

Harvey
 
Hi,
sorry for the late response.

I have seen the problems with windows updates (unfortunately never at my own
computer).
If you have a fresh install, you have a hardware problem. Of course you
don't have clean install :)

Tell me (us) which updates are missing (you said 3 (are they CRITICAL =
SECURITY))?

If they are (and you don't have a clean install) try disabling Start Up
Items and NON MS Services (KB: 310353) and try installing the updates
again.
The only problem is, that you should back up everything before installing
any update (or at least have a possibility to return your data via another
computer).
If you know what an image of a disk means - use it!

Tell me (us), which updates do you have left to install ??

And finally,
you cannot know what update is causing you problems, if you don't anwser the
questions I gave you in the previous posts.

Hope I anwsered some of your questions, for the rest, fill the holes...

--

------------------------------------------------------------
For direct e-mailing remove "-spam" from my e-mail address
--
Best Regards,
Matija Hrovat
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services

Harvey said:
Matija:

I don't recall any specific error. It just aborted the boot, and put up
the screen which allowed me to return to the last good system. As to what I
loaded, it was whatever MS said was needed. I think it was just 3 critical
updates. They're not installed now, since I returned to the previous state.
I was wondering whether this is a known problem, so that it'll be fixed
and I'll be able to update in the future. Or perhaps someone knows which of
the updates is responsible, and I can install the others.
 
OK Matija - I did it again.
This time I got 5 updates:

KB823353, KB840315, KB841873, KB839643, KB839645

They were "successfully installed", but the reboot blew up, twice.
It gave no information or error code.

I restored to the prior good configuration, which loaded fine, but it then tried to run "Windows Installer", which hung, and I had to cancel it.

Now I seem to be running fine under the old config.

Harvey
 
I think that we don't understand each other.
You should install the updates after you exclude the startup items and the
services that aren't Microsoft's.

Let's try a different approach.

Here you have 5 links to your 5 updates.

Try installing one by one. Restart computer after each install.
You can than see which one isn't compatible with your computer.

KB823353:
MS04-018: Cumulative security update for Outlook Express
(http://www.microsoft.com/technet/security/bulletin/ms04-018.mspx)
(http://www.microsoft.com/downloads/details.aspx?FamilyId=AD6A96BC-DAF0-4EAB
-89B8-BD702B3E3E5D&displaylang=en) for OLEXP 6 Sp1

KB840315:
MS04-023: Vulnerability in HTML Help could allow code execution
(http://www.microsoft.com/technet/security/bulletin/ms04-023.mspx)
(http://www.microsoft.com/downloads/details.aspx?FamilyId=8B412C7F-44AD-4E77
-8973-FD3E84CC496A&displaylang=en) for WinXp and WinXp SP1

KB841873:
MS04-022: A vulnerability in Task Scheduler could allow code execution
(http://www.microsoft.com/technet/security/bulletin/ms04-022.mspx)
(http://www.microsoft.com/downloads/details.aspx?FamilyId=8E8D0A2D-D3B9-4DE8
-8B6F-FC27715BC0CF&displaylang=en) for WinXp Sp1

KB839643:
MS04-016: Vulnerability in DirectPlay could allow denial of service
(http://www.microsoft.com/technet/security/bulletin/ms04-016.mspx)
(http://www.microsoft.com/downloads/details.aspx?FamilyId=1BEF9C9D-B317-4575
-90E6-E89779469D37&displaylang=en) for WinXp and WinXp Sp1

KB839645:
MS04-024: A vulnerability in Windows Shell could allow remote code execution
(http://www.microsoft.com/technet/security/bulletin/ms04-024.mspx)
(http://www.microsoft.com/downloads/details.aspx?FamilyId=C3365B8E-666B-4C82
-A9ED-FC0F84F107BA&displaylang=en) for WinXp and WinXp Sp1

If your computer "blows up" (Does that mean that restarts ?) try Safe Mode
before doing Last Known Good Configuration.

One more thing.
Didn't understand you what did you mean by running the "Windows Installer" ?

--

------------------------------------------------------------
For direct e-mailing remove "-spam" from my e-mail address
--
Best Regards,
Matija Hrovat
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services

Harvey said:
OK Matija - I did it again.
This time I got 5 updates:

KB823353, KB840315, KB841873, KB839643, KB839645

They were "successfully installed", but the reboot blew up, twice.
It gave no information or error code.

I restored to the prior good configuration, which loaded fine, but it then
tried to run "Windows Installer", which hung, and I had to cancel it.
 
Matija:
You should install the updates after you exclude the startup items and the
services that aren't Microsoft's.

All 5 are Microsoft, aren't they? What services are NOT Microsoft's?
Try installing one by one. Restart computer after each install.

That's a good idea.
If your computer "blows up" (Does that mean that restarts ?)

Yes. The boot aborts and restarts, going to the error screen.
try Safe Mode before doing Last Known Good Configuration.

But those are alternate selections on the same menu.
Didn't understand you what did you mean by running the "Windows Installer" ?

After I booted using the last good config, a window appeared, labelled "Windows Installer", which just sat there till I cancelled it.

Harvey
 
How you doin' Harvey :)

Look, MS Services, the things that you have listed in services (Start/Run:
services.msc)

If you go to msconfig (Start/Run: msconfig)

On General tab you select Selective startup
Uncheck Load Startup Items

Go to Services tab CHECK Hide All Microsoft Services
The list of services will shorten
Click UNCHECK every service that is still in the list
Click OK
Click Restart

Now you have "Clean Booted" your Windows;

How to perform a clean boot in Windows XP
http://support.microsoft.com/?id=310353

If you haven't already downloaded the mentioned updates do that BEFORE doing
a clean boot, because you will disable the antivirus program with msconfig
as well.

So the steps are:
You download the mentioned updates.
You perform clean boot.
You install the updates one by one, reboot computer after each install.
If it boots normally continue with the next update, if it doesn't, boot into
safe mode (http://support.microsoft.com/?id=315222)
Let me know which update is causing the problem.

Hope I explained everything all right, if not contact me again and I'll try
again :)

--

------------------------------------------------------------
For direct e-mailing remove "-spam" from my e-mail address
--
Best Regards,
Matija Hrovat
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services

Harvey said:
Matija:


All 5 are Microsoft, aren't they? What services are NOT Microsoft's?


That's a good idea.


Yes. The boot aborts and restarts, going to the error screen.


But those are alternate selections on the same menu.
Installer" ?

After I booted using the last good config, a window appeared,
labelled "Windows Installer", which just sat there till I cancelled it.
 
Thanks for staying with me on this, Matija. <g>

After your last message, I tried installing subsets of the updates.
I did KB823353 & KB840315. That blew the reboot.

So then I installed KB823353 alone, and that worked fine, suggesting that KB840315 is the problem.

Rather than blow again, I installed KB841873, and rebooted successfully.

So I'm willing to accept that it is KB840315 that is causing the boot abort.

Is there any way to find out whether this is a known problem, or whether I'm unique?

Is it still necessary to do the 'clean boot'?

I don't understand part of your instructions. You say to download the updates without installing them, but the MS download site downloads and installs each one seamlessly before completing. I see no way to download without installing.

Harvey
 
Yes, still try doing clean boot.
First apply all patches except 840315 (if you haven't already done so)

You should download the patch because you don't need you internet connection
after doing a clean boot (read earlier posts - Antivirus).

Did you try going into safe mode after computer didn't start in normal mode
?

--

------------------------------------------------------------
For direct e-mailing remove "-spam" from my e-mail address
--
Best Regards,
Matija Hrovat
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services

Harvey said:
Thanks for staying with me on this, Matija. <g>

After your last message, I tried installing subsets of the updates.
I did KB823353 & KB840315. That blew the reboot.

So then I installed KB823353 alone, and that worked fine, suggesting that KB840315 is the problem.

Rather than blow again, I installed KB841873, and rebooted successfully.

So I'm willing to accept that it is KB840315 that is causing the boot abort.

Is there any way to find out whether this is a known problem, or whether I'm unique?

Is it still necessary to do the 'clean boot'?

I don't understand part of your instructions. You say to download the
updates without installing them, but the MS download site downloads and
installs each one seamlessly before completing. I see no way to download
without installing.
 
Matija:
Did you try going into safe mode after computer didn't start in normal mode

No, because I have no idea what I'd do in 'safe mode', or after a 'clean boot'.
I'll have to go read the reference pages you gave me to try to understand why it would make a difference.

I'm not intellectually equipped to debug this problem. I just need to know whether Microsoft has seen it before, and whether it'll fix it.


Harvey
 
You'll have to contact your MS support service for the MS answer.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

I'm just trying to help you.
If it works in clean boot it means that some program is in conflict with the
update.
If it works in safe mode, it's a hardware problem.

If you tell me where it works we can continue.
If you have enough, I'll maybe "see" you in another topic.

--

------------------------------------------------------------
For direct e-mailing remove "-spam" from my e-mail address
--
Best Regards,
Matija Hrovat
Avtenta.SI
Microsoft Gold Certified Partner
for Support Services


Harvey said:
Matija:
mode

No, because I have no idea what I'd do in 'safe mode', or after a 'clean boot'.
I'll have to go read the reference pages you gave me to try to understand
why it would make a difference.
I'm not intellectually equipped to debug this problem. I just need to
know whether Microsoft has seen it before, and whether it'll fix it.
 
Back
Top