This KB Article might give you some fiox:
http://support.microsoft.com/default...b;en-us;883821
"Stone Free" wrote:
> I have only just recently got broadband and I have been configuring my
> Kerio firewall rules and so at certain times svchost has not been able
> to do its stuff and so automatic updates hasnt been able to contact the
> server.
>
> Last week when I first got broadband the automatic upates icon appeared
> and it said that SP2 was ready for download, it then downloaded
> preliminary amount. The next time the icon appeared it stayed on 0%, it
> stayed at 0% for a long time. For some of this time svchost had been
> blocked by incorrectly set rules and "Windows update.log" showed that it
> failed with 80072ee7 and 8024402c.
>
> I have since got the rules right, but automatic updates does not seem to
> discover SP2, but if I goto windows update manually it lists SP2 as an
> essential update.
>
>
> 2004-08-28 16:55:47+0100 1176 49c Service received
> SERVICE_CONTROL_SHUTDOWN control
> 2004-08-28 16:55:47+0100 1176 6c Exiting Service Main
> 2004-08-28 16:55:47+0100 1176 6c ISusInternal API
> CClientCallRecorder:
isconnectCall succeeds
> 2004-08-28 16:55:47+0100 1176 6c DM: SetNotifyInterface failed
> with 0x80080008.
> 2004-08-28 16:57:03+0100 1196 558 Service Main starts
> 2004-08-28 16:57:03+0100 1196 558 Using BatchFlushAge = 33111.
> 2004-08-28 16:57:03+0100 1196 558 Using SamplingValue = 493.
> 2004-08-28 16:57:03+0100 1196 558 Successfully loaded event
> namespace dictionary.
> 2004-08-28 16:57:03+0100 1196 558 Successfully loaded client
> event namespace descriptor.
> 2004-08-28 16:57:03+0100 1196 558 Successfully initialized local
> event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution
> \ReportingEvents.log.
> 2004-08-28 16:57:04+0100 1196 558 Successfully initialized NT
> event logger.
> 2004-08-28 16:57:04+0100 1196 558 Successfully initialized event
> uploader 0.
> 2004-08-28 16:57:04+0100 1196 558 Reopened existing event cache
> file at C:\WINDOWS\SoftwareDistribution\EventCache\{44569C 6F-B3AD-4225-
> 9727-7F0F7DE1532B}.bin for writing.
> 2004-08-28 16:57:04+0100 1196 558 Successfully initialized event
> uploader 1.
> 2004-08-28 16:57:04+0100 1196 558 WU client with version
> 5.4.3790.2182 successfully initialized
> 2004-08-28 16:57:04+0100 1196 558 Service status is now
> SERVICE_RUNNING
> 2004-08-28 16:57:14+0100 1196 4b0 Service received connect
> notification
> 2004-08-28 16:57:49+0100 1196 558 start delayed initialization
> of WU client
> 2004-08-28 16:57:49+0100 2808 afc Trying to make out of proc
> datastore active
> 2004-08-28 16:57:50+0100 2808 afc Out of proc datastore is now
> active
> 2004-08-28 16:57:50+0100 1196 558 WU client successfully loaded
> ongoing download call {150C3787-E442-47B0-9EE7-85148444B1F1} from
> datastore
> 2004-08-28 16:57:50+0100 1196 558 WU client successfully loaded
> ongoing download call {89D991B9-3A8E-4D55-9A54-F052CA06A1D5} from
> datastore
> 2004-08-28 16:57:50+0100 1196 558 WU client succeeded to load 2
> persisted Download Calls
> 2004-08-28 16:57:50+0100 1196 558 Client Call Recorder finished
> delayed initialization
> 2004-08-28 16:57:50+0100 1196 558 AU finished delayed
> initialization
> 2004-08-28 16:57:50+0100 1196 55c WU client calls back to
> download call {89D991B9-3A8E-4D55-9A54-F052CA06A1D5} with code Call
> progress and error 0
> 2004-08-28 16:58:04+0100 1196 558 AU received event of 1
> 2004-08-28 16:58:04+0100 1196 558 No pending client directive,
> bailing out
>
>