The laswt 30 lines are:
2005-02-13 17:57:24-0600 888 54c WU client add update
{66216830-74FA-4A91-BEA8-212E6A5A43DD}.101 to search result
2005-02-13 17:57:24-0600 888 54c WU client add update
{BB758AAA-8024-44D0-8434-73CEFE8CA80B}.100 to search result
2005-02-13 17:57:24-0600 888 54c WU client add update
{8A1423ED-CE96-42DC-84B3-C51CEC59EA87}.100 to search result
2005-02-13 17:57:24-0600 888 54c WU client found 3 updates and 11
categories in search
2005-02-13 17:57:24-0600 888 54c OS Version = 5.1.2600.2.0.66304
2005-02-13 17:57:24-0600 888 54c Computer Brand = eMachines, Inc.
2005-02-13 17:57:24-0600 888 54c Computer Model = Imperial
2005-02-13 17:57:24-0600 888 54c Bios Revision = 6.00
2005-02-13 17:57:24-0600 888 54c Bios Name = Revision 0.90
2005-02-13 17:57:24-0600 888 54c Bios Release Date = 2003-10-02T00:00:00
2005-02-13 17:57:24-0600 888 54c Locale ID = 1033
2005-02-13 17:57:24-0600 888 54c ClientVersion: iuengine.dll = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c ClientVersion: wuapi.dll = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c ClientVersion: wuauclt.exe = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c ClientVersion: wuauclt1.exe = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c ClientVersion: wuaucpl.cpl = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c ClientVersion: wuaueng.dll = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c ClientVersion: wuaueng1.dll = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c ClientVersion: wuauserv.dll = 5.4.3790.2180
2005-02-13 17:57:24-0600 888 54c ClientVersion: wucltui.dll = 5.4.3790.2182
2005-02-13 17:57:24-0600 888 54c WU client finished Searching for update
2005-02-13 17:57:24-0600 888 54c AU Detection callback: 3 updates detected
2005-02-13 17:57:24-0600 888 54c Setting next AU detection timeout to
2005-02-14 20:15:16
2005-02-13 17:57:24-0600 888 54c Setting AU scheduled install time to
2005-02-14 16:00:00
2005-02-13 17:57:24-0600 888 54c WU client calls back to search call
AutomaticUpdates with code Call complete and error 0
2005-02-13 17:57:24-0600 888 54c WU client completed and deleted call
{AFB02D59-0C3B-4A6A-A2BE-4E6A812F3AC1}
2005-02-13 17:57:29-0600 888 54c REPORT EVENT:
{2678EC30-B826-42FC-A33A-ADC12BFC7B6C} 313 2005-02-13
17:57:24-0600 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
2005-02-13 17:57:29-0600 888 54c Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{38A0F1 87-E184-49DB-93FB-A30460CC5246}.bin for writing.
2005-02-13 18:02:24-0600 2976 ba4 Out of proc datastore is shutting down
2005-02-13 18:02:26-0600 2976 ba4 Out of proc datastore is now inactive
I have no idea what I'm looking at ? But thank you for taking the time to
help with this problem Torgeir. Charlie
"Torgeir Bakken (MVP)" wrote:
> Chaslie wrote:
>
> > When trying to use windows Update I always get the
> > following error after having run the "Express Install"
> > scan:
> > "Windows update has encountered an error and
> > cannot display the requested page.You may find the
> > following resources helpful in resolving your problem."
> > The following options for finding a fix appear:
> > For self help options:
> > *Windows Update Response Center
> > *Windows Update Troubleshooter
> > *Windows Update Newsgroups
> >
> > I have Windows XP with both the SP1 & SP2 patches
> > installed. I have looked at the options it gives to fix
> > the problem but haven't been able to resolve the
> > problem. Any help would be greatly appreciated.
> Hi
>
> Look for any specific error messages or error numbers in
> windowsupdate.log.
>
> From Start/Run run this exact command:
>
> notepad %windir%\windowsupdate.log
>
> See if you can find any clues and/or error massages/numbers there and
> post e.g. the last 30 lines of that log here.
>
>
>
>
> --
> 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
>
Similar Threads
Linear Mode
