RE: Windows Update Stuck

Hello ShadowGod,

Am I correct in thinking that you are running CCleaner or another registry

cleaner?

- -- ---

See if anything here helps.

Windows Update

<http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?query=80010106&dg=microsoft.public.windowsupdate&cat=en_US_56d1dd45-de9e-4fc5-9bc1-2d1d0de6daee&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us>

Google

<http://www.google.com/search?hl=en&q=0x80010106&btnG=Search>

<http://www.google.com/search?hl=en&q=80010106&btnG=Search>

Next

Start a free Windows Update support incident request:

See the "Need more help? Tell us what problem you are having" section of

<https://support.microsoft.com/oas/default.aspx?gprid=6527>

Support for Windows Update:

<http://support.microsoft.com/gp/wusupport>

Good luck

-=-

"ShadowGod" wrote:

> Windows Update is stuck at "Checking for the latest updates for your

> computer..."

>

> I've had this issue before and had to reinstall. It worked for awhile. I'm

> not going to reinstall Windows XP every week because there is no solution to

> this bug. I will buy a Mac.

>

> Why won't MS recognize this issue? It's a Microsoft bug.

>

> Here are the last few lines of my WindowsUpdate.log:

>

> 2008-07-15 19:00:31:250 1240 70 Driver Calculated driver attributes as

> 0x00000000

> 2008-07-15 19:00:31:265 1240 70 Misc Validating signature for

> C:\WINDOWS\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muredir.cab:

> 2008-07-15 19:00:31:265 1240 70 Misc Microsoft signed: Yes

> 2008-07-15 19:00:31:296 1240 70 Misc Validating signature for

> C:\WINDOWS\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muredir.cab:

> 2008-07-15 19:00:31:312 1240 70 Misc Microsoft signed: Yes

> 2008-07-15 19:00:31:312 1240 70 PT +++++++++++ PT: Synchronizing extended

> update info +++++++++++

> 2008-07-15 19:00:31:312 1240 70 PT + ServiceId =

> {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =

> https://www.update.microsoft.com/v6/ClientWebService/client.asmx

> 2008-07-15 19:00:31:421 1240 70 Agent * Added update

> {6B0FC530-10C2-47B8-BBDA-8014C9D8D317}.100 to search result

> 2008-07-15 19:00:31:421 1240 70 Agent * Found 1 updates and 36 categories

> in search evaluated appl. rules of 610 out of 772 deployed entities

> 2008-07-15 19:00:31:421 1240 70 Agent *********

> 2008-07-15 19:00:31:421 1240 70 Agent ** END ** Agent: Finding updates

> [CallerId = MicrosoftUpdate]

> 2008-07-15 19:00:31:421 1240 70 Agent *************

> 2008-07-15 19:00:31:453 208 f48 COMAPI FATAL: Call to CallbackWorker()

> failed, hr=80010106

> 2008-07-15 19:00:36:421 1240 70 Report REPORT EVENT:

> {2ECB3F07-6EF7-4839-BA39-B89641CB3FE0} 2008-07-15

> 19:00:31:421-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 MicrosoftUpdate Success Software

> Synchronization Windows Update Client successfully detected 1 updates.

>

> ----------------------

>

> "FATAL: Call to CallbackWorker() failed" is obviously the problem, why is it

> failing? Is there any way to find out why it is failing or do we all just

> have to make wild guesses? No, I have no viruses, no spyware, no IE7

> toolbars or add-ons. I swear I've tried every single documented "fix" for

> this with no success.