Windows XP SP2 hangs when restarted but does not when shutdown

[James Fee]

I have a windows XP SP2 box that will hang when the user attempts to restart
(start>shut down>restart). It will go thru shutting down all the programs
and the dialog box shows saving settings and shows closing network
connections and show shutting down windows, then the dialog box disappears,
then the mouse cursor disappears, then nothing. The box will remain with
just a the blue background, no dialog box, no mouse cursor.

However this same user/box can perform a shutdown (start>shut down>shut
down) and the box will shutdown properly.

I am a bit stumped at this point.

 

[Lanwench [MVP - Exchange]]

In

I have a windows XP SP2 box that will hang when the user attempts to
restart (start>shut down>restart). It will go thru shutting down all
the programs and the dialog box shows saving settings and shows
closing network connections and show shutting down windows, then the
dialog box disappears, then the mouse cursor disappears, then
nothing. The box will remain with just a the blue background, no
dialog box, no mouse cursor.
However this same user/box can perform a shutdown (start>shut
down>shut down) and the box will shutdown properly.

I am a bit stumped at this point.

Check the event logs for clues...

 

[andymarbles]

Check the event logs for clues...

Wouldn't the Event log service have stopped by that point?

 

[Lanwench [MVP - Exchange]]

In

Wouldn't the Event log service have stopped by that point?

After the user logs back in, he or she can open the event viewer, which
should have information about what was failing when the problem occurred.

 

[Guest]

Try running shutdown from the command prompt using these switches:
-s (Shutdown only)
-r (Shutdown and restart)

Does the behavior repeat there?

If so, then try it with the -f switch (to force stubborn apps to close)
-s -f
-r -f

Any improvement? If so, then try terminating running apps until you find
the one that's hanging. I had this problem with an out-dated version of
SyncBackSE on a computer at my wife's office.

Also, the Event Viewer may or may not catch the errors - but checking it
will ensure that you don't miss an important clue.

- John

 

[andymarbles]

In

On 26 Jan, 16:48, "Lanwench [MVP - Exchange]"

Check the event logs for clues...

Wouldn't the Event log service have stopped by that point?

After the user logs back in, he or she can open the event viewer, which
should have information about what was failing when the problem occurred.

The problem occurred after he Event Log service has stopped, is what I
mean.