Windows update stalls/hangs on initialisation

New PC XP Pro SP2 installed.
Have successfully applied most of the security critical updates.
Attempted to apply the monster 10mb update to .NET 1.1. This update stalled
during the initialisation. Attempts to retry this results in exactly the same
thing. Same problem arises attempting to apply any other hotfix. e.g.
KB885835.
Also blocking any attempt to run any other Windows installer runs. Something
as simple as install Windows installer clean up utility stalls on the
intialisation. NO ERRORS are reported. I have switched on verbose logging
and nothing obvious appears in the log file. Something is blocking both
windows upate and other installs, but what??? HELP HELP

"davem",

I am sorry you have hit this issue. Please open your windowsupdate.log and
post the last error you run into, along with maybe 10 more lines before it
to let us understand the context. Here is the procedure:
On Windows XP:

1. Click Start
2. Click Run
3. type: %WINDIR%\WindowsUpdate.log
4. Click OK
5. Next, when the log has opened, scroll all the way to the bottom.
6. Ensure this is the case by clicking anywhere inside the log and typing
the <CTRL> and <End> keys.
7. Now that you are at the bottom of the log, type <CTRL> then the <F> key
for Find.
8. When the Find window opens, in Direction click the "Up" radio button.
9. Still in the Find window, in the Find what: field, type in 0x and then
click the Find Next button.
10. You will find the very latest error, usually in a format such as
0x800732EF or 0xFFFFFB40.
11. Copy the whole line this code is on, and perhaps a few others around it,
to let us understand the context.
12. Reply to this thread in this newsgroup, and paste the text you copied
from the log.

Sincerely,

Pat Walters [MSFT]

"davem" <> wrote in message
news:275EA85C-BE67-4E3E-8BB6-...
> New PC XP Pro SP2 installed.
> Have successfully applied most of the security critical updates.
> Attempted to apply the monster 10mb update to .NET 1.1. This update
stalled
> during the initialisation. Attempts to retry this results in exactly the
same
> thing. Same problem arises attempting to apply any other hotfix. e.g.
> KB885835.
> Also blocking any attempt to run any other Windows installer runs.
Something
> as simple as install Windows installer clean up utility stalls on the
> intialisation. NO ERRORS are reported. I have switched on verbose
logging
> and nothing obvious appears in the log file. Something is blocking both
> windows upate and other installs, but what??? HELP HELP

Pat
Thank you for your assistance
I initiated the >NEt updae agin and thsi is all taht is dispayed on screen
before it appears to stall after about 5 minutes
Initializing installation... done!
Installing Microsoft .NET Framework 1.1 Service Pack 1 (update 1 of 1)...

The extract from the windows update log is as follows

2005-01-11 19:14:30-0000 1224 a90 DeviceStatus: 0x180200a,
DeviceProblemNumber: 00000000
2005-01-11 19:14:30-0000 1224 a90 WU client add update
{3025FDF0-D3B2-4F7E-859B-0010955ECE57}.100 to search result
2005-01-11 19:14:30-0000 1224 a90 WU client found 11 updates and 10
categories in search
2005-01-11 19:14:30-0000 1224 a90 WU client finished Searching for update
2005-01-11 19:14:30-0000 1224 a90 WU client calls back to search call
WindowsUpdate with code Call complete and error 0
2005-01-11 19:14:30-0000 1224 a90 WU client completed and deleted call
{0056022B-54AD-4596-AB4B-B0898AD349E6}
2005-01-11 19:14:35-0000 1224 a90 REPORT EVENT:
{C3BBF023-15FE-47F1-9180-34152D4EE3E7} 75 2005-01-11
19:14:30-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software Synchronization Agent has finished detecting items.
2005-01-11 19:15:10-0000 1224 1fc WU client succeeds
CClientCallRecorder::BeginInstallUpdates from WindowsUpdate with call id
{0BBA92B0-9398-49B8-8987-2FD8A86E07C6}
2005-01-11 19:15:10-0000 1224 788 WU client executing call
{0BBA92B0-9398-49B8-8987-2FD8A86E07C6} of type Install call
2005-01-11 19:15:10-0000 1224 788 validate updates before Install
2005-01-11 19:15:11-0000 1224 788 prune update list before Install
2005-01-11 19:15:11-0000 1224 788 setting system restore point
2005-01-11 19:20:11-0000 944 9e4 Out of proc datastore is shutting down
2005-01-11 19:20:12-0000 944 9e4 Out of proc datastore is now inactive
2005-01-11 19:25:11-0000 1224 788 Failed SRSetRestorePoint call with win32
error 1460
2005-01-11 19:25:11-0000 1224 788 WU client starts install in user context
2005-01-11 19:25:11-0000 1224 788 WU client is installing update
{AFCFDECF-2B9F-4881-8CFE-F56ED0DD81AF}

*****
It appears that teh set restore point fails - which is consistent with teh
fact that trying to start the system recovery console fails afer displaying a
blank window.

Hope this helps as this is also apparently blocking any other Windows
Installer runs, they all initialise and then hang


"Pat Walters [MSFT]" wrote:

> "davem",
>
> I am sorry you have hit this issue. Please open your windowsupdate.log and
> post the last error you run into, along with maybe 10 more lines before it
> to let us understand the context. Here is the procedure:
> On Windows XP:
>
> 1. Click Start
> 2. Click Run
> 3. type: %WINDIR%\WindowsUpdate.log
> 4. Click OK
> 5. Next, when the log has opened, scroll all the way to the bottom.
> 6. Ensure this is the case by clicking anywhere inside the log and typing
> the <CTRL> and <End> keys.
> 7. Now that you are at the bottom of the log, type <CTRL> then the <F> key
> for Find.
> 8. When the Find window opens, in Direction click the "Up" radio button.
> 9. Still in the Find window, in the Find what: field, type in 0x and then
> click the Find Next button.
> 10. You will find the very latest error, usually in a format such as
> 0x800732EF or 0xFFFFFB40.
> 11. Copy the whole line this code is on, and perhaps a few others around it,
> to let us understand the context.
> 12. Reply to this thread in this newsgroup, and paste the text you copied
> from the log.
>
> Sincerely,
>
> Pat Walters [MSFT]
>
> "davem" <> wrote in message
> news:275EA85C-BE67-4E3E-8BB6-...
> > New PC XP Pro SP2 installed.
> > Have successfully applied most of the security critical updates.
> > Attempted to apply the monster 10mb update to .NET 1.1. This update
> stalled
> > during the initialisation. Attempts to retry this results in exactly the
> same
> > thing. Same problem arises attempting to apply any other hotfix. e.g.
> > KB885835.
> > Also blocking any attempt to run any other Windows installer runs.
> Something
> > as simple as install Windows installer clean up utility stalls on the
> > intialisation. NO ERRORS are reported. I have switched on verbose
> logging
> > and nothing obvious appears in the log file. Something is blocking both
> > windows upate and other installs, but what??? HELP HELP
>
>
>

Pat
Hi where are you?
WHat the stalled and terminated .NET SP1 appears to have done is screw up
the system restore process.
I have disabled system restore. This freed up the ability to apply further
windows updates and application installs.
BUT when I try to re-enable system restore it fails with a message "System
restore encountered an error trying to enable/disable one or more drives,
please restart your machine and try again"
When I restart the machine and check it looks as though system restore is
enabled and Drive C: is being monitored. To attempt to prove this is OK I
attempted to create a manual Restore point, this just hangs and eventually
reports not responding after about 20 minutes. HELP

"Pat Walters [MSFT]" wrote:

> "davem",
>
> I am sorry you have hit this issue. Please open your windowsupdate.log and
> post the last error you run into, along with maybe 10 more lines before it
> to let us understand the context. Here is the procedure:
> On Windows XP:
>
> 1. Click Start
> 2. Click Run
> 3. type: %WINDIR%\WindowsUpdate.log
> 4. Click OK
> 5. Next, when the log has opened, scroll all the way to the bottom.
> 6. Ensure this is the case by clicking anywhere inside the log and typing
> the <CTRL> and <End> keys.
> 7. Now that you are at the bottom of the log, type <CTRL> then the <F> key
> for Find.
> 8. When the Find window opens, in Direction click the "Up" radio button.
> 9. Still in the Find window, in the Find what: field, type in 0x and then
> click the Find Next button.
> 10. You will find the very latest error, usually in a format such as
> 0x800732EF or 0xFFFFFB40.
> 11. Copy the whole line this code is on, and perhaps a few others around it,
> to let us understand the context.
> 12. Reply to this thread in this newsgroup, and paste the text you copied
> from the log.
>
> Sincerely,
>
> Pat Walters [MSFT]
>
> "davem" <> wrote in message
> news:275EA85C-BE67-4E3E-8BB6-...
> > New PC XP Pro SP2 installed.
> > Have successfully applied most of the security critical updates.
> > Attempted to apply the monster 10mb update to .NET 1.1. This update
> stalled
> > during the initialisation. Attempts to retry this results in exactly the
> same
> > thing. Same problem arises attempting to apply any other hotfix. e.g.
> > KB885835.
> > Also blocking any attempt to run any other Windows installer runs.
> Something
> > as simple as install Windows installer clean up utility stalls on the
> > intialisation. NO ERRORS are reported. I have switched on verbose
> logging
> > and nothing obvious appears in the log file. Something is blocking both
> > windows upate and other installs, but what??? HELP HELP
>
>
>