[Allan]

I went through the process of getting Microsoft updates v6 and installed the
active X. The after the installation of the active X I get this error
0x80072F76. I tried installing microsoft updates before and the error number
was 0X80245033. So I thought to do a system restor to yesterday and now the
new error number comes up. PLEASE, how do I fix this mess I am in?

[Jim]

I get the same error when I try to get an update. Did you get an answer the
the problem?

"Allan" wrote:

> I went through the process of getting Microsoft updates v6 and installed the
> active X. The after the installation of the active X I get this error
> 0x80072F76. I tried installing microsoft updates before and the error number
> was 0X80245033. So I thought to do a system restor to yesterday and now the
> new error number comes up. PLEASE, how do I fix this mess I am in?

[Allan]

No I have not. Have emailed Microsoft about it and got a reply that it will
have to be sent to Windows Upadate Professional Support. As soon as I get a
response and fix for this I will post it for you.
Allan

"Jim" wrote:

> I get the same error when I try to get an update. Did you get an answer the
> the problem?
>
> "Allan" wrote:
>
> > I went through the process of getting Microsoft updates v6 and installed the
> > active X. The after the installation of the active X I get this error
> > 0x80072F76. I tried installing microsoft updates before and the error number
> > was 0X80245033. So I thought to do a system restor to yesterday and now the
> > new error number comes up. PLEASE, how do I fix this mess I am in?

[Soeren]

> No I have not. Have emailed Microsoft about it and got a reply that it will
> have to be sent to Windows Upadate Professional Support. As soon as I get a
> response and fix for this I will post it for you.

Sounds good. I have the same problem. Installed the activeX thingy and now
there seems to be no go on the update. I had a similar problem half a year
ago, though most likely another error code, and after 5 frustrating days of
searching the net I finally gave in and reinstalled my rig. However, this
time I have no intention of doing so. The update broke something - there must
be a fix.

[Soeren]

Hi again

I think I have, if not THE, then at least A solution to the problem. I hope
this will also fix your problems.

What I did was start a command prompt and unregister the wuweb.dll which
seemed to cause my problems.

@command prompt type:
regsvr32 c:\windows\system32\wuweb.dll /u

I then deleted the directory (with all it's contents):
c:\WINDOWS\SoftwareDistribution\WuRedir

The classic reboot of your rig then followed (just to make sure the
wuweb.dll was truely dead) and I fired up Windows Update again. It is now
back to using v5 of the update and this time seems to get the transition to
v6 (Microsoft Update) right.

No more error codes and a nice working updating system again. :o)

[Jeff]

This did the trick on my machine. Thanks for the information!

"Soeren" wrote:

> Hi again
>
> I think I have, if not THE, then at least A solution to the problem. I hope
> this will also fix your problems.
>
> What I did was start a command prompt and unregister the wuweb.dll which
> seemed to cause my problems.
>
> @command prompt type:
> regsvr32 c:\windows\system32\wuweb.dll /u
>
> I then deleted the directory (with all it's contents):
> c:\WINDOWS\SoftwareDistribution\WuRedir
>
> The classic reboot of your rig then followed (just to make sure the
> wuweb.dll was truely dead) and I fired up Windows Update again. It is now
> back to using v5 of the update and this time seems to get the transition to
> v6 (Microsoft Update) right.
>
> No more error codes and a nice working updating system again. :o)

[Sally]

I just tried this and it didn't work
--
Sally


"Jeff" wrote:

> This did the trick on my machine. Thanks for the information!
>
> "Soeren" wrote:
>
> > Hi again
> >
> > I think I have, if not THE, then at least A solution to the problem. I hope
> > this will also fix your problems.
> >
> > What I did was start a command prompt and unregister the wuweb.dll which
> > seemed to cause my problems.
> >
> > @command prompt type:
> > regsvr32 c:\windows\system32\wuweb.dll /u
> >
> > I then deleted the directory (with all it's contents):
> > c:\WINDOWS\SoftwareDistribution\WuRedir
> >
> > The classic reboot of your rig then followed (just to make sure the
> > wuweb.dll was truely dead) and I fired up Windows Update again. It is now
> > back to using v5 of the update and this time seems to get the transition to
> > v6 (Microsoft Update) right.
> >
> > No more error codes and a nice working updating system again. :o)