Windows Update v5 locks up my PC

I have Automatic Updates enabled in my Dell Dimension 4600 running Windows XP
SP1 with all the critical Security patches installed. Since the
release of Windows Update v5, my PC locks up after Windows XP starts up. I
have successfully able to eliminate the lock-ups by disabling the Automatic
Updates Service. I have also reproduced the lock-ups by visiting this site:
http://v5.windowsupdate.microsoft.co....aspx?ln=en-us

I don't want to have Automatic Updates disable permanently. Is there any
known issues with Windows Update v5 and are there any work-arounds/solutions?

Thanks

Some info out of the Windows Update.log

2004-08-19 21:30:12-0500 1848 640 Service Main starts
2004-08-19 21:30:13-0500 1848 640 Using BatchFlushAge = 23571.
2004-08-19 21:30:13-0500 1848 640 Using SamplingValue = 286.
2004-08-19 21:30:13-0500 1848 640 Successfully loaded event namespace
dictionary.
2004-08-19 21:30:15-0500 1848 640 Successfully loaded client event namespace
descriptor.
2004-08-19 21:30:15-0500 1848 640 Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
2004-08-19 21:30:15-0500 1848 640 Successfully initialized NT event logger.
2004-08-19 21:30:15-0500 1848 640 Successfully initialized event uploader 0.
2004-08-19 21:30:16-0500 1848 640 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin for writing.
2004-08-19 21:30:16-0500 1848 640 Successfully initialized event uploader 1.
2004-08-19 21:30:16-0500 1848 640 WU client with version 5.4.3790.2182
successfully initialized
2004-08-19 21:30:16-0500 1848 640 Service status is now SERVICE_RUNNING
2004-08-19 21:30:16-0500 1848 74c Successfully opened event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin for reading.
2004-08-19 21:30:19-0500 1756 718 Trying to make out of proc datastore active
2004-08-19 21:30:22-0500 1756 718 Out of proc datastore is now active
2004-08-19 21:30:23-0500 1848 74c PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-19 21:30:23-0500 1848 74c PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-19 21:30:23-0500 1848 74c PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-19 21:30:23-0500 1848 74c PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-19 21:30:23-0500 1848 74c URL for server is
http://v5stats.windowsupdate.microso...ebService.asmx
2004-08-19 21:30:23-0500 1848 74c Trying to upload 3 events using cached
cookie.
2004-08-19 21:30:27-0500 1848 74c DetectCompressionType returning type 0,
hr=0x1
2004-08-19 21:30:27-0500 1848 74c Successfully uploaded 3 events.
2004-08-19 21:30:27-0500 1848 74c Deleted event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin.
2004-08-19 21:30:41-0500 1848 73c Service received logon notification
2004-08-19 21:30:41-0500 1848 73c Service received connect notification
2004-08-19 21:41:47-0500 1860 f4 Service Main starts
2004-08-19 21:41:49-0500 1860 f4 Using BatchFlushAge = 23571.
2004-08-19 21:41:49-0500 1860 f4 Using SamplingValue = 286.
2004-08-19 21:41:49-0500 1860 f4 Successfully loaded event namespace
dictionary.
2004-08-19 21:41:50-0500 1860 f4 Successfully loaded client event namespace
descriptor.
2004-08-19 21:41:50-0500 1860 f4 Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
2004-08-19 21:41:51-0500 1860 f4 Successfully initialized NT event logger.
2004-08-19 21:41:51-0500 1860 f4 Successfully initialized event uploader 0.
2004-08-19 21:41:51-0500 1860 f4 Successfully initialized event uploader 1.
2004-08-19 21:41:51-0500 1860 f4 WU client with version 5.4.3790.2182
successfully initialized
2004-08-19 21:41:51-0500 1860 f4 Service status is now SERVICE_RUNNING
2004-08-19 21:41:54-0500 1860 748 Service received connect notification
2004-08-19 21:42:36-0500 1860 f4 start delayed initialization of WU client
2004-08-19 21:42:37-0500 1804 724 Trying to make out of proc datastore active
2004-08-19 21:42:38-0500 1804 724 Out of proc datastore is now active
2004-08-19 21:42:38-0500 1860 f4 Client Call Recorder finished delayed
initialization
2004-08-19 21:42:38-0500 1860 f4 Setting next AU detection timeout to
2004-08-20 02:42:38
2004-08-19 21:42:38-0500 1860 f4 AU finished delayed initialization
2004-08-19 21:42:38-0500 1860 f4 AU received event of 1
2004-08-19 21:42:38-0500 1860 758 WU client executing call
{10403822-FCBD-4C1A-BEC5-9692375015E2} of type Search Call
2004-08-19 21:42:38-0500 1860 f4 WU client succeeds
CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id
{10403822-FCBD-4C1A-BEC5-9692375015E2}
2004-08-19 21:42:38-0500 1860 758 Checking for different Redirector at:
http://download.windowsupdate.com/ms...ir/wuredir.cab
2004-08-19 21:42:52-0500 1860 758 Successfully refreshed Redirector cab.
2004-08-19 21:42:52-0500 1860 f4 AU received event of 1
2004-08-19 21:42:52-0500 1860 f4 Successfully launched client for directive 4
2004-08-19 21:42:55-0500 1860 758 Loading inf file
C:\WINDOWS\SoftwareDistribution\SelfUpdate\wusetup .inf
2004-08-19 21:42:55-0500 1860 758 Section name: cdm: Index: 0
2004-08-19 21:42:55-0500 1860 758 Section name: iuengine: Index: 1
2004-08-19 21:42:55-0500 1860 758 Section name: wuapi: Index: 2
2004-08-19 21:42:55-0500 1860 758 Section name: wuauclt: Index: 3
2004-08-19 21:42:55-0500 1860 758 Section name: wuauclt1: Index: 4
2004-08-19 21:42:55-0500 1860 758 Section name: wuaucpl: Index: 5
2004-08-19 21:42:55-0500 1860 758 Section name: wuaueng_SelfUpdate: Index: 6
2004-08-19 21:42:55-0500 1860 758 Section name: wuaueng1: Index: 7
2004-08-19 21:42:55-0500 1860 758 Section name: wucltui: Index: 8
2004-08-19 21:42:55-0500 1860 758 Section name: wups: Index: 9
2004-08-19 21:42:55-0500 1860 758 Section name: wuweb_SelfUpdate: Index: 10
2004-08-19 21:42:55-0500 1860 758 Section name: winhttp: Index: 11
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\cdm.dll is: 5,5,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\cdm.dll:
Target version: 5.5.3790.2182 Required: 5.5.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\iuengine.dll is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\iuengine.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wuapi.dll is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wuapi.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wuauclt.exe is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wuauclt.exe:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wuauclt1.exe is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wuauclt1.exe:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wuaucpl.cpl is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wuaucpl.cpl:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wuaueng.dll is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wuaueng.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wuaueng1.dll is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wuaueng1.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wucltui.dll is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wucltui.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wups.dll is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wups.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:55-0500 1860 758 Required Version for binary
C:\WINDOWS\System32\wuweb.dll is: 5,4,3790,2182
2004-08-19 21:42:55-0500 1860 758 Binary: C:\WINDOWS\System32\wuweb.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-08-19 21:42:56-0500 1860 758 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-19 21:42:56-0500 1860 758 PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-19 21:43:02-0500 1860 758 Add header for accept-encoding: xpress
succeeded
2004-08-19 21:43:03-0500 1860 758 DetectCompressionType returning type 1,
hr=0x0
2004-08-19 21:43:03-0500 1860 758 Add header for accept-encoding: xpress
succeeded
2004-08-19 21:43:06-0500 1860 758 DetectCompressionType returning type 1,
hr=0x0
2004-08-19 21:43:06-0500 1860 758 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-19 21:43:06-0500 1860 758 PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-19 21:43:06-0500 1860 758 Add header for accept-encoding: xpress
succeeded
2004-08-19 21:43:06-0500 1860 758 DetectCompressionType returning type 1,
hr=0x0
2004-08-19 21:43:07-0500 1860 758 WU client add update
{7477AF62-8F9B-4F32-9DAF-7AB452E52396}.106 to search result
2004-08-19 21:43:07-0500 1860 758 WU client found 1 updates and 10
categories in search
2004-08-19 21:43:07-0500 1860 758 OS Version = 5.1.2600.1.0.66304
2004-08-19 21:43:08-0500 1860 758 Computer Brand = Dell Computer Corporation
2004-08-19 21:43:08-0500 1860 758 Computer Model = Dimension 4600i

2004-08-19 21:43:08-0500 1860 758 Bios Revision = A09
2004-08-19 21:43:08-0500 1860 758 Bios Name = Phoenix ROM BIOS PLUS Version
1.10 A09
2004-08-19 21:43:08-0500 1860 758 Bios Release Date = 2004-02-20T00:00:00
2004-08-19 21:43:08-0500 1860 758 Locale ID = 1033
2004-08-19 21:43:08-0500 1860 758 ClientVersion: iuengine.dll = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wuapi.dll = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wuauclt.exe = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wuauclt1.exe = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wuaucpl.cpl = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wuaueng.dll = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wuaueng1.dll = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wuauserv.dll = 5.4.3630.1106
2004-08-19 21:43:08-0500 1860 758 ClientVersion: wucltui.dll = 5.4.3790.2182
2004-08-19 21:43:08-0500 1860 758 WU client finished Searching for update
2004-08-19 21:43:08-0500 1860 758 AU Detection callback: 1 updates detected
2004-08-19 21:43:08-0500 1860 758 Setting next AU detection timeout to
2004-08-20 22:08:42
2004-08-19 21:43:08-0500 1860 758 WU client calls back to search call
AutomaticUpdates with code Call complete and error 0
2004-08-19 21:43:08-0500 1860 758 WU client completed and deleted call
{10403822-FCBD-4C1A-BEC5-9692375015E2}
2004-08-19 21:43:13-0500 1860 758 REPORT EVENT:
{5681F19D-2DBB-454C-81C5-1D67B6A42784} 11 2004-08-19
21:43:07-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
2004-08-19 21:43:13-0500 1860 758 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{E3370C 12-9A59-4CAB-A59A-D1C20594C438}.bin for writing.
2004-08-19 21:43:13-0500 1860 758 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin for writing.
2004-08-19 21:48:08-0500 1804 724 Out of proc datastore is shutting down
2004-08-19 21:48:09-0500 1804 724 Out of proc datastore is now inactive
2004-08-19 22:38:05-0500 1860 748 Service received SERVICE_CONTROL_STOP
control
2004-08-19 22:38:05-0500 1860 f4 Exiting Service Main
2004-08-19 22:38:05-0500 1100 1fc Failed to show client UI, directive=4,
hr=80010108
2004-08-19 22:38:05-0500 236 874 Trying to make out of proc datastore active
2004-08-19 22:38:06-0500 236 874 Out of proc datastore is now active
2004-08-19 22:38:06-0500 236 874 Out of proc datastore is shutting down
2004-08-19 22:38:06-0500 1860 f4 WUAUENG ServiceMain exits. Exit code is
0x240001
2004-08-19 22:38:07-0500 236 874 Out of proc datastore is now inactive

See this recent thread here: http://snipurl.com/8k8y
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH-VSOP

Are You Ready for WinXP SP2?
http://support.microsoft.com/default...r=windowsxpsp2

What You Should Know About Spyware
http://www.microsoft.com/athome/secu...ssoftware.mspx

AumHa Forums
http://forum.aumha.org

boricua68 wrote:
> I have Automatic Updates enabled in my Dell Dimension 4600 running
> Windows XP SP1 with all the critical Security patches installed. Since the
> release of Windows Update v5, my PC locks up after Windows XP starts up. I
> have successfully able to eliminate the lock-ups by disabling the
> Automatic Updates Service. I have also reproduced the lock-ups by
> visiting this site:
> http://v5.windowsupdate.microsoft.co....aspx?ln=en-us
>
> I don't want to have Automatic Updates disable permanently. Is there any
> known issues with Windows Update v5 and are there any
> work-arounds/solutions?
>
> Thanks

Thanks PA Bear... I selected "Automatically detect settings" and it seems to
help. I gotta do some other testing to make sure it has completely fix it but
it is a start.

Thanks again!!

"PA Bear" wrote:

> See this recent thread here: http://snipurl.com/8k8y
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE/OE), AH-VSOP
>
> Are You Ready for WinXP SP2?
> http://support.microsoft.com/default...r=windowsxpsp2
>
> What You Should Know About Spyware
> http://www.microsoft.com/athome/secu...ssoftware.mspx
>
> AumHa Forums
> http://forum.aumha.org
>
> boricua68 wrote:
> > I have Automatic Updates enabled in my Dell Dimension 4600 running
> > Windows XP SP1 with all the critical Security patches installed. Since the
> > release of Windows Update v5, my PC locks up after Windows XP starts up. I
> > have successfully able to eliminate the lock-ups by disabling the
> > Automatic Updates Service. I have also reproduced the lock-ups by
> > visiting this site:
> > http://v5.windowsupdate.microsoft.co....aspx?ln=en-us
> >
> > I don't want to have Automatic Updates disable permanently. Is there any
> > known issues with Windows Update v5 and are there any
> > work-arounds/solutions?
> >
> > Thanks
>
>

YW.

boricua68 wrote:
> Thanks PA Bear... I selected "Automatically detect settings" and it seems
> to help. I gotta do some other testing to make sure it has completely fix
> it but it is a start.
>
> Thanks again!!
>
> "PA Bear" wrote:
>
> > See this recent thread here: http://snipurl.com/8k8y
> > --
> > ~Robear Dyer (PA Bear)
> > MS MVP-Windows (IE/OE), AH-VSOP
> >
> > Are You Ready for WinXP SP2?
> > http://support.microsoft.com/default...r=windowsxpsp2
> >
> > What You Should Know About Spyware
> > http://www.microsoft.com/athome/secu...ssoftware.mspx
> >
> > AumHa Forums
> > http://forum.aumha.org
> >
> > boricua68 wrote:
> > > I have Automatic Updates enabled in my Dell Dimension 4600 running
> > > Windows XP SP1 with all the critical Security patches installed.
> > > Since the release of Windows Update v5, my PC locks up after Windows
> > > XP starts up. I have successfully able to eliminate the lock-ups by
> > > disabling the Automatic Updates Service. I have also reproduced the
> > > lock-ups by visiting this site:
> > > http://v5.windowsupdate.microsoft.co....aspx?ln=en-us
> > >
> > > I don't want to have Automatic Updates disable permanently. Is there
> > > any known issues with Windows Update v5 and are there any
> > > work-arounds/solutions?
> > >
> > > Thanks

Selecting this option below did not fixed the problem during Windows XP
start-up. The PC locked-up same as before. This is crazy...

2004-08-22 19:06:37-0500 1864 178 Service Main starts
2004-08-22 19:06:40-0500 1864 178 Using BatchFlushAge = 23571.
2004-08-22 19:06:40-0500 1864 178 Using SamplingValue = 286.
2004-08-22 19:06:40-0500 1864 178 Successfully loaded event namespace
dictionary.
2004-08-22 19:06:41-0500 1864 178 Successfully loaded client event namespace
descriptor.
2004-08-22 19:06:41-0500 1864 178 Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
2004-08-22 19:06:41-0500 1864 178 Successfully initialized NT event logger.
2004-08-22 19:06:41-0500 1864 178 Successfully initialized event uploader 0.
2004-08-22 19:06:41-0500 1864 178 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin for writing.
2004-08-22 19:06:41-0500 1864 178 Successfully initialized event uploader 1.
2004-08-22 19:06:42-0500 1864 178 WU client with version 5.4.3790.2182
successfully initialized
2004-08-22 19:06:42-0500 1864 178 Service status is now SERVICE_RUNNING
2004-08-22 19:06:42-0500 1864 768 Successfully opened event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin for reading.
2004-08-22 19:06:44-0500 1668 628 Trying to make out of proc datastore active
2004-08-22 19:06:53-0500 1668 628 Out of proc datastore is now active
2004-08-22 19:06:53-0500 1864 768 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-22 19:06:53-0500 1864 74c Service received connect notification
2004-08-22 19:06:54-0500 1864 768 PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-22 19:06:54-0500 1864 768 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-22 19:06:54-0500 1864 768 PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-22 19:06:54-0500 1864 768 URL for server is
http://v5stats.windowsupdate.microso...ebService.asmx
2004-08-22 19:06:54-0500 1864 768 Trying to upload 3 events using cached
cookie.
2004-08-22 19:06:57-0500 1864 768 DetectCompressionType returning type 0,
hr=0x1
2004-08-22 19:06:57-0500 1864 768 Successfully uploaded 3 events.
2004-08-22 19:06:57-0500 1864 768 Deleted event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin.

Hmm... it seems this finaly fixed it.

http://v5.windowsupdate.microsoft.co...cleid=16&ln=en

PA Bear, thanks for the link to the WU Troubleshooter in one of your other
posts.

"boricua68" wrote:

> Selecting this option below did not fixed the problem during Windows XP
> start-up. The PC locked-up same as before. This is crazy...
>
> 2004-08-22 19:06:37-0500 1864 178 Service Main starts
> 2004-08-22 19:06:40-0500 1864 178 Using BatchFlushAge = 23571.
> 2004-08-22 19:06:40-0500 1864 178 Using SamplingValue = 286.
> 2004-08-22 19:06:40-0500 1864 178 Successfully loaded event namespace
> dictionary.
> 2004-08-22 19:06:41-0500 1864 178 Successfully loaded client event namespace
> descriptor.
> 2004-08-22 19:06:41-0500 1864 178 Successfully initialized local event
> logger. Events will be logged at
> C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
> 2004-08-22 19:06:41-0500 1864 178 Successfully initialized NT event logger.
> 2004-08-22 19:06:41-0500 1864 178 Successfully initialized event uploader 0.
> 2004-08-22 19:06:41-0500 1864 178 Reopened existing event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin for writing.
> 2004-08-22 19:06:41-0500 1864 178 Successfully initialized event uploader 1.
> 2004-08-22 19:06:42-0500 1864 178 WU client with version 5.4.3790.2182
> successfully initialized
> 2004-08-22 19:06:42-0500 1864 178 Service status is now SERVICE_RUNNING
> 2004-08-22 19:06:42-0500 1864 768 Successfully opened event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin for reading.
> 2004-08-22 19:06:44-0500 1668 628 Trying to make out of proc datastore active
> 2004-08-22 19:06:53-0500 1668 628 Out of proc datastore is now active
> 2004-08-22 19:06:53-0500 1864 768 PT: Using serverID
> {9482F4B4-E343-43B6-B170-9A65BC822C77}
> 2004-08-22 19:06:53-0500 1864 74c Service received connect notification
> 2004-08-22 19:06:54-0500 1864 768 PT: Using server URL
> https://v5.windowsupdate.microsoft.c...ce/client.asmx
> 2004-08-22 19:06:54-0500 1864 768 PT: Using serverID
> {9482F4B4-E343-43B6-B170-9A65BC822C77}
> 2004-08-22 19:06:54-0500 1864 768 PT: Using server URL
> https://v5.windowsupdate.microsoft.c...ce/client.asmx
> 2004-08-22 19:06:54-0500 1864 768 URL for server is
> http://v5stats.windowsupdate.microso...ebService.asmx
> 2004-08-22 19:06:54-0500 1864 768 Trying to upload 3 events using cached
> cookie.
> 2004-08-22 19:06:57-0500 1864 768 DetectCompressionType returning type 0,
> hr=0x1
> 2004-08-22 19:06:57-0500 1864 768 Successfully uploaded 3 events.
> 2004-08-22 19:06:57-0500 1864 768 Deleted event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin.

I for one would like to know how you got that Javascript pop-up to show
content! All links in V5 Troubleshooter show no content for me and others.
--
~PA Bear

boricua68 wrote:
> Hmm... it seems this finaly fixed it.
>
> http://v5.windowsupdate.microsoft.co...cleid=16&ln=en
>
> PA Bear, thanks for the link to the WU Troubleshooter in one of your other
> posts.
>
> "boricua68" wrote:
>
> > Selecting this option below did not fixed the problem during Windows XP
> > start-up. The PC locked-up same as before. This is crazy...
> >
> > 2004-08-22 19:06:37-0500 1864 178 Service Main starts
> > 2004-08-22 19:06:40-0500 1864 178 Using BatchFlushAge = 23571.
> > 2004-08-22 19:06:40-0500 1864 178 Using SamplingValue = 286.
> > 2004-08-22 19:06:40-0500 1864 178 Successfully loaded event namespace
> > dictionary.
> > 2004-08-22 19:06:41-0500 1864 178 Successfully loaded client event
> > namespace
> > descriptor.
> > 2004-08-22 19:06:41-0500 1864 178 Successfully initialized local event
> > logger. Events will be logged at
> > C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
> > 2004-08-22 19:06:41-0500 1864 178 Successfully initialized NT event
> > logger. 2004-08-22 19:06:41-0500 1864 178 Successfully initialized
> > event uploader 0. 2004-08-22 19:06:41-0500 1864 178 Reopened existing
> > event cache file at
> > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin
> > for writing. 2004-08-22 19:06:41-0500 1864 178 Successfully initialized
> > event uploader 1. 2004-08-22 19:06:42-0500 1864 178 WU client with
> > version 5.4.3790.2182
> > successfully initialized
> > 2004-08-22 19:06:42-0500 1864 178 Service status is now SERVICE_RUNNING
> > 2004-08-22 19:06:42-0500 1864 768 Successfully opened event cache file
> > at
> > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin
> > for reading. 2004-08-22 19:06:44-0500 1668 628 Trying to make out of
> > proc datastore active 2004-08-22 19:06:53-0500 1668 628 Out of proc
> > datastore is now active 2004-08-22 19:06:53-0500 1864 768 PT: Using
> > serverID {9482F4B4-E343-43B6-B170-9A65BC822C77} 2004-08-22
> > 19:06:53-0500 1864 74c Service received connect notification 2004-08-22
> > 19:06:54-0500 1864 768 PT: Using server URL
> > https://v5.windowsupdate.microsoft.c...ce/client.asmx
> > 2004-08-22 19:06:54-0500 1864 768 PT: Using serverID
> > {9482F4B4-E343-43B6-B170-9A65BC822C77} 2004-08-22 19:06:54-0500 1864
> > 768 PT: Using server URL
> > https://v5.windowsupdate.microsoft.c...ce/client.asmx
> > 2004-08-22 19:06:54-0500 1864 768 URL for server is
> > http://v5stats.windowsupdate.microso...ebService.asmx
> > 2004-08-22 19:06:54-0500 1864 768 Trying to upload 3 events using
> > cached
> > cookie.
> > 2004-08-22 19:06:57-0500 1864 768 DetectCompressionType returning type
> > 0,
> > hr=0x1
> > 2004-08-22 19:06:57-0500 1864 768 Successfully uploaded 3 events.
> > 2004-08-22 19:06:57-0500 1864 768 Deleted event cache file at
> > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin.

Haa,haa... good question!!! I don't know but it shows up ok. I have IE 6.0 @
default medium security level. I also have a Java Plug-In (JRE 2 v1.4.2) from
SUN Microsystems installed. Maybe that is the reason why...

"PA Bear" wrote:

> I for one would like to know how you got that Javascript pop-up to show
> content! All links in V5 Troubleshooter show no content for me and others.
> --
> ~PA Bear
>
> boricua68 wrote:
> > Hmm... it seems this finaly fixed it.
> >
> > http://v5.windowsupdate.microsoft.co...cleid=16&ln=en
> >
> > PA Bear, thanks for the link to the WU Troubleshooter in one of your other
> > posts.
> >
> > "boricua68" wrote:
> >
> > > Selecting this option below did not fixed the problem during Windows XP
> > > start-up. The PC locked-up same as before. This is crazy...
> > >
> > > 2004-08-22 19:06:37-0500 1864 178 Service Main starts
> > > 2004-08-22 19:06:40-0500 1864 178 Using BatchFlushAge = 23571.
> > > 2004-08-22 19:06:40-0500 1864 178 Using SamplingValue = 286.
> > > 2004-08-22 19:06:40-0500 1864 178 Successfully loaded event namespace
> > > dictionary.
> > > 2004-08-22 19:06:41-0500 1864 178 Successfully loaded client event
> > > namespace
> > > descriptor.
> > > 2004-08-22 19:06:41-0500 1864 178 Successfully initialized local event
> > > logger. Events will be logged at
> > > C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
> > > 2004-08-22 19:06:41-0500 1864 178 Successfully initialized NT event
> > > logger. 2004-08-22 19:06:41-0500 1864 178 Successfully initialized
> > > event uploader 0. 2004-08-22 19:06:41-0500 1864 178 Reopened existing
> > > event cache file at
> > > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin
> > > for writing. 2004-08-22 19:06:41-0500 1864 178 Successfully initialized
> > > event uploader 1. 2004-08-22 19:06:42-0500 1864 178 WU client with
> > > version 5.4.3790.2182
> > > successfully initialized
> > > 2004-08-22 19:06:42-0500 1864 178 Service status is now SERVICE_RUNNING
> > > 2004-08-22 19:06:42-0500 1864 768 Successfully opened event cache file
> > > at
> > > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin
> > > for reading. 2004-08-22 19:06:44-0500 1668 628 Trying to make out of
> > > proc datastore active 2004-08-22 19:06:53-0500 1668 628 Out of proc
> > > datastore is now active 2004-08-22 19:06:53-0500 1864 768 PT: Using
> > > serverID {9482F4B4-E343-43B6-B170-9A65BC822C77} 2004-08-22
> > > 19:06:53-0500 1864 74c Service received connect notification 2004-08-22
> > > 19:06:54-0500 1864 768 PT: Using server URL
> > > https://v5.windowsupdate.microsoft.c...ce/client.asmx
> > > 2004-08-22 19:06:54-0500 1864 768 PT: Using serverID
> > > {9482F4B4-E343-43B6-B170-9A65BC822C77} 2004-08-22 19:06:54-0500 1864
> > > 768 PT: Using server URL
> > > https://v5.windowsupdate.microsoft.c...ce/client.asmx
> > > 2004-08-22 19:06:54-0500 1864 768 URL for server is
> > > http://v5stats.windowsupdate.microso...ebService.asmx
> > > 2004-08-22 19:06:54-0500 1864 768 Trying to upload 3 events using
> > > cached
> > > cookie.
> > > 2004-08-22 19:06:57-0500 1864 768 DetectCompressionType returning type
> > > 0,
> > > hr=0x1
> > > 2004-08-22 19:06:57-0500 1864 768 Successfully uploaded 3 events.
> > > 2004-08-22 19:06:57-0500 1864 768 Deleted event cache file at
> > > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin.
>
>

I have the page in Trusted Sites, low, and have JRE 2 v1.4.2 and nothing
loads in any javascript pop-up.
--
~PA Bear

boricua68 wrote:
> Haa,haa... good question!!! I don't know but it shows up ok. I have IE
> 6.0 @ default medium security level. I also have a Java Plug-In (JRE 2
> v1.4.2) from SUN Microsystems installed. Maybe that is the reason why...
>
> "PA Bear" wrote:
>
> > I for one would like to know how you got that Javascript pop-up to show
> > content! All links in V5 Troubleshooter show no content for me and
> > others. --
> > ~PA Bear
> >
> > boricua68 wrote:
> > > Hmm... it seems this finaly fixed it.
> > >
> > > http://v5.windowsupdate.microsoft.co...cleid=16&ln=en
> > >
> > > PA Bear, thanks for the link to the WU Troubleshooter in one of your
> > > other posts.
> > >
> > > "boricua68" wrote:
> > >
> > > > Selecting this option below did not fixed the problem during
> > > > Windows XP start-up. The PC locked-up same as before. This is
> > > > crazy...
> > > >
> > > > 2004-08-22 19:06:37-0500 1864 178 Service Main starts
> > > > 2004-08-22 19:06:40-0500 1864 178 Using BatchFlushAge = 23571.
> > > > 2004-08-22 19:06:40-0500 1864 178 Using SamplingValue = 286.
> > > > 2004-08-22 19:06:40-0500 1864 178 Successfully loaded event
> > > > namespace dictionary.
> > > > 2004-08-22 19:06:41-0500 1864 178 Successfully loaded client event
> > > > namespace
> > > > descriptor.
> > > > 2004-08-22 19:06:41-0500 1864 178 Successfully initialized local
> > > > event logger. Events will be logged at
> > > > C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
> > > > 2004-08-22 19:06:41-0500 1864 178 Successfully initialized NT event
> > > > logger. 2004-08-22 19:06:41-0500 1864 178 Successfully initialized
> > > > event uploader 0. 2004-08-22 19:06:41-0500 1864 178 Reopened
> > > > existing event cache file at
> > > > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin
> > > > for writing. 2004-08-22 19:06:41-0500 1864 178 Successfully
> > > > initialized event uploader 1. 2004-08-22 19:06:42-0500 1864 178 WU
> > > > client with version 5.4.3790.2182
> > > > successfully initialized
> > > > 2004-08-22 19:06:42-0500 1864 178 Service status is now
> > > > SERVICE_RUNNING 2004-08-22 19:06:42-0500 1864 768 Successfully
> > > > opened event cache file at
> > > > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin
> > > > for reading. 2004-08-22 19:06:44-0500 1668 628 Trying to make out of
> > > > proc datastore active 2004-08-22 19:06:53-0500 1668 628 Out of proc
> > > > datastore is now active 2004-08-22 19:06:53-0500 1864 768 PT: Using
> > > > serverID {9482F4B4-E343-43B6-B170-9A65BC822C77} 2004-08-22
> > > > 19:06:53-0500 1864 74c Service received connect notification
> > > > 2004-08-22 19:06:54-0500 1864 768 PT: Using server URL
> > > > https://v5.windowsupdate.microsoft.c...ce/client.asmx
> > > > 2004-08-22 19:06:54-0500 1864 768 PT: Using serverID
> > > > {9482F4B4-E343-43B6-B170-9A65BC822C77} 2004-08-22 19:06:54-0500 1864
> > > > 768 PT: Using server URL
> > > > https://v5.windowsupdate.microsoft.c...ce/client.asmx
> > > > 2004-08-22 19:06:54-0500 1864 768 URL for server is
> > > > http://v5stats.windowsupdate.microso...ebService.asmx
> > > > 2004-08-22 19:06:54-0500 1864 768 Trying to upload 3 events using
> > > > cached
> > > > cookie.
> > > > 2004-08-22 19:06:57-0500 1864 768 DetectCompressionType returning
> > > > type 0,
> > > > hr=0x1
> > > > 2004-08-22 19:06:57-0500 1864 768 Successfully uploaded 3 events.
> > > > 2004-08-22 19:06:57-0500 1864 768 Deleted event cache file at
> > > > C:\WINDOWS\SoftwareDistribution\EventCache\{58AE9A D3-5E36-44CC-905D-7FDFEC9B1D30}.bin.