Error number 80073712

i have no idea what this means and how do i fix it

The "Windows Features" dialog box is empty in Windows Vista, or you receive
an error message that includes the following code when you try to use Windows
Update: "0x80073712"
http://support.microsoft.com/kb/931712/en-us


"naraku4656" wrote:

> i have no idea what this means and how do i fix it

I have exactly the same issue, and there isnt tehe expected registry entry.
So I gather there isnt a solution and my computer is at risk?


"TaurArian" wrote:

> The "Windows Features" dialog box is empty in Windows Vista, or you receive
> an error message that includes the following code when you try to use Windows
> Update: "0x80073712"
> http://support.microsoft.com/kb/931712/en-us
>
>
> "naraku4656" wrote:
>
> > i have no idea what this means and how do i fix it

On Jul 13, 6:04 pm, Ice <I...@discussions.microsoft.com> wrote:
> I have exactly the same issue, and there isnt tehe expected registry entry.
> So I gather there isnt a solution and my computer is at risk?
>
>
>
> "TaurArian" wrote:
> > The "Windows Features" dialog box is empty in Windows Vista, or you receive
> > an error message that includes the following code when you try to use Windows
> > Update: "0x80073712"
> >http://support.microsoft.com/kb/931712/en-us
>
> > "naraku4656" wrote:
>
> > > i have no idea what this means and how do ifixit- Hide quoted text -
>
> - Show quoted text -

I have the same error also, and have tried Microsofts solution, but
the entry in the registry does not exists. I have also turned off all
virus checking, firewall, ect... still get the same error.

IS there a solution to this problem?

There is no solution to this MS error other than to reinstall Vista!

After days and days of calling MS Australia, I finally got onto a Techy who
advised that there "was no way to fix this error" sorry, go and get stuffed
customer. We have your money now it is a problem belong you!!! God I love
Microsoft!

After a long search, some good inputs, here finally a procedure that worked
for me:
All credits to CogitoErgoSum on forums, hereunder his procedure with a
slight modification:

I assume MS will deliver a patch sooner or later for this issue... however, I
fixed it with the help of MS Support.

DISCLAIMER: This solution fixed the problem for me, I cannot guarantee it
will fix it for anybody else! Moreover, renaming system files might corrupt
your system!!!

The issue is that the WUA 3.0 (7.0.6000.374) upgrade is corrupted,
essentially the system reports the WUA to be 7.0.6000.374 but the files on
the disk are still from the old version (you can check some of the DLLs like
wups.dll, wuaueng.dll etc... in the windows\system32) ... and you cannot
install the WUA 3.0 even manually.

delete the following file:

C:\windows\winsxs\pending.xml

Since Windows security will not allow you to do this, hereunder the
procedure to take ownership of the file:

run a command prompt with "Run as Administrator".
Type in the following commands:

takeown /f C:\Windows\winsxs\pending.xml


cacls C:\Windows\winsxs\pending.xml /G <YourUsername>:F

then delete the file
Reboot the machine, then manually install the WUA 3.0 downloadable from
here:
http://download.windowsupdate.com/v7...gent30-x86.exe

This should fix the Error 80073712 when the other solutions do not work.

BE AWARE that renaming C:\windows\winsxs\pending.xml might have
unrecoverable impacts on your Vista installation




"Hoock the Spook" wrote:

> There is no solution to this MS error other than to reinstall Vista!
>
> After days and days of calling MS Australia, I finally got onto a Techy who
> advised that there "was no way to fix this error" sorry, go and get stuffed
> customer. We have your money now it is a problem belong you!!! God I love
> Microsoft!
>

Hi Guys,

hereunder a solution I found which proved to be working (I've modified the pending.xml ownership issue part and it worked for me after weeks of no solution...)

All credits to CogitoErgoSum on forums, hereunder his procedure with a
slight modification:

I assume MS will deliver a patch sooner or later for this issue... however, I
fixed it with the help of MS Support.

DISCLAIMER: This solution fixed the problem for me, I cannot guarantee it
will fix it for anybody else! Moreover, renaming system files might corrupt
your system!!!

The issue is that the WUA 3.0 (7.0.6000.374) upgrade is corrupted,
essentially the system reports the WUA to be 7.0.6000.374 but the files on
the disk are still from the old version (you can check some of the DLLs like
wups.dll, wuaueng.dll etc... in the windows\system32) ... and you cannot
install the WUA 3.0 even manually.

delete the following file:

C:\windows\winsxs\pending.xml

Since Windows security will not allow you to do this, hereunder the
procedure to take ownership of the file:

run a command prompt with "Run as Administrator".
Type in the following commands:

takeown /f C:\Windows\winsxs\pending.xml


cacls C:\Windows\winsxs\pending.xml /G <YourUsername>:F

then delete the file
Reboot the machine, then manually install the WUA 3.0 downloadable from
here:
http://download.windowsupdate.com/v7...gent30-x86.exe

This should fix the Error 80073712 when the other solutions do not work.

Tried it yesterday and it worked just fine... got 14 updates since then...


EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Hi, i have had this problem for ages, but from reading what u have
wrote, i think i might be getting somewhere, but my lack of knowledge
on cmd promt is letting me down. i can take ownership of the file
fine, but the second line "cacls C:\Windows\winsxs\pending.xml /G
<YourUsername>:F ", just never works for me, do i type it exactly like
that, except for the usernme part?

On Jul 20, 7:01 am, Alwei wrote:
> Hi Guys,
>
> hereunder a solution I found which proved to be working (I've modified the pending.xml ownership issue part and it worked for me after weeks of no solution...)
>
> All credits to CogitoErgoSum on forums, hereunder his procedure with a
> slight modification:
>
> I assume MS will deliver a patch sooner or later for this issue... however, I
> fixed it with the help of MS Support.
>
> DISCLAIMER: This solution fixed the problem for me, I cannot guarantee it
> will fix it for anybody else! Moreover, renaming system files might corrupt
> your system!!!
>
> The issue is that the WUA 3.0 (7.0.6000.374) upgrade is corrupted,
> essentially the system reports the WUA to be 7.0.6000.374 but the files on
> the disk are still from the old version (you can check some of the DLLs like
> wups.dll, wuaueng.dll etc... in the windows\system32) ... and you cannot
> install the WUA 3.0 even manually.
>
> delete the following file:
>
> C:\windows\winsxs\pending.xml
>
> Since Windows security will not allow you to do this, hereunder the
> procedure to take ownership of the file:
>
> run a command prompt with "Run as Administrator".
> Type in the following commands:
>
> takeown /f C:\Windows\winsxs\pending.xml
>
> cacls C:\Windows\winsxs\pending.xml /G <YourUsername>:F
>
> then delete the file
> Reboot the machine, then manually install the WUA 3.0 downloadable from
> here:http://download.windowsupdate.com/v7...st/standalone/...
>
> This should fix the Error 80073712 when the other solutions do not work.
>
> Tried it yesterday and it worked just fine... got 14 updates since then...
>
> EggHeadCafe.com - .NET Developer Portal of Choicehttp://www.eggheadcafe.com

Yes indeed, your username without the potential domain. Instead of /G, you
can also type /grant

Should be working fine (I was in the same case as you were).

Kind regards,

AWHP

"" wrote:

> Hi, i have had this problem for ages, but from reading what u have
> wrote, i think i might be getting somewhere, but my lack of knowledge
> on cmd promt is letting me down. i can take ownership of the file
> fine, but the second line "cacls C:\Windows\winsxs\pending.xml /G
> <YourUsername>:F ", just never works for me, do i type it exactly like
> that, except for the usernme part?
>
> On Jul 20, 7:01 am, Alwei wrote:
> > Hi Guys,
> >
> > hereunder a solution I found which proved to be working (I've modified the pending.xml ownership issue part and it worked for me after weeks of no solution...)
> >
> > All credits to CogitoErgoSum on forums, hereunder his procedure with a
> > slight modification:
> >
> > I assume MS will deliver a patch sooner or later for this issue... however, I
> > fixed it with the help of MS Support.
> >
> > DISCLAIMER: This solution fixed the problem for me, I cannot guarantee it
> > will fix it for anybody else! Moreover, renaming system files might corrupt
> > your system!!!
> >
> > The issue is that the WUA 3.0 (7.0.6000.374) upgrade is corrupted,
> > essentially the system reports the WUA to be 7.0.6000.374 but the files on
> > the disk are still from the old version (you can check some of the DLLs like
> > wups.dll, wuaueng.dll etc... in the windows\system32) ... and you cannot
> > install the WUA 3.0 even manually.
> >
> > delete the following file:
> >
> > C:\windows\winsxs\pending.xml
> >
> > Since Windows security will not allow you to do this, hereunder the
> > procedure to take ownership of the file:
> >
> > run a command prompt with "Run as Administrator".
> > Type in the following commands:
> >
> > takeown /f C:\Windows\winsxs\pending.xml
> >
> > cacls C:\Windows\winsxs\pending.xml /G <YourUsername>:F
> >
> > then delete the file
> > Reboot the machine, then manually install the WUA 3.0 downloadable from
> > here:http://download.windowsupdate.com/v7...st/standalone/...
> >
> > This should fix the Error 80073712 when the other solutions do not work.
> >
> > Tried it yesterday and it worked just fine... got 14 updates since then...
> >
> > EggHeadCafe.com - .NET Developer Portal of Choicehttp://www.eggheadcafe.com
>
>
>

hi, sorry to bug you again, still cant get it to work. so i put spaces
where there are spaces, and i put my username in < >