Automatic Updates Query

I'm running XP Pro SP2.

I'm set to install updates automatically but I'm not sure it is doing
it properly. My Windows Update.log has not been modified since the 13
Aug: I understand the checks for AU are recorded there. I have
another file called WindowsUpdate.log which was created on 14 Aug and
seems to record the checks there but in a different format; for
instance it does not record an error or success like the
aforementioned log.

I manually downloaded SP2 last week because I thought the automatic
feature was not working.

I was wondering whether I should have these 2 logs and what their
functions were? I don't understand why the first log stopped on 13
Aug when it was getting modified every 1 or 2 days.

Is there a Windows Update FAQ/Troubleshooting guide available for XP?

Thanks Dave

(Dave Ranson) wrote in message news:<. com>...
> I'm running XP Pro SP2.
>
> I'm set to install updates automatically but I'm not sure it is doing
> it properly. My Windows Update.log has not been modified since the 13
> Aug: I understand the checks for AU are recorded there. I have
> another file called WindowsUpdate.log which was created on 14 Aug and
> seems to record the checks there but in a different format; for
> instance it does not record an error or success like the
> aforementioned log.
>
> I manually downloaded SP2 last week because I thought the automatic
> feature was not working.
>
> I was wondering whether I should have these 2 logs and what their
> functions were? I don't understand why the first log stopped on 13
> Aug when it was getting modified every 1 or 2 days.
>
> Is there a Windows Update FAQ/Troubleshooting guide available for XP?

OK folks, any advice out there?

Dave
>
> Thanks Dave

(Dave Ranson) wrote in message news:<. com>...
> (Dave Ranson) wrote in message news:<. com>...
> > I'm running XP Pro SP2.
> >
> > I'm set to install updates automatically but I'm not sure it is doing
> > it properly. My Windows Update.log has not been modified since the 13
> > Aug: I understand the checks for AU are recorded there. I have
> > another file called WindowsUpdate.log which was created on 14 Aug and
> > seems to record the checks there but in a different format; for
> > instance it does not record an error or success like the
> > aforementioned log.
> >
> > I manually downloaded SP2 last week because I thought the automatic
> > feature was not working.
> >
> > I was wondering whether I should have these 2 logs and what their
> > functions were? I don't understand why the first log stopped on 13
> > Aug when it was getting modified every 1 or 2 days.
> >
> > Is there a Windows Update FAQ/Troubleshooting guide available for XP?
>
> OK folks, any advice out there?
>
> Dave
> >
> > Thanks Dave

Anybody kind enough to answer my questions?

The 'Windows Update.log' file has still not been modified since 13 Aug 04.

Dave

Dave Ranson wrote:

> (Dave Ranson) wrote:
>> (Dave Ranson) wrote:
>>
>>>I'm running XP Pro SP2.
>>>
>>>I'm set to install updates automatically but I'm not sure it is doing
>>>it properly. My Windows Update.log has not been modified since the 13
>>>Aug: I understand the checks for AU are recorded there. I have
>>>another file called WindowsUpdate.log which was created on 14 Aug and
>>>seems to record the checks there but in a different format; for
>>>instance it does not record an error or success like the
>>>aforementioned log.
>>>
>>>I manually downloaded SP2 last week because I thought the automatic
>>>feature was not working.
>>>
>>>I was wondering whether I should have these 2 logs and what their
>>>functions were? I don't understand why the first log stopped on 13
>>>Aug when it was getting modified every 1 or 2 days.
>>>
>>>Is there a Windows Update FAQ/Troubleshooting guide available for XP?
>>
>>OK folks, any advice out there?
>
> Anybody kind enough to answer my questions?
>
> The 'Windows Update.log' file has still not been modified since 13 Aug 04.
Hi

As you have WinXP SP2, you are using WU v5, and it does not use the file
'Windows Update.log' (that was for WU v4). v5 uses the file WindowsUpdate.log.

Windows Update FAQ
http://v5.windowsupdate.microsoft.co....aspx?ln=en-us

Windows Update Troubleshooter
http://v5.windowsupdate.microsoft.co...oot.aspx?ln=en

and

Please try the following:

Click Start >> Run >>
Type the follow command in the Open box.
"net.exe stop wuauserv" (w/o quotes)
Press Ok

Repeat the same for the following commands:

regsvr32.exe wuapi.dll
regsvr32.exe wups.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wucltui.dll
regsvr32.exe msxml3.dll
net.exe start wuauserv


Restart the machine and see if it helps.


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

"Torgeir Bakken \(MVP\)" <Torgeir.Bakken-> wrote in message news:<#>...
> Dave Ranson wrote:
>
> > (Dave Ranson) wrote:
> >> (Dave Ranson) wrote:
> >>
> >>>I'm running XP Pro SP2.
> >>>
> >>>I'm set to install updates automatically but I'm not sure it is doing
> >>>it properly. My Windows Update.log has not been modified since the 13
> >>>Aug: I understand the checks for AU are recorded there. I have
> >>>another file called WindowsUpdate.log which was created on 14 Aug and
> >>>seems to record the checks there but in a different format; for
> >>>instance it does not record an error or success like the
> >>>aforementioned log.
> >>>
> >>>I manually downloaded SP2 last week because I thought the automatic
> >>>feature was not working.
> >>>
> >>>I was wondering whether I should have these 2 logs and what their
> >>>functions were? I don't understand why the first log stopped on 13
> >>>Aug when it was getting modified every 1 or 2 days.
> >>>
> >>>Is there a Windows Update FAQ/Troubleshooting guide available for XP?
> >>
> >>OK folks, any advice out there?
> >
> > Anybody kind enough to answer my questions?
> >
> > The 'Windows Update.log' file has still not been modified since 13 Aug 04.
> Hi
>
> As you have WinXP SP2, you are using WU v5, and it does not use the file
> 'Windows Update.log' (that was for WU v4). v5 uses the file WindowsUpdate.log.
>
> Windows Update FAQ
> http://v5.windowsupdate.microsoft.co....aspx?ln=en-us
>
> Windows Update Troubleshooter
> http://v5.windowsupdate.microsoft.co...oot.aspx?ln=en
>
> and
>
> Please try the following:
>
> Click Start >> Run >>
> Type the follow command in the Open box.
> "net.exe stop wuauserv" (w/o quotes)
> Press Ok
>
> Repeat the same for the following commands:
>
> regsvr32.exe wuapi.dll
> regsvr32.exe wups.dll
> regsvr32.exe wuaueng.dll
> regsvr32.exe wucltui.dll
> regsvr32.exe msxml3.dll
> net.exe start wuauserv
>
>
> Restart the machine and see if it helps.

Thanks for the reply.

I did as suggested but the Windows Update.log did not update.

I've copied the contents of the (other) Windowsupdate.log from the
start of the instructions to see if it can shed some light.

2004-09-09 09:22:39+0100 956 3c0 Service received connect
notification
2004-09-09 09:23:17+0100 956 620 start delayed initialization of WU
client
2004-09-09 09:23:35+0100 680 1e4 Trying to make out of proc datastore
active
2004-09-09 09:23:42+0100 680 1e4 Out of proc datastore is now active
2004-09-09 09:23:42+0100 956 620 Client Call Recorder finished
delayed initialization
2004-09-09 09:23:43+0100 956 620 Setting AU scheduled install time to
2004-09-09 17:00:00
2004-09-09 09:23:43+0100 956 620 AU finished delayed initialization
2004-09-09 09:23:43+0100 956 620 AU received event of 1
2004-09-09 09:23:44+0100 956 620 WU client succeeds
CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call
id {408ECF3B-DD73-4DF5-9336-8704D8938D13}
2004-09-09 09:23:44+0100 956 638 WU client executing call
{408ECF3B-DD73-4DF5-9336-8704D8938D13} of type Search Call
2004-09-09 09:23:58+0100 956 638 WU client found 0 updates and 10
categories in search
2004-09-09 09:23:58+0100 956 638 WU client finished Searching for
update
2004-09-09 09:23:58+0100 956 638 AU Detection callback: 0 updates
detected
2004-09-09 09:23:58+0100 956 638 Setting AU scheduled install time to
2004-09-09 17:00:00
2004-09-09 09:23:58+0100 956 638 WU client calls back to search call
AutomaticUpdates with code Call complete and error 0
2004-09-09 09:23:58+0100 956 638 WU client completed and deleted call
{408ECF3B-DD73-4DF5-9336-8704D8938D13}

Tks Dave

"Torgeir Bakken \(MVP\)" <Torgeir.Bakken-> wrote in message news:<#>...
> Dave Ranson wrote:
>
> > (Dave Ranson) wrote:
> >> (Dave Ranson) wrote:
> >>
> >>>I'm running XP Pro SP2.
> >>>
> >>>I'm set to install updates automatically but I'm not sure it is doing
> >>>it properly. My Windows Update.log has not been modified since the 13
> >>>Aug: I understand the checks for AU are recorded there. I have
> >>>another file called WindowsUpdate.log which was created on 14 Aug and
> >>>seems to record the checks there but in a different format; for
> >>>instance it does not record an error or success like the
> >>>aforementioned log.
> >>>
> >>>I manually downloaded SP2 last week because I thought the automatic
> >>>feature was not working.
> >>>
> >>>I was wondering whether I should have these 2 logs and what their
> >>>functions were? I don't understand why the first log stopped on 13
> >>>Aug when it was getting modified every 1 or 2 days.
> >>>
> >>>Is there a Windows Update FAQ/Troubleshooting guide available for XP?
> >>
> >>OK folks, any advice out there?
> >
> > Anybody kind enough to answer my questions?
> >
> > The 'Windows Update.log' file has still not been modified since 13 Aug 04.
> Hi
>
> As you have WinXP SP2, you are using WU v5, and it does not use the file
> 'Windows Update.log' (that was for WU v4). v5 uses the file WindowsUpdate.log.
>
> Windows Update FAQ
> http://v5.windowsupdate.microsoft.co....aspx?ln=en-us
>
> Windows Update Troubleshooter
> http://v5.windowsupdate.microsoft.co...oot.aspx?ln=en
>
> and
>
> Please try the following:
>
> Click Start >> Run >>
> Type the follow command in the Open box.
> "net.exe stop wuauserv" (w/o quotes)
> Press Ok
>
> Repeat the same for the following commands:
>
> regsvr32.exe wuapi.dll
> regsvr32.exe wups.dll
> regsvr32.exe wuaueng.dll
> regsvr32.exe wucltui.dll
> regsvr32.exe msxml3.dll
> net.exe start wuauserv
>
>
> Restart the machine and see if it helps.


Actually, this is complete record of (other) Windowsupdate.log
recorded from commencing your instructions. I cut some of it out on
the other posting.

2004-09-09 09:15:38+0100 956 3c0 Service received
SERVICE_CONTROL_STOP control
2004-09-09 09:15:38+0100 956 618 Exiting Service Main
2004-09-09 09:15:40+0100 2096 af8 Trying to make out of proc datastore
active
2004-09-09 09:15:40+0100 2096 af8 Out of proc datastore is now active
2004-09-09 09:15:40+0100 2096 af8 Out of proc datastore is shutting
down
2004-09-09 09:15:40+0100 956 618 WUAUENG ServiceMain exits. Exit code
is 0x240001
2004-09-09 09:15:42+0100 2096 af8 Out of proc datastore is now
inactive
2004-09-09 09:20:13+0100 792 b24 ChangeServiceConfig for wuauserv
succeeded
2004-09-09 09:20:56+0100 956 7dc Service Main starts
2004-09-09 09:20:56+0100 956 7dc Using BatchFlushAge = 20346.
2004-09-09 09:20:56+0100 956 7dc Using SamplingValue = 22.
2004-09-09 09:20:56+0100 956 7dc Successfully loaded event namespace
dictionary.
2004-09-09 09:20:56+0100 956 7dc Successfully loaded client event
namespace descriptor.
2004-09-09 09:20:56+0100 956 7dc Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
2004-09-09 09:20:56+0100 956 7dc Successfully initialized NT event
logger.
2004-09-09 09:20:56+0100 956 7dc Successfully initialized event
uploader 0.
2004-09-09 09:20:56+0100 956 7dc Successfully initialized event
uploader 1.
2004-09-09 09:20:56+0100 956 7dc WU client with version 5.4.3790.2182
successfully initialized
2004-09-09 09:20:56+0100 956 7dc Service status is now
SERVICE_RUNNING
2004-09-09 09:21:07+0100 236 258 WUCheckForUpdatesAtShutdown failed,
hr=8024A000
2004-09-09 09:21:12+0100 956 3c0 Service received logoff notification
2004-09-09 09:21:20+0100 1448 b98 Trying to make out of proc datastore
active
2004-09-09 09:21:21+0100 1448 b98 Out of proc datastore is now active
2004-09-09 09:21:21+0100 956 610 Client Call Recorder finished
delayed initialization
2004-09-09 09:21:21+0100 956 610 Setting AU scheduled install time to
2004-09-09 17:00:00
2004-09-09 09:21:21+0100 956 610 AU finished delayed initialization
2004-09-09 09:21:21+0100 956 7dc AU received event of 1
2004-09-09 09:21:21+0100 956 7dc WU client succeeds
CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call
id {DFE232F4-EFF4-4633-8E50-B7217C1B4A3C}
2004-09-09 09:21:21+0100 956 610 AU Restart required....
2004-09-09 09:21:21+0100 956 7dc AU received event of 1
2004-09-09 09:21:21+0100 956 d74 WU client executing call
{DFE232F4-EFF4-4633-8E50-B7217C1B4A3C} of type Search Call
2004-09-09 09:21:21+0100 956 7dc ISusInternal API
CClientCallRecorder:isconnectCall succeeds
2004-09-09 09:21:21+0100 956 7dc AU is paused, not initializing any
handlers
2004-09-09 09:21:22+0100 956 d74 WU client found 0 updates and 10
categories in search
2004-09-09 09:21:22+0100 956 d74 WU client finished Searching for
update
2004-09-09 09:21:22+0100 956 d74 WU client fails to call back to
search call AutomaticUpdates with error 0x8024000c
2004-09-09 09:21:22+0100 956 d74 WU client completed and deleted call
{DFE232F4-EFF4-4633-8E50-B7217C1B4A3C}
2004-09-09 09:21:25+0100 956 3c0 Service received
SERVICE_CONTROL_SHUTDOWN control
2004-09-09 09:21:25+0100 956 7dc Exiting Service Main
2004-09-09 09:21:25+0100 1448 b98 Out of proc datastore is shutting
down
2004-09-09 09:21:25+0100 956 7dc WUAUENG ServiceMain exits. Exit code
is 0x240001
2004-09-09 09:21:27+0100 1448 b98 Out of proc datastore is now
inactive
2004-09-09 09:22:32+0100 956 620 Service Main starts
2004-09-09 09:22:32+0100 956 620 Using BatchFlushAge = 20346.
2004-09-09 09:22:32+0100 956 620 Using SamplingValue = 22.
2004-09-09 09:22:32+0100 956 620 Successfully loaded event namespace
dictionary.
2004-09-09 09:22:32+0100 956 620 Successfully loaded client event
namespace descriptor.
2004-09-09 09:22:32+0100 956 620 Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
2004-09-09 09:22:32+0100 956 620 Successfully initialized NT event
logger.
2004-09-09 09:22:32+0100 956 620 Successfully initialized event
uploader 0.
2004-09-09 09:22:32+0100 956 620 Successfully initialized event
uploader 1.
2004-09-09 09:22:32+0100 956 620 WU client with version 5.4.3790.2182
successfully initialized
2004-09-09 09:22:32+0100 956 620 Service status is now
SERVICE_RUNNING
2004-09-09 09:22:39+0100 956 3c0 Service received logon notification
2004-09-09 09:22:39+0100 956 3c0 Service received connect
notification
2004-09-09 09:23:17+0100 956 620 start delayed initialization of WU
client
2004-09-09 09:23:35+0100 680 1e4 Trying to make out of proc datastore
active
2004-09-09 09:23:42+0100 680 1e4 Out of proc datastore is now active
2004-09-09 09:23:42+0100 956 620 Client Call Recorder finished
delayed initialization
2004-09-09 09:23:43+0100 956 620 Setting AU scheduled install time to
2004-09-09 17:00:00
2004-09-09 09:23:43+0100 956 620 AU finished delayed initialization
2004-09-09 09:23:43+0100 956 620 AU received event of 1
2004-09-09 09:23:44+0100 956 620 WU client succeeds
CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call
id {408ECF3B-DD73-4DF5-9336-8704D8938D13}
2004-09-09 09:23:44+0100 956 638 WU client executing call
{408ECF3B-DD73-4DF5-9336-8704D8938D13} of type Search Call
2004-09-09 09:23:58+0100 956 638 WU client found 0 updates and 10
categories in search
2004-09-09 09:23:58+0100 956 638 WU client finished Searching for
update
2004-09-09 09:23:58+0100 956 638 AU Detection callback: 0 updates
detected
2004-09-09 09:23:58+0100 956 638 Setting AU scheduled install time to
2004-09-09 17:00:00
2004-09-09 09:23:58+0100 956 638 WU client calls back to search call
AutomaticUpdates with code Call complete and error 0
2004-09-09 09:23:58+0100 956 638 WU client completed and deleted call
{408ECF3B-DD73-4DF5-9336-8704D8938D13}
2004-09-09 09:28:58+0100 680 1e4 Out of proc datastore is shutting
down
2004-09-09 09:28:59+0100 680 1e4 Out of proc datastore is now
inactive

Still no change with the other log.

Tks for your help so far.

Dave

Dave Ranson wrote:

> Actually, this is complete record of (other) Windowsupdate.log
> recorded from commencing your instructions. I cut some of it out on
> the other posting.
>
> (snip)
> 2004-09-09 09:20:56+0100 956 7dc WU client with version 5.4.3790.2182
> successfully initialized
> 2004-09-09 09:20:56+0100 956 7dc Service status is now
> SERVICE_RUNNING
> 2004-09-09 09:21:07+0100 236 258 WUCheckForUpdatesAtShutdown failed,
> hr=8024A000
Hi

Only "failure" I see is 8024A000, and a search for that one doesn't
come up with anything, so I would think that it is not critical.

I start to think that your Automatic Updates might work fine.

Note that unless .Net Framework is installed on the SP2 computer, no
critical updates is relevant for SP2 so far, this could explain
why you are not offered any updates.



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

> Hi
>
> Only "failure" I see is 8024A000, and a search for that one doesn't
> come up with anything, so I would think that it is not critical.
>
> I start to think that your Automatic Updates might work fine.
>
> Note that unless .Net Framework is installed on the SP2 computer, no
> critical updates is relevant for SP2 so far, this could explain
> why you are not offered any updates.

Thanks for your help.

I suspect it is not working like it should as I noticed this Windows
Update.log was not updating like it normally does, every day or so. I
knew SP2 was available to download but it (Automatic Updates) did not
alert me to the fact; consequently, I did it manually.

I guess I'll find out for sure when other downloads are available?

Would it be worth deleting those two logs in the hope they are both
re-created?

Thanks Dave

Dave Ranson wrote:

>>Hi
>>
>>Only "failure" I see is 8024A000, and a search for that one doesn't
>>come up with anything, so I would think that it is not critical.
>>
>>I start to think that your Automatic Updates might work fine.
>>
>>Note that unless .Net Framework is installed on the SP2 computer, no
>>critical updates is relevant for SP2 so far, this could explain
>>why you are not offered any updates.
>
>
> Thanks for your help.
>
> I suspect it is not working like it should as I noticed this Windows
> Update.log was not updating like it normally does, every day or so. I
> knew SP2 was available to download but it (Automatic Updates) did not
> alert me to the fact; consequently, I did it manually.
>
> I guess I'll find out for sure when other downloads are available?
>
> Would it be worth deleting those two logs in the hope they are both
> re-created?
Hi

You can safely delete %windir%\WindowsUpdate.log, it will be recreated
when something is to be logged again.

Also, please take a look in the file
%windir%\SoftwareDistribution\ReportingEvents.log for a history
listing (note that the text goes pretty far out to the right).

(%windir% is typically C:\Windows)


Do you have any activity in that log file?



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

"Torgeir Bakken \(MVP\)" <Torgeir.Bakken-> wrote in message news:<#>...
> Dave Ranson wrote:
>
> >>Hi
> >>
> >>Only "failure" I see is 8024A000, and a search for that one doesn't
> >>come up with anything, so I would think that it is not critical.
> >>
> >>I start to think that your Automatic Updates might work fine.
> >>
> >>Note that unless .Net Framework is installed on the SP2 computer, no
> >>critical updates is relevant for SP2 so far, this could explain
> >>why you are not offered any updates.
> >
> >
> > Thanks for your help.
> >
> > I suspect it is not working like it should as I noticed this Windows
> > Update.log was not updating like it normally does, every day or so. I
> > knew SP2 was available to download but it (Automatic Updates) did not
> > alert me to the fact; consequently, I did it manually.
> >
> > I guess I'll find out for sure when other downloads are available?
> >
> > Would it be worth deleting those two logs in the hope they are both
> > re-created?
> Hi
>
> You can safely delete %windir%\WindowsUpdate.log, it will be recreated
> when something is to be logged again.
>
> Also, please take a look in the file
> %windir%\SoftwareDistribution\ReportingEvents.log for a history
> listing (note that the text goes pretty far out to the right).
>
> (%windir% is typically C:\Windows)
>
>
> Do you have any activity in that log file?

Hi

I've deleted the Windows Update.log but it won't let me delete the
Windowsupdate.log, ....is being used by another program etc...

As for the ReportingEvents.log there is a lot of activity there which
I have copied below:-



{F8FCB3A4-8F2E-4AE5-95A3-580CC703148F} 1 2004-08-14
18:47:08+0100 1 183 101 {F6E951E0-D3BC-448B-B74E-B793CAD18135} 0 0 SelfUpdate Success Content
Install Installation Successful: Windows successfully installed the
following update: Automatic Updates
{B6F37B5A-50B8-4090-923A-28677E026053} 2 2004-08-14
18:48:49+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{D646A701-C43B-4961-ABED-F64327D829E2} 3 2004-08-15
14:52:05+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{541DFFAE-17DD-4F5A-BAEF-5104FE145006} 4 2004-08-16
12:29:23+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{9DA2F41E-39FC-4A6E-83A0-F9D380F04320} 6 2004-08-17
09:18:30+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{AB09D034-238F-4C3A-911A-8011C6F93229} 7 2004-08-18
07:17:11+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{FAD5C36D-7B5F-4018-98A0-124EBD480993} 8 2004-08-19
08:23:54+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{6EFD5B28-A146-40F1-95AF-7750F5B93D26} 9 2004-08-19
09:16:13+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{37993334-AC24-4ECD-ABD0-4E2BFD0B2A92} 10 2004-08-19
09:16:59+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{74E04B11-2836-4F05-8AE0-FEC7DE04C7F7} 11 2004-08-20
06:43:46+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{26F2DDB7-F49F-4C9B-A358-98CB786C33DC} 12 2004-08-20
15:45:44+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software
Synchronization Agent has finished detecting items.
{B3BC5BFB-A752-4418-8E56-915DD29DB2E1} 13 2004-08-20
15:46:19+0100 1 185 101 {57E2E5AA-F91B-4EC8-8BFA-85AC7728C393} 100 0 WindowsUpdate Success Content
Install Hide update: user hid one update.
{F32E8012-792B-4419-85F7-5BD9D91C09FE} 14 2004-08-20
15:49:19+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{DFC771B1-784E-4313-80C7-C6FF37DA278F} 15 2004-08-21
15:08:12+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{CDFB66F9-A7D8-48A6-80AF-FD223B7E1061} 16 2004-08-22
10:59:14+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{471ED8CB-C07E-47F7-8313-C4D76CFF7139} 17 2004-08-23
06:44:17+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{D11A24D0-9079-4970-96FE-493E59E1F150} 18 2004-08-24
07:46:54+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{F12023B8-B21F-4DA7-B53F-C31AC10290AD} 19 2004-08-24
08:35:32+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 CDM Success Software
Synchronization Agent has finished detecting items.
{897380E0-6B65-49B5-A162-512BAB8590A6} 20 2004-08-24
14:01:50+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software
Synchronization Agent has finished detecting items.
{F4973848-FAE5-4520-84FA-01124FE68A43} 21 2004-08-24
14:02:19+0100 1 185 101 {AC065938-13C8-4C88-849B-D7B8A8A28839} 100 0 WindowsUpdate Success Content
Install Hide update: user hid one update.
{B47F69D0-859F-4C50-8D51-6EDF2FF05D77} 22 2004-08-24
14:04:17+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software
Synchronization Agent has finished detecting items.
{DA31F36E-223A-4CBC-B457-6153EA75B2A3} 23 2004-08-24
19:35:51+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software
Synchronization Agent has finished detecting items.
{88E03C9D-A6E2-4044-AFDA-B64487F1038A} 24 2004-08-25
07:25:02+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{5D3578B5-8356-41F4-B703-36E94A2BB35B} 25 2004-08-26
06:25:58+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{21B2BE6A-EF77-4A6A-9770-8140F2483C91} 26 2004-08-26
11:35:33+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 WindowsUpdate Success Software
Synchronization Agent has finished detecting items.
{E7FF25ED-867F-482F-9E7E-639EFC43FD70} 28 2004-08-26
12:21:20+0100 1 189 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
Install Installation Ready: The following updates are downloaded and
ready for installation. To install the updates, an administrator
should log on to this computer and Windows will prompt with further
instructions: - Windows XP Service Pack 2
{0AFE94BC-F808-49F4-9746-3CA43B0BAFD3} 27 2004-08-26
12:21:20+0100 1 162 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 107 0 AutomaticUpdates Success Content
Download Download succeeded.
{37079CBC-5544-45F5-8859-C72AEDD6A8EA} 29 2004-08-26
12:21:20+0100 1 162 101 {12497FC5-D5E1-49A8-8E44-26CBA6400DD7} 105 0 AutomaticUpdates Success Content
Download Download succeeded.
{E2CAEBA9-2BF6-4535-979A-F4B1D33A6135} 30 2004-08-26
14:40:16+0100 1 184 101 {7477AF62-8F9B-4F32-9DAF-7AB452E52396} 107 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Windows XP Service Pack 2
{10E1C740-3C27-4FE0-B79E-61DDAF696B9F} 31 2004-08-26
14:40:16+0100 1 184 101 {12497FC5-D5E1-49A8-8E44-26CBA6400DD7} 105 0 WindowsUpdate Success Content
Install Installation successful and restart required for the following
update: Windows XP Service Pack 2
{1050645F-D281-443A-BF42-399141459146} 32 2004-08-27
01:41:01+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{BDF31F20-8555-4AAD-AD00-2B70E3702E42} 33 2004-08-27
22:21:48+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{A4AB7DB9-B2ED-4ADC-9942-EF48C29ADE7A} 34 2004-08-28
19:59:32+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{30B21DFF-94ED-4F64-81C4-184B21A9E8C1} 35 2004-08-29
18:55:09+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{F92A96E9-0954-4A31-9BC9-FD7656F3209E} 36 2004-08-30
18:58:50+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{07BEA04A-9169-4732-9B4F-2D4587FA1D98} 37 2004-08-31
16:47:00+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{882C3306-3455-4351-8B7C-FAB564E7F29C} 38 2004-09-01
13:27:32+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{93029D19-AD06-4FF2-BDE0-EBD79AF58DA9} 39 2004-09-02
08:47:44+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{93420768-4BB4-4F0F-BE74-2894C832CE9F} 40 2004-09-03
08:54:29+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{E3AEE62A-5A5C-4D0B-9DC4-B14B84713405} 41 2004-09-04
08:26:40+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{AE74A808-35E3-4EDD-9472-555222982D9B} 42 2004-09-04
14:48:14+0100 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software
Synchronization Unable to Connect: Windows is unable to connect to the
automatic updates service and therefore cannot download and install
updates according to the set schedule. Windows will continue to try to
establish a connection.
{989D1300-E5D7-4330-A5D7-3BED330BABF5} 43 2004-09-04
17:31:27+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{65FE1B28-5FCB-49AE-BA43-1506DE0D9865} 44 2004-09-05
15:16:48+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{85787E44-FB9F-4322-A77C-99A2D65DC726} 45 2004-09-06
13:41:58+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{D398A9FF-870C-4387-BCBE-BD2717E9F8F1} 46 2004-09-07
16:24:23+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{C077BA72-D48E-4DBC-B3CA-73249754F81C} 47 2004-09-08
13:37:46+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{E90A7EDB-3F88-424F-8C26-3BD0297890F9} 48 2004-09-09
11:09:32+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{EE5B3F3D-60E7-4525-89C2-39DBDB5DFB25} 49 2004-09-10
11:14:28+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{C2C2210D-78C4-41FB-A6A1-7ED16C01E5BA} 50 2004-09-10
11:46:21+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{960164DD-C72B-4F16-B215-99B7F0F2C81E} 51 2004-09-10
11:47:52+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
{DCF2FFA6-5472-478F-B090-F0471F2E2362} 52 2004-09-11
09:40:12+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.

I hope this helps. Thanks for your help so far.

Dave