Automatic Updates Error Boxes

Last night I went over to Windows Update to check for new updates and while I
was there I got a Window with the following.

Automatic Updates

Automatic Updates has encountered a problem and needs to close. We are sorry
for the inconvenience.

I sent the error report to Microsoft and logged off.
Since then I keep getting the same Window popping up all the time. I cannot
get into Automatic Updates (tried 3 way) without the computer freezing up.
The windows keep popping up. What is going on?

"MichaelM",

Please check that your services are running, and then we'll see if we cannot
narrow it down. In other words, where the error occurs when you try to
start Automatic Updates service:

1. Click Start
2. Click Run
3. type services.msc
4. Click OK or type the <Enter> key
5. In the Services window, look for Background Intelligent Transfer Service
6. Double-click on Background Intelligent Transfer Service
7. In the middle of the Properties window, make sure the Startup type is set
to "Manual" or "Automatic"
8. Just below the Startup type, verify that the Service status is set to
"Started"
9. If it is not, click the Start button, and wait for the service to start.
Verify this starts.
10. Repeat steps 5-9 with the Automatic Updates service, but make sure this
is set to "Automatic".
11. Close the properties window
12. Close the Services window

Assuming you hit any errors during this procedure, open the event viewer and
reply back to this newsgroup with any entries from the system log that
correlate to your failure. We are especially interested in any error codes.

If this all succeeds, try to go to Windows Update and install just one
update, by unchecking all of the others. Let us know if you succeed or not.
If not, send us the error and last part of the log. Here's how:

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.
13. Also tell us what update you were installing.

Sincerely,

Pat Walters [MSFT]

"MichaelM" <> wrote in message
news:904172EB-A31D-41FD-B54A-...
> Last night I went over to Windows Update to check for new updates and
while I
> was there I got a Window with the following.
>
> Automatic Updates
>
> Automatic Updates has encountered a problem and needs to close. We are
sorry
> for the inconvenience.
>
> I sent the error report to Microsoft and logged off.
> Since then I keep getting the same Window popping up all the time. I
cannot
> get into Automatic Updates (tried 3 way) without the computer freezing up.
> The windows keep popping up. What is going on?

Pat,
I made sure Automatic Updates was running in Services. In fact I have turned
it off (stopped it) since it was annoying to have the error windows being
generated ever 30 minutes or so. I did try to log back on to Windows Update
web page with Automatic Updates active. I received an error 0x80248011 from
the Windows Update web page.

In the mean time I have done the following.
Scanned for Viruses
Scanned Disk for errors several times with Disk Doctor and ChkDsk
Deleted all Temporary Internet Files

I have also got the last lines of the WindowsUpdate.log in this message. The
Log just keeps repeating the same errors over and over when Automatic Updates
is active.

Also, the error being repeated over and over is as follows:
Error Signature
szAppName wuauctl.exe
szAppVer 5.4.3790.2182
sz ModName esent.dll
szModVer 5.1.26002180

Here are the log lines. Hope this info can help you dig me out of my hole.
Looks like I have a file corrupt, but which one I don't know. Do have a
complete backup of disk with Norton Ghost from last week if needed.

Thanks,
2005-02-09 18:08:33-0500 1240 1d0 AU received event of 1
2005-02-09 18:08:33-0500 1240 1d0 Setting next AU detection timeout to
2005-02-09 23:08:33
2005-02-09 18:08:33-0500 1016 d04 Trying to make out of proc datastore active
2005-02-09 18:08:38-0500 1240 1d0 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-02-09 18:08:38-0500 2112 d38 Trying to make out of proc datastore active
2005-02-09 18:08:42-0500 1240 1d0 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-02-09 18:08:42-0500 3044 b4c Trying to make out of proc datastore active
2005-02-09 18:08:46-0500 1240 1d0 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-02-09 18:08:46-0500 176 a44 Trying to make out of proc datastore active
2005-02-09 18:08:50-0500 1240 1d0 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-02-09 18:08:50-0500 2064 5e4 Trying to make out of proc datastore active
2005-02-09 18:08:54-0500 1240 1d0 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-02-09 18:08:54-0500 3368 8e0 Trying to make out of proc datastore active
2005-02-09 18:08:58-0500 1240 1d0 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-02-09 18:08:58-0500 1240 1d0 Failed to get session from datastore:
80248011
2005-02-09 18:08:58-0500 1240 1d0 Failed to Unserialize from data store:
80248011
2005-02-09 18:08:58-0500 1240 1d0 AU Restart required....
2005-02-09 18:09:45-0500 1240 1d0 Cleared the proxy cache.
2005-02-09 18:13:01-0500 1240 4dc Service received logoff notification
2005-02-09 18:13:01-0500 1240 1d0 AU received event of 3
2005-02-09 18:13:01-0500 1240 1d0 Received an event which can not be
processed at this time
2005-02-09 18:13:02-0500 1240 4dc Service received connect notification
2005-02-09 18:13:02-0500 1240 1d0 AU received event of 3
2005-02-09 18:13:02-0500 1240 1d0 Received an event which can not be
processed at this time
2005-02-09 18:13:10-0500 1240 4dc Service received disconnect notification
2005-02-09 18:13:10-0500 1240 1d0 AU received event of 3
2005-02-09 18:13:10-0500 1240 1d0 Received an event which can not be
processed at this time
2005-02-09 18:13:10-0500 1240 4dc Service received connect notification
2005-02-09 18:13:10-0500 1240 1d0 AU received event of 3
2005-02-09 18:13:10-0500 1240 1d0 Received an event which can not be
processed at this time

Mike


"Pat Walters [MSFT]" wrote:

> "MichaelM",
>
> Please check that your services are running, and then we'll see if we cannot
> narrow it down. In other words, where the error occurs when you try to
> start Automatic Updates service:
>
> 1. Click Start
> 2. Click Run
> 3. type services.msc
> 4. Click OK or type the <Enter> key
> 5. In the Services window, look for Background Intelligent Transfer Service
> 6. Double-click on Background Intelligent Transfer Service
> 7. In the middle of the Properties window, make sure the Startup type is set
> to "Manual" or "Automatic"
> 8. Just below the Startup type, verify that the Service status is set to
> "Started"
> 9. If it is not, click the Start button, and wait for the service to start.
> Verify this starts.
> 10. Repeat steps 5-9 with the Automatic Updates service, but make sure this
> is set to "Automatic".
> 11. Close the properties window
> 12. Close the Services window
>
> Assuming you hit any errors during this procedure, open the event viewer and
> reply back to this newsgroup with any entries from the system log that
> correlate to your failure. We are especially interested in any error codes.
>
> If this all succeeds, try to go to Windows Update and install just one
> update, by unchecking all of the others. Let us know if you succeed or not.
> If not, send us the error and last part of the log. Here's how:
>
> 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.
> 13. Also tell us what update you were installing.
>
> Sincerely,
>
> Pat Walters [MSFT]
>
> "MichaelM" <> wrote in message
> news:904172EB-A31D-41FD-B54A-...
> > Last night I went over to Windows Update to check for new updates and
> while I
> > was there I got a Window with the following.
> >
> > Automatic Updates
> >
> > Automatic Updates has encountered a problem and needs to close. We are
> sorry
> > for the inconvenience.
> >
> > I sent the error report to Microsoft and logged off.
> > Since then I keep getting the same Window popping up all the time. I
> cannot
> > get into Automatic Updates (tried 3 way) without the computer freezing up.
> > The windows keep popping up. What is going on?
>
>
>

I guess I will reply to myself on this matter. I got in touch with Joey Wu in
Microsoft Windows Update Support. The following were suggested to try. Step 2
WORKS !!! Please note I was receiving error 0x80248011 at Windows update web
page. Thank you Joey.

Step 1: Reset Internet Explorer settings, and disable third-party Internet
Explorer plug-ins.
==========
1. Click Start, Run, type: inetcpl.cpl and press Enter.
2. Select the General tab, and in the Temporary Internet files window, click
Delete Cookies, and click OK.
3. In the same tab click Delete Flies, check the "Delete all offline
contents" box and click OK.
4. Click "Clear History" and click Yes.

5. Click the Advanced tab.
6. Click the "Use HTTP 1.1" check box.
7. Click the "Use HTTP 1.1 through proxy connections" check box.
8. Click OK to confirm the changes.

Then, we can open Internet Explorer, and click Tools-> Windows Update to
access the Windows Update site again. If the issue persists, we can refer to
the next suggestion.

Step 2: Rename the temporary folder of Windows Update.
===============
This behavior may occur if the temporary folder of Windows Update has been
corrupted. We can refer to the following steps to rename this folder. Please
be assured the folder will be created again when we visit the Windows Update
site again.

1. Click Start, click Run, and type in "cmd" (without quotations) and press
Enter. Please run the following command in the opened window to start the
Automatic Updates service.

Type in "net stop WuAuServ" (without quotations) and press Enter.

Note: Please ensure the Automatic Updates service is stopped before we try
to rename the folder.

2. Click Start, click Run, and type in "%windir%" (without quotations) and
press Enter.
3. In the opened folder, rename the folder SoftwareDistribution to SDold.
4. Click Start, click Run, and type in "cmd" (without quotations) and press
Enter. Please run the command "net start WuAuServ" in the opened window to
restart the service Automatic Updates.

If the issue persists after we successfully rename the SoftwareDistribution
folder, some background programs are likely causing the issue. We can prepare
a Clean Boot environment, and then rename the SoftwareDistribution folder
again to get the issue resolved. To prepare a Clean Boot environment, w
e can refer to the following steps:

Mike


"MichaelM" wrote:

> Last night I went over to Windows Update to check for new updates and while I
> was there I got a Window with the following.
>
> Automatic Updates
>
> Automatic Updates has encountered a problem and needs to close. We are sorry
> for the inconvenience.
>
> I sent the error report to Microsoft and logged off.
> Since then I keep getting the same Window popping up all the time. I cannot
> get into Automatic Updates (tried 3 way) without the computer freezing up.
> The windows keep popping up. What is going on?

Thanks to Michael and Joey - step 2 cured my same problem also - cheers guys!

I am having problems with 0x80248011 persisting. I have tried all the steps
explained in this thread but no success.

The instructions below say that if all else fails "we can prepare a Clean
Boot Environment" but then doesn't go on to say what this is or how to do it.

Does anyone have any more suggestions about how to get over this problem?

Below are the relevant windowsupdate.log entries

Cheers.

Graham B.

2005-05-23 08:37:58+1000 1028 154 Service Main starts
2005-05-23 08:37:59+1000 1028 154 Using BatchFlushAge = 31204.
2005-05-23 08:37:59+1000 1028 154 Using SamplingValue = 608.
2005-05-23 08:37:59+1000 1028 154 Successfully loaded event namespace
dictionary.
2005-05-23 08:37:59+1000 1028 154 Successfully loaded client event namespace
descriptor.
2005-05-23 08:37:59+1000 1028 154 Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
2005-05-23 08:37:59+1000 1028 154 Successfully initialized NT event logger.
2005-05-23 08:37:59+1000 1028 154 Successfully initialized event uploader 0.
2005-05-23 08:37:59+1000 1028 154 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{96F4A3 E2-F47D-4CC2-BCB8-D7ED290F37CF}.bin for writing.
2005-05-23 08:37:59+1000 1028 154 Successfully initialized event uploader 1.
2005-05-23 08:37:59+1000 1028 154 WU client with version 5.4.3790.2182
successfully initialized
2005-05-23 08:37:59+1000 1028 154 Service status is now SERVICE_RUNNING
2005-05-23 08:37:59+1000 1028 1b4 Successfully opened event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{96F4A3 E2-F47D-4CC2-BCB8-D7ED290F37CF}.bin for reading.
2005-05-23 08:37:59+1000 580 248 Trying to make out of proc datastore active
2005-05-23 08:38:01+1000 1028 1b4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:01+1000 1580 630 Trying to make out of proc datastore active
2005-05-23 08:38:01+1000 1028 1b4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:02+1000 1636 668 Trying to make out of proc datastore active
2005-05-23 08:38:02+1000 1028 1b4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:02+1000 1028 1b4 Failed to obtain cached cookie with hr =
80248011.
2005-05-23 08:38:02+1000 1692 6a0 Trying to make out of proc datastore active
2005-05-23 08:38:03+1000 1028 1b4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:03+1000 1748 524 Trying to make out of proc datastore active
2005-05-23 08:38:04+1000 1028 1b4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:04+1000 1976 7bc Trying to make out of proc datastore active
2005-05-23 08:38:04+1000 1028 1b4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:04+1000 1028 1b4 Failed to obtain cached url with hr =
80248011.
2005-05-23 08:38:04+1000 1028 1b4 Failed to upload events with hr = 80248011.
2005-05-23 08:38:44+1000 1028 154 start delayed initialization of WU client
2005-05-23 08:38:44+1000 1020 418 Trying to make out of proc datastore active
2005-05-23 08:38:44+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:45+1000 1332 538 Trying to make out of proc datastore active
2005-05-23 08:38:45+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:45+1000 1436 5a0 Trying to make out of proc datastore active
2005-05-23 08:38:46+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:46+1000 1028 154 WU client failed to load persisted
download calls with error 0x80248011
2005-05-23 08:38:46+1000 1028 154 Client Call Recorder finished delayed
initialization
2005-05-23 08:38:46+1000 1528 5fc Trying to make out of proc datastore active
2005-05-23 08:38:47+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:47+1000 1588 638 Trying to make out of proc datastore active
2005-05-23 08:38:47+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:47+1000 1648 674 Trying to make out of proc datastore active
2005-05-23 08:38:48+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:48+1000 1028 154 DM: GetSession failed with 0x80248011.
2005-05-23 08:38:48+1000 1028 154 Setting next AU detection timeout to
2005-05-22 22:38:48
2005-05-23 08:38:48+1000 220 e0 Trying to make out of proc datastore active
2005-05-23 08:38:49+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:49+1000 1736 6c4 Trying to make out of proc datastore active
2005-05-23 08:38:49+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:50+1000 1960 7a4 Trying to make out of proc datastore active
2005-05-23 08:38:50+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:50+1000 1976 fc Trying to make out of proc datastore active
2005-05-23 08:38:51+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:51+1000 1920 7e8 Trying to make out of proc datastore active
2005-05-23 08:38:52+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:52+1000 1072 3dc Trying to make out of proc datastore active
2005-05-23 08:38:52+1000 1028 154 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:38:52+1000 1028 154 Failed to get session from datastore:
80248011
2005-05-23 08:38:52+1000 1028 154 Failed to Unserialize from data store:
80248011
2005-05-23 08:38:52+1000 1028 154 InitAUComponents Failed, will restart AU
in 30 mins: 80248011
2005-05-23 08:38:52+1000 1028 154 AU Restart required....
2005-05-23 08:40:39+1000 1028 408 Service received connect notification
2005-05-23 08:40:39+1000 1028 154 AU received event of 3
2005-05-23 08:40:39+1000 1028 154 Received an event which can not be
processed at this time
2005-05-23 08:40:44+1000 1028 408 Service received logon notification
2005-05-23 08:40:44+1000 1028 154 AU received event of 3
2005-05-23 08:40:44+1000 1028 154 Received an event which can not be
processed at this time
2005-05-23 08:44:48+1000 1688 8d8 Trying to make out of proc datastore active
2005-05-23 08:44:48+1000 1028 4e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:44:49+1000 2200 89c Trying to make out of proc datastore active
2005-05-23 08:44:49+1000 1028 4e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:44:49+1000 760 5fc Trying to make out of proc datastore active
2005-05-23 08:44:50+1000 1028 4e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:44:50+1000 1028 4e4 WU client fails
CClientCallRecorder::EnumerateService with error 0x80248011
2005-05-23 08:44:50+1000 3604 e18 ISusInternal::EnumerateService failed,
hr=80248011
2005-05-23 08:44:55+1000 2400 964 Trying to make out of proc datastore active
2005-05-23 08:44:56+1000 1028 4e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:44:56+1000 2476 9b0 Trying to make out of proc datastore active
2005-05-23 08:44:57+1000 1028 4e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:44:57+1000 2528 9e4 Trying to make out of proc datastore active
2005-05-23 08:44:57+1000 1028 4e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:44:57+1000 1028 4e4 WU client fails
CClientCallRecorder::EnumerateService with error 0x80248011
2005-05-23 08:44:57+1000 3604 e18 ISusInternal::EnumerateService failed,
hr=80248011
2005-05-23 08:45:04+1000 3604 e18 Checking for different Redirector at:
http://download.windowsupdate.com/ms...ir/wuredir.cab
2005-05-23 08:45:05+1000 3604 e18 WinInet: Server file is not newer.
Skipping download.
2005-05-23 08:45:05+1000 3604 e18 Successfully refreshed Redirector cab.
2005-05-23 08:45:05+1000 3604 e18 WinInet: Server file is not newer.
Skipping download.
2005-05-23 08:45:06+1000 3604 e18 WinInet: Download speed is 19976 bytes/sec
2005-05-23 08:45:06+1000 3604 e18 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...en/wusetup.cab to
file C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.c ab
2005-05-23 08:45:06+1000 3604 e18 Loading inf file
C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.i nf
2005-05-23 08:45:06+1000 3604 e18 Section name: cdm: Index: 0
2005-05-23 08:45:06+1000 3604 e18 Section name: iuengine: Index: 1
2005-05-23 08:45:06+1000 3604 e18 Section name: wuapi: Index: 2
2005-05-23 08:45:06+1000 3604 e18 Section name: wuauclt: Index: 3
2005-05-23 08:45:06+1000 3604 e18 Section name: wuauclt1: Index: 4
2005-05-23 08:45:06+1000 3604 e18 Section name: wuaucpl: Index: 5
2005-05-23 08:45:06+1000 3604 e18 Section name: wuaueng_WebSetup: Index: 6
2005-05-23 08:45:06+1000 3604 e18 Section name: wuaueng1: Index: 7
2005-05-23 08:45:06+1000 3604 e18 Section name: wuauserv_WebSetup: Index: 8
2005-05-23 08:45:06+1000 3604 e18 Section name: wucltui: Index: 9
2005-05-23 08:45:06+1000 3604 e18 Section name: wups: Index: 10
2005-05-23 08:45:06+1000 3604 e18 Section name: winhttp: Index: 11
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\cdm.dll is: 5,5,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\cdm.dll:
Target version: 5.5.3790.2182 Required: 5.5.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\iuengine.dll is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\iuengine.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wuapi.dll is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuapi.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wuauclt.exe is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuauclt.exe:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wuauclt1.exe is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuauclt1.exe:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wuaucpl.cpl is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuaucpl.cpl:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wuaueng.dll is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuaueng.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wuaueng1.dll is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuaueng1.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wucltui.dll is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wucltui.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
C:\WINDOWS\system32\wups.dll is: 5,4,3790,2182
2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wups.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2005-05-23 08:45:12+1000 1028 4d4 WU client succeeds
CClientCallRecorder::BeginFindUpdates from WindowsUpdate with call id
{4319C872-59A2-420F-AACA-14C11843ADCC}
2005-05-23 08:45:12+1000 1028 5e4 WU client executing call
{4319C872-59A2-420F-AACA-14C11843ADCC} of type Search Call
2005-05-23 08:45:12+1000 2832 b14 Trying to make out of proc datastore active
2005-05-23 08:45:13+1000 1028 5e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:45:13+1000 2904 b5c Trying to make out of proc datastore active
2005-05-23 08:45:14+1000 1028 5e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:45:14+1000 2980 ba8 Trying to make out of proc datastore active
2005-05-23 08:45:14+1000 1028 5e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:45:14+1000 1028 5e4 OS Version = 5.1.2600.2.0.65792
2005-05-23 08:45:15+1000 1028 5e4 Computer Brand = ASUS
2005-05-23 08:45:15+1000 1028 5e4 Computer Model = A7V8X-MX SE
2005-05-23 08:45:15+1000 1028 5e4 Bios Revision = ASUS A7V8X-MX SE ACPI BIOS
Revision 1004
2005-05-23 08:45:15+1000 1028 5e4 Bios Name = Phoenix - Award BIOS v6.00PG
2005-05-23 08:45:15+1000 1028 5e4 Bios Release Date = 2004-07-01T00:00:00
2005-05-23 08:45:15+1000 1028 5e4 Locale ID = 1033
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: iuengine.dll = 5.4.3790.2182
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuapi.dll = 5.4.3790.2182
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuauclt.exe = 5.4.3790.2182
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuauclt1.exe = 5.4.3790.2182
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuaucpl.cpl = 5.4.3790.2182
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuaueng.dll = 5.4.3790.2182
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuaueng1.dll = 5.4.3790.2182
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuauserv.dll = 5.4.3790.2180
2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wucltui.dll = 5.4.3790.2182
2005-05-23 08:45:16+1000 3132 c40 Trying to make out of proc datastore active
2005-05-23 08:45:16+1000 1028 5e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:45:16+1000 3208 c8c Trying to make out of proc datastore active
2005-05-23 08:45:17+1000 1028 5e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:45:17+1000 3244 cb0 Trying to make out of proc datastore active
2005-05-23 08:45:18+1000 1028 5e4 DS: Out of proc datastore process exited
with error 0xc0000005 before signalling ready event.
2005-05-23 08:45:18+1000 1028 5e4 WU client failed Searching for update with
error 0x80248011
2005-05-23 08:45:18+1000 1028 5e4 WU client calls back to search call
WindowsUpdate with code Call failed and error 0x80248011
2005-05-23 08:45:18+1000 1028 5e4 WU client completed and deleted call
{4319C872-59A2-420F-AACA-14C11843ADCC}
2005-05-23 08:45:18+1000 3604 e18 Operation completed due to earlier error.
(hr=80248011)
2005-05-23 08:45:18+1000 3604 e18 Unable to complete asynchronous search
successfully. (hr=80248011)
2005-05-23 08:45:20+1000 1028 5e4 REPORT EVENT:
{50C57CD7-4526-4725-BC4C-ECC957505EC5} 445 2005-05-23
08:45:14+1000 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248011 WindowsUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80248011
2005-05-23 08:45:20+1000 1028 5e4 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{AF1B91 94-F9F0-4C9A-8C76-735277FAFD1C}.bin for writing.
2005-05-23 08:45:20+1000 1028 5e4 Created new event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{DD0374 47-EB76-472C-B9D2-068AFBE87EEF}.bin for writing.


Cheers.

"MichaelM" wrote:

> I guess I will reply to myself on this matter. I got in touch with Joey Wu in
> Microsoft Windows Update Support. The following were suggested to try. Step 2
> WORKS !!! Please note I was receiving error 0x80248011 at Windows update web
> page. Thank you Joey.
>
> Step 1: Reset Internet Explorer settings, and disable third-party Internet
> Explorer plug-ins.
> ==========
> 1. Click Start, Run, type: inetcpl.cpl and press Enter.
> 2. Select the General tab, and in the Temporary Internet files window, click
> Delete Cookies, and click OK.
> 3. In the same tab click Delete Flies, check the "Delete all offline
> contents" box and click OK.
> 4. Click "Clear History" and click Yes.
>
> 5. Click the Advanced tab.
> 6. Click the "Use HTTP 1.1" check box.
> 7. Click the "Use HTTP 1.1 through proxy connections" check box.
> 8. Click OK to confirm the changes.
>
> Then, we can open Internet Explorer, and click Tools-> Windows Update to
> access the Windows Update site again. If the issue persists, we can refer to
> the next suggestion.
>
> Step 2: Rename the temporary folder of Windows Update.
> ===============
> This behavior may occur if the temporary folder of Windows Update has been
> corrupted. We can refer to the following steps to rename this folder. Please
> be assured the folder will be created again when we visit the Windows Update
> site again.
>
> 1. Click Start, click Run, and type in "cmd" (without quotations) and press
> Enter. Please run the following command in the opened window to start the
> Automatic Updates service.
>
> Type in "net stop WuAuServ" (without quotations) and press Enter.
>
> Note: Please ensure the Automatic Updates service is stopped before we try
> to rename the folder.
>
> 2. Click Start, click Run, and type in "%windir%" (without quotations) and
> press Enter.
> 3. In the opened folder, rename the folder SoftwareDistribution to SDold.
> 4. Click Start, click Run, and type in "cmd" (without quotations) and press
> Enter. Please run the command "net start WuAuServ" in the opened window to
> restart the service Automatic Updates.
>
> If the issue persists after we successfully rename the SoftwareDistribution
> folder, some background programs are likely causing the issue. We can prepare
> a Clean Boot environment, and then rename the SoftwareDistribution folder
> again to get the issue resolved. To prepare a Clean Boot environment, w
> e can refer to the following steps:
>
> Mike
>
>
> "MichaelM" wrote:
>
> > Last night I went over to Windows Update to check for new updates and while I
> > was there I got a Window with the following.
> >
> > Automatic Updates
> >
> > Automatic Updates has encountered a problem and needs to close. We are sorry
> > for the inconvenience.
> >
> > I sent the error report to Microsoft and logged off.
> > Since then I keep getting the same Window popping up all the time. I cannot
> > get into Automatic Updates (tried 3 way) without the computer freezing up.
> > The windows keep popping up. What is going on?

> The instructions below say that if all else fails "we can prepare a Clean
> Boot Environment" but then doesn't go on to say what this is or how to do it.

It looks as if that is all that the poster wanted to show you from his
E-mail.

Try a search?

<title>How to perform a clean boot in Windows XP</title>
http://support.microsoft.com/kb/310353

<title>How to perform advanced clean-boot troubleshooting in Windows XP</title>
http://support.microsoft.com/default...b;en-us;316434

(Google web search for
site:microsoft.com intitle:xp intitle:clean intitle:boot
)


BTW your error code is a FAQ so you could also find other suggestions, even with the search filter on the web interface
to newsgroups that you are using.

Courtesy of Taurarian:

http://www.microsoft.com/windowsxp/e...5-ecc96fab9093

(web interface search for
0x80248011 MSFT
- Threads with helpful posts
)


If that still doesn't help avoid your symptom you should consider
the 0xc0000005 error code which is also present in your log.
That is a code which indicates a module is crashing. For that
particular symptom there may be more information in your Event log.


Good luck

Robert Aldwinckle
---


"GrahamB" <> wrote in message news:CE6A9501-FAB4-49FD-A260-...
>I am having problems with 0x80248011 persisting. I have tried all the steps
> explained in this thread but no success.
>
> The instructions below say that if all else fails "we can prepare a Clean
> Boot Environment" but then doesn't go on to say what this is or how to do it.
>
> Does anyone have any more suggestions about how to get over this problem?
>
> Below are the relevant windowsupdate.log entries
>
> Cheers.
>
> Graham B.
>
> 2005-05-23 08:37:58+1000 1028 154 Service Main starts
> 2005-05-23 08:37:59+1000 1028 154 Using BatchFlushAge = 31204.
> 2005-05-23 08:37:59+1000 1028 154 Using SamplingValue = 608.
> 2005-05-23 08:37:59+1000 1028 154 Successfully loaded event namespace
> dictionary.
> 2005-05-23 08:37:59+1000 1028 154 Successfully loaded client event namespace
> descriptor.
> 2005-05-23 08:37:59+1000 1028 154 Successfully initialized local event
> logger. Events will be logged at
> C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
> 2005-05-23 08:37:59+1000 1028 154 Successfully initialized NT event logger.
> 2005-05-23 08:37:59+1000 1028 154 Successfully initialized event uploader 0.
> 2005-05-23 08:37:59+1000 1028 154 Reopened existing event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{96F4A3 E2-F47D-4CC2-BCB8-D7ED290F37CF}.bin for writing.
> 2005-05-23 08:37:59+1000 1028 154 Successfully initialized event uploader 1.
> 2005-05-23 08:37:59+1000 1028 154 WU client with version 5.4.3790.2182
> successfully initialized
> 2005-05-23 08:37:59+1000 1028 154 Service status is now SERVICE_RUNNING
> 2005-05-23 08:37:59+1000 1028 1b4 Successfully opened event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{96F4A3 E2-F47D-4CC2-BCB8-D7ED290F37CF}.bin for reading.
> 2005-05-23 08:37:59+1000 580 248 Trying to make out of proc datastore active
> 2005-05-23 08:38:01+1000 1028 1b4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:01+1000 1580 630 Trying to make out of proc datastore active
> 2005-05-23 08:38:01+1000 1028 1b4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:02+1000 1636 668 Trying to make out of proc datastore active
> 2005-05-23 08:38:02+1000 1028 1b4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:02+1000 1028 1b4 Failed to obtain cached cookie with hr =
> 80248011.
> 2005-05-23 08:38:02+1000 1692 6a0 Trying to make out of proc datastore active
> 2005-05-23 08:38:03+1000 1028 1b4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:03+1000 1748 524 Trying to make out of proc datastore active
> 2005-05-23 08:38:04+1000 1028 1b4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:04+1000 1976 7bc Trying to make out of proc datastore active
> 2005-05-23 08:38:04+1000 1028 1b4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:04+1000 1028 1b4 Failed to obtain cached url with hr =
> 80248011.
> 2005-05-23 08:38:04+1000 1028 1b4 Failed to upload events with hr = 80248011.
> 2005-05-23 08:38:44+1000 1028 154 start delayed initialization of WU client
> 2005-05-23 08:38:44+1000 1020 418 Trying to make out of proc datastore active
> 2005-05-23 08:38:44+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:45+1000 1332 538 Trying to make out of proc datastore active
> 2005-05-23 08:38:45+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:45+1000 1436 5a0 Trying to make out of proc datastore active
> 2005-05-23 08:38:46+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:46+1000 1028 154 WU client failed to load persisted
> download calls with error 0x80248011
> 2005-05-23 08:38:46+1000 1028 154 Client Call Recorder finished delayed
> initialization
> 2005-05-23 08:38:46+1000 1528 5fc Trying to make out of proc datastore active
> 2005-05-23 08:38:47+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:47+1000 1588 638 Trying to make out of proc datastore active
> 2005-05-23 08:38:47+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:47+1000 1648 674 Trying to make out of proc datastore active
> 2005-05-23 08:38:48+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:48+1000 1028 154 DM: GetSession failed with 0x80248011.
> 2005-05-23 08:38:48+1000 1028 154 Setting next AU detection timeout to
> 2005-05-22 22:38:48
> 2005-05-23 08:38:48+1000 220 e0 Trying to make out of proc datastore active
> 2005-05-23 08:38:49+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:49+1000 1736 6c4 Trying to make out of proc datastore active
> 2005-05-23 08:38:49+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:50+1000 1960 7a4 Trying to make out of proc datastore active
> 2005-05-23 08:38:50+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:50+1000 1976 fc Trying to make out of proc datastore active
> 2005-05-23 08:38:51+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:51+1000 1920 7e8 Trying to make out of proc datastore active
> 2005-05-23 08:38:52+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:52+1000 1072 3dc Trying to make out of proc datastore active
> 2005-05-23 08:38:52+1000 1028 154 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:38:52+1000 1028 154 Failed to get session from datastore:
> 80248011
> 2005-05-23 08:38:52+1000 1028 154 Failed to Unserialize from data store:
> 80248011
> 2005-05-23 08:38:52+1000 1028 154 InitAUComponents Failed, will restart AU
> in 30 mins: 80248011
> 2005-05-23 08:38:52+1000 1028 154 AU Restart required....
> 2005-05-23 08:40:39+1000 1028 408 Service received connect notification
> 2005-05-23 08:40:39+1000 1028 154 AU received event of 3
> 2005-05-23 08:40:39+1000 1028 154 Received an event which can not be
> processed at this time
> 2005-05-23 08:40:44+1000 1028 408 Service received logon notification
> 2005-05-23 08:40:44+1000 1028 154 AU received event of 3
> 2005-05-23 08:40:44+1000 1028 154 Received an event which can not be
> processed at this time
> 2005-05-23 08:44:48+1000 1688 8d8 Trying to make out of proc datastore active
> 2005-05-23 08:44:48+1000 1028 4e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:44:49+1000 2200 89c Trying to make out of proc datastore active
> 2005-05-23 08:44:49+1000 1028 4e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:44:49+1000 760 5fc Trying to make out of proc datastore active
> 2005-05-23 08:44:50+1000 1028 4e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:44:50+1000 1028 4e4 WU client fails
> CClientCallRecorder::EnumerateService with error 0x80248011
> 2005-05-23 08:44:50+1000 3604 e18 ISusInternal::EnumerateService failed,
> hr=80248011
> 2005-05-23 08:44:55+1000 2400 964 Trying to make out of proc datastore active
> 2005-05-23 08:44:56+1000 1028 4e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:44:56+1000 2476 9b0 Trying to make out of proc datastore active
> 2005-05-23 08:44:57+1000 1028 4e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:44:57+1000 2528 9e4 Trying to make out of proc datastore active
> 2005-05-23 08:44:57+1000 1028 4e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:44:57+1000 1028 4e4 WU client fails
> CClientCallRecorder::EnumerateService with error 0x80248011
> 2005-05-23 08:44:57+1000 3604 e18 ISusInternal::EnumerateService failed,
> hr=80248011
> 2005-05-23 08:45:04+1000 3604 e18 Checking for different Redirector at:
> http://download.windowsupdate.com/ms...ir/wuredir.cab
> 2005-05-23 08:45:05+1000 3604 e18 WinInet: Server file is not newer.
> Skipping download.
> 2005-05-23 08:45:05+1000 3604 e18 Successfully refreshed Redirector cab.
> 2005-05-23 08:45:05+1000 3604 e18 WinInet: Server file is not newer.
> Skipping download.
> 2005-05-23 08:45:06+1000 3604 e18 WinInet: Download speed is 19976 bytes/sec
> 2005-05-23 08:45:06+1000 3604 e18 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...en/wusetup.cab to
> file C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.c ab
> 2005-05-23 08:45:06+1000 3604 e18 Loading inf file
> C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.i nf
> 2005-05-23 08:45:06+1000 3604 e18 Section name: cdm: Index: 0
> 2005-05-23 08:45:06+1000 3604 e18 Section name: iuengine: Index: 1
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wuapi: Index: 2
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wuauclt: Index: 3
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wuauclt1: Index: 4
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wuaucpl: Index: 5
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wuaueng_WebSetup: Index: 6
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wuaueng1: Index: 7
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wuauserv_WebSetup: Index: 8
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wucltui: Index: 9
> 2005-05-23 08:45:06+1000 3604 e18 Section name: wups: Index: 10
> 2005-05-23 08:45:06+1000 3604 e18 Section name: winhttp: Index: 11
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\cdm.dll is: 5,5,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\cdm.dll:
> Target version: 5.5.3790.2182 Required: 5.5.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\iuengine.dll is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\iuengine.dll:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wuapi.dll is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuapi.dll:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wuauclt.exe is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuauclt.exe:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wuauclt1.exe is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuauclt1.exe:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wuaucpl.cpl is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuaucpl.cpl:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wuaueng.dll is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuaueng.dll:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wuaueng1.dll is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wuaueng1.dll:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wucltui.dll is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wucltui.dll:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:06+1000 3604 e18 Required Version for binary
> C:\WINDOWS\system32\wups.dll is: 5,4,3790,2182
> 2005-05-23 08:45:06+1000 3604 e18 Binary: C:\WINDOWS\system32\wups.dll:
> Target version: 5.4.3790.2182 Required: 5.4.3790.2182
> 2005-05-23 08:45:12+1000 1028 4d4 WU client succeeds
> CClientCallRecorder::BeginFindUpdates from WindowsUpdate with call id
> {4319C872-59A2-420F-AACA-14C11843ADCC}
> 2005-05-23 08:45:12+1000 1028 5e4 WU client executing call
> {4319C872-59A2-420F-AACA-14C11843ADCC} of type Search Call
> 2005-05-23 08:45:12+1000 2832 b14 Trying to make out of proc datastore active
> 2005-05-23 08:45:13+1000 1028 5e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:45:13+1000 2904 b5c Trying to make out of proc datastore active
> 2005-05-23 08:45:14+1000 1028 5e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:45:14+1000 2980 ba8 Trying to make out of proc datastore active
> 2005-05-23 08:45:14+1000 1028 5e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:45:14+1000 1028 5e4 OS Version = 5.1.2600.2.0.65792
> 2005-05-23 08:45:15+1000 1028 5e4 Computer Brand = ASUS
> 2005-05-23 08:45:15+1000 1028 5e4 Computer Model = A7V8X-MX SE
> 2005-05-23 08:45:15+1000 1028 5e4 Bios Revision = ASUS A7V8X-MX SE ACPI BIOS
> Revision 1004
> 2005-05-23 08:45:15+1000 1028 5e4 Bios Name = Phoenix - Award BIOS v6.00PG
> 2005-05-23 08:45:15+1000 1028 5e4 Bios Release Date = 2004-07-01T00:00:00
> 2005-05-23 08:45:15+1000 1028 5e4 Locale ID = 1033
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: iuengine.dll = 5.4.3790.2182
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuapi.dll = 5.4.3790.2182
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuauclt.exe = 5.4.3790.2182
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuauclt1.exe = 5.4.3790.2182
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuaucpl.cpl = 5.4.3790.2182
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuaueng.dll = 5.4.3790.2182
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuaueng1.dll = 5.4.3790.2182
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wuauserv.dll = 5.4.3790.2180
> 2005-05-23 08:45:15+1000 1028 5e4 ClientVersion: wucltui.dll = 5.4.3790.2182
> 2005-05-23 08:45:16+1000 3132 c40 Trying to make out of proc datastore active
> 2005-05-23 08:45:16+1000 1028 5e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:45:16+1000 3208 c8c Trying to make out of proc datastore active
> 2005-05-23 08:45:17+1000 1028 5e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:45:17+1000 3244 cb0 Trying to make out of proc datastore active
> 2005-05-23 08:45:18+1000 1028 5e4 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-05-23 08:45:18+1000 1028 5e4 WU client failed Searching for update with
> error 0x80248011
> 2005-05-23 08:45:18+1000 1028 5e4 WU client calls back to search call
> WindowsUpdate with code Call failed and error 0x80248011
> 2005-05-23 08:45:18+1000 1028 5e4 WU client completed and deleted call
> {4319C872-59A2-420F-AACA-14C11843ADCC}
> 2005-05-23 08:45:18+1000 3604 e18 Operation completed due to earlier error.
> (hr=80248011)
> 2005-05-23 08:45:18+1000 3604 e18 Unable to complete asynchronous search
> successfully. (hr=80248011)
> 2005-05-23 08:45:20+1000 1028 5e4 REPORT EVENT:
> {50C57CD7-4526-4725-BC4C-ECC957505EC5} 445 2005-05-23
> 08:45:14+1000 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248011 WindowsUpdate Failure Software
> Synchronization Error: Agent failed detecting with reason: 0x80248011
> 2005-05-23 08:45:20+1000 1028 5e4 Reopened existing event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{AF1B91 94-F9F0-4C9A-8C76-735277FAFD1C}.bin for writing.
> 2005-05-23 08:45:20+1000 1028 5e4 Created new event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{DD0374 47-EB76-472C-B9D2-068AFBE87EEF}.bin for writing.
>
>
> Cheers.
>
> "MichaelM" wrote:
>
>> I guess I will reply to myself on this matter. I got in touch with Joey Wu in
>> Microsoft Windows Update Support. The following were suggested to try. Step 2
>> WORKS !!! Please note I was receiving error 0x80248011 at Windows update web
>> page. Thank you Joey.
>>
>> Step 1: Reset Internet Explorer settings, and disable third-party Internet
>> Explorer plug-ins.
>> ==========
>> 1. Click Start, Run, type: inetcpl.cpl and press Enter.
>> 2. Select the General tab, and in the Temporary Internet files window, click
>> Delete Cookies, and click OK.
>> 3. In the same tab click Delete Flies, check the "Delete all offline
>> contents" box and click OK.
>> 4. Click "Clear History" and click Yes.
>>
>> 5. Click the Advanced tab.
>> 6. Click the "Use HTTP 1.1" check box.
>> 7. Click the "Use HTTP 1.1 through proxy connections" check box.
>> 8. Click OK to confirm the changes.
>>
>> Then, we can open Internet Explorer, and click Tools-> Windows Update to
>> access the Windows Update site again. If the issue persists, we can refer to
>> the next suggestion.
>>
>> Step 2: Rename the temporary folder of Windows Update.
>> ===============
>> This behavior may occur if the temporary folder of Windows Update has been
>> corrupted. We can refer to the following steps to rename this folder. Please
>> be assured the folder will be created again when we visit the Windows Update
>> site again.
>>
>> 1. Click Start, click Run, and type in "cmd" (without quotations) and press
>> Enter. Please run the following command in the opened window to start the
>> Automatic Updates service.
>>
>> Type in "net stop WuAuServ" (without quotations) and press Enter.
>>
>> Note: Please ensure the Automatic Updates service is stopped before we try
>> to rename the folder.
>>
>> 2. Click Start, click Run, and type in "%windir%" (without quotations) and
>> press Enter.
>> 3. In the opened folder, rename the folder SoftwareDistribution to SDold.
>> 4. Click Start, click Run, and type in "cmd" (without quotations) and press
>> Enter. Please run the command "net start WuAuServ" in the opened window to
>> restart the service Automatic Updates.
>>
>> If the issue persists after we successfully rename the SoftwareDistribution
>> folder, some background programs are likely causing the issue. We can prepare
>> a Clean Boot environment, and then rename the SoftwareDistribution folder
>> again to get the issue resolved. To prepare a Clean Boot environment, w
>> e can refer to the following steps:
>>
>> Mike
>>
>>
>> "MichaelM" wrote:
>>
>> > Last night I went over to Windows Update to check for new updates and while I
>> > was there I got a Window with the following.
>> >
>> > Automatic Updates
>> >
>> > Automatic Updates has encountered a problem and needs to close. We are sorry
>> > for the inconvenience.
>> >
>> > I sent the error report to Microsoft and logged off.
>> > Since then I keep getting the same Window popping up all the time. I cannot
>> > get into Automatic Updates (tried 3 way) without the computer freezing up.
>> > The windows keep popping up. What is going on?

--
7878209


"MichaelM" wrote:

> Pat,
> I made sure Automatic Updates was running in Services. In fact I have turned
> it off (stopped it) since it was annoying to have the error windows being
> generated ever 30 minutes or so. I did try to log back on to Windows Update
> web page with Automatic Updates active. I received an error 0x80248011 from
> the Windows Update web page.
>
> In the mean time I have done the following.
> Scanned for Viruses
> Scanned Disk for errors several times with Disk Doctor and ChkDsk
> Deleted all Temporary Internet Files
>
> I have also got the last lines of the WindowsUpdate.log in this message. The
> Log just keeps repeating the same errors over and over when Automatic Updates
> is active.
>
> Also, the error being repeated over and over is as follows:
> Error Signature
> szAppName wuauctl.exe
> szAppVer 5.4.3790.2182
> sz ModName esent.dll
> szModVer 5.1.26002180
>
> Here are the log lines. Hope this info can help you dig me out of my hole.
> Looks like I have a file corrupt, but which one I don't know. Do have a
> complete backup of disk with Norton Ghost from last week if needed.
>
> Thanks,
> 2005-02-09 18:08:33-0500 1240 1d0 AU received event of 1
> 2005-02-09 18:08:33-0500 1240 1d0 Setting next AU detection timeout to
> 2005-02-09 23:08:33
> 2005-02-09 18:08:33-0500 1016 d04 Trying to make out of proc datastore active
> 2005-02-09 18:08:38-0500 1240 1d0 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-02-09 18:08:38-0500 2112 d38 Trying to make out of proc datastore active
> 2005-02-09 18:08:42-0500 1240 1d0 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-02-09 18:08:42-0500 3044 b4c Trying to make out of proc datastore active
> 2005-02-09 18:08:46-0500 1240 1d0 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-02-09 18:08:46-0500 176 a44 Trying to make out of proc datastore active
> 2005-02-09 18:08:50-0500 1240 1d0 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-02-09 18:08:50-0500 2064 5e4 Trying to make out of proc datastore active
> 2005-02-09 18:08:54-0500 1240 1d0 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-02-09 18:08:54-0500 3368 8e0 Trying to make out of proc datastore active
> 2005-02-09 18:08:58-0500 1240 1d0 DS: Out of proc datastore process exited
> with error 0xc0000005 before signalling ready event.
> 2005-02-09 18:08:58-0500 1240 1d0 Failed to get session from datastore:
> 80248011
> 2005-02-09 18:08:58-0500 1240 1d0 Failed to Unserialize from data store:
> 80248011
> 2005-02-09 18:08:58-0500 1240 1d0 AU Restart required....
> 2005-02-09 18:09:45-0500 1240 1d0 Cleared the proxy cache.
> 2005-02-09 18:13:01-0500 1240 4dc Service received logoff notification
> 2005-02-09 18:13:01-0500 1240 1d0 AU received event of 3
> 2005-02-09 18:13:01-0500 1240 1d0 Received an event which can not be
> processed at this time
> 2005-02-09 18:13:02-0500 1240 4dc Service received connect notification
> 2005-02-09 18:13:02-0500 1240 1d0 AU received event of 3
> 2005-02-09 18:13:02-0500 1240 1d0 Received an event which can not be
> processed at this time
> 2005-02-09 18:13:10-0500 1240 4dc Service received disconnect notification
> 2005-02-09 18:13:10-0500 1240 1d0 AU received event of 3
> 2005-02-09 18:13:10-0500 1240 1d0 Received an event which can not be
> processed at this time
> 2005-02-09 18:13:10-0500 1240 4dc Service received connect notification
> 2005-02-09 18:13:10-0500 1240 1d0 AU received event of 3
> 2005-02-09 18:13:10-0500 1240 1d0 Received an event which can not be
> processed at this time
>
> Mike
>
>
> "Pat Walters [MSFT]" wrote:
>
> > "MichaelM",
> >
> > Please check that your services are running, and then we'll see if we cannot
> > narrow it down. In other words, where the error occurs when you try to
> > start Automatic Updates service:
> >
> > 1. Click Start
> > 2. Click Run
> > 3. type services.msc
> > 4. Click OK or type the <Enter> key
> > 5. In the Services window, look for Background Intelligent Transfer Service
> > 6. Double-click on Background Intelligent Transfer Service
> > 7. In the middle of the Properties window, make sure the Startup type is set
> > to "Manual" or "Automatic"
> > 8. Just below the Startup type, verify that the Service status is set to
> > "Started"
> > 9. If it is not, click the Start button, and wait for the service to start.
> > Verify this starts.
> > 10. Repeat steps 5-9 with the Automatic Updates service, but make sure this
> > is set to "Automatic".
> > 11. Close the properties window
> > 12. Close the Services window
> >
> > Assuming you hit any errors during this procedure, open the event viewer and
> > reply back to this newsgroup with any entries from the system log that
> > correlate to your failure. We are especially interested in any error codes.
> >
> > If this all succeeds, try to go to Windows Update and install just one
> > update, by unchecking all of the others. Let us know if you succeed or not.
> > If not, send us the error and last part of the log. Here's how:
> >
> > 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.
> > 13. Also tell us what update you were installing.
> >
> > Sincerely,
> >
> > Pat Walters [MSFT]
> >
> > "MichaelM" <> wrote in message
> > news:904172EB-A31D-41FD-B54A-...
> > > Last night I went over to Windows Update to check for new updates and
> > while I
> > > was there I got a Window with the following.
> > >
> > > Automatic Updates
> > >
> > > Automatic Updates has encountered a problem and needs to close. We are
> > sorry
> > > for the inconvenience.
> > >
> > > I sent the error report to Microsoft and logged off.
> > > Since then I keep getting the same Window popping up all the time. I
> > cannot
> > > get into Automatic Updates (tried 3 way) without the computer freezing up.
> > > The windows keep popping up. What is going on?
> >
> >
> >

I've got the same exact problem -- with an additional problem -- my computer
locks-up now without warning.
I've checked all my services and the only thing I've got disabled is remote
access.

I researched my WindowsUpdateLog and discovered that Automatic Updates began
having problems back on 27Jan06. That's about when I left; I've been gone a
month so I was not aware through the month of Feb there was a
problem........... Now I'm back and getting annoyed.
No software was loaded by myself, no changes made to the OS, the only
"updates" made to the OS were through the AU onboard system.......... My log
only goes back to 26Jan06, so I have no idea what the last download was from
Microsoft before all the problems began..........

What I DID notice was that wuauclt.exe in the system32\dllcache had been
replaced with a different file than what was in my windowsupdate uninstall
folder -- it had a revision date much higher than - but an actual file date
of 2004, also a different file size.
I replaced it (retaining the suspect file renamed) without any changes....
same error codes and same results.

I copied more than just a few lines from the WindowsUpdateLog -- it's going
to be difficult for anyone to understand otherwise -- now I need a person to
send the copied file to for a better understanding than I can provide.

Pls message me back at


"Pat Walters [MSFT]" wrote:

> "MichaelM",
>
> Please check that your services are running, and then we'll see if we cannot
> narrow it down. In other words, where the error occurs when you try to
> start Automatic Updates service:
>
> 1. Click Start
> 2. Click Run
> 3. type services.msc
> 4. Click OK or type the <Enter> key
> 5. In the Services window, look for Background Intelligent Transfer Service
> 6. Double-click on Background Intelligent Transfer Service
> 7. In the middle of the Properties window, make sure the Startup type is set
> to "Manual" or "Automatic"
> 8. Just below the Startup type, verify that the Service status is set to
> "Started"
> 9. If it is not, click the Start button, and wait for the service to start.
> Verify this starts.
> 10. Repeat steps 5-9 with the Automatic Updates service, but make sure this
> is set to "Automatic".
> 11. Close the properties window
> 12. Close the Services window
>
> Assuming you hit any errors during this procedure, open the event viewer and
> reply back to this newsgroup with any entries from the system log that
> correlate to your failure. We are especially interested in any error codes.
>
> If this all succeeds, try to go to Windows Update and install just one
> update, by unchecking all of the others. Let us know if you succeed or not.
> If not, send us the error and last part of the log. Here's how:
>
> 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.
> 13. Also tell us what update you were installing.
>
> Sincerely,
>
> Pat Walters [MSFT]
>
> "MichaelM" <> wrote in message
> news:904172EB-A31D-41FD-B54A-...
> > Last night I went over to Windows Update to check for new updates and
> while I
> > was there I got a Window with the following.
> >
> > Automatic Updates
> >
> > Automatic Updates has encountered a problem and needs to close. We are
> sorry
> > for the inconvenience.
> >
> > I sent the error report to Microsoft and logged off.
> > Since then I keep getting the same Window popping up all the time. I
> cannot
> > get into Automatic Updates (tried 3 way) without the computer freezing up.
> > The windows keep popping up. What is going on?
>
>
>