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

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?

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

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...

[mindgames]

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 < >

thank the lord, i done it. couldnt get that second bit to work on cmd
promp, so after taking owenership, i went to the file properties, and
was now able to give myself full access to it that way, then delete
it. restarted, reinstalled windows update, and its working a treat.
cheers for your help.

I am not able to do windows vista home premium updates. I get error code
80073712.

I do not have pending.xml file on my computer.

I downloaded the windows update facility given in this thread, but when I
run it, it says it is already installed and there is no need to reinstall it.
But I still cannot do windows updates.

well i have read the soultions and they work fine depending on one fact...
you have the pending,xml file...... i do not yet i still get the error any
explantions?

when I type "net stop WuAuServ" in c:\WINDOWS\SYSTEM32 I get the message "Program too big to fit in memory" what should I do next ?

I contacted MS technical support. This is what they told me:

***

Step 1: Rename the Windows Update Softwaredistribution folder
==========================================
This problem may occur if the Windows Update, Software distribution folder
has been corrupted. We can refer to the following steps to rename this
folder. Please note that the folder will be re-created the next time we visit
the Windows Update site.

1. Close all the open windows.
2. Click the "Start" Button, click "All programs", and click "Accessories".
3. Right-click "Command Prompt", and click "Run as administrator".
4. In "Administrator: Command Prompt" window, type in "net stop WuAuServ"
(without the quotes) and press Enter.

Note: Please look at the cmd window and make sure it says that it was
successfully stopped before we try to rename the folder. However, if it
failed, please let me know before performing any further steps and include
any error messages you may have received when it failed.

5. Click the "Start" Button, in the "Start Search" box, type in "%windir%"
(without the quotes) and press Enter.
6. In the opened folder, look for the folder named "SoftwareDistribution".
7. Right-click on the folder, select "Rename" and type "SDold" (without the
quotes) to rename this folder.
8. Still in "Administrator: Command Prompt" window, type the command "net
start WuAuServ" (without the quotes) in the opened window to restart the
Windows Updates service.

Note: Please look at the cmd window and make sure it says that it was
successfully started. However, if it failed, please let me know before
performing any further steps and include any error messages you may have
received when it failed.

Step 2: SFC
============
Use the System File Checker (SFC) to scan system files for Vista
=====================================================
The System File Checker tool enable an administrator to scan all protected
files to verify their versions. To do so, follow these steps:

1. Click "Start", type "CMD" (without quotation marks) in the "Start Search"
box. Right click on the "CMD.exe" file, choose "Run as Administrator"
2. Copy and paste "SFC /Scannow" (without quotation marks) in the "Open"
box, and click "OK".

Note: There is a SPACE between "SFC" and "/Scannow", this command will take
several minutes to complete and may require access to the Windows
installation source files. If you are prompted to insert the CD, click
"Continue" each time it prompts. In addition the process may stop at 99%. If
this happens, please wait for some time and close it if it still stops at 99%.

***

The SFC command above detected several corrupted files on my system but
could not repair them, and a CBS log was generated which I compressed into a
ZIP archive and sent back to them by email.
They later told me on the same message to run Windows Update from the
Control Panel. This time it checked and detected several updates missing from
my computer (that is, no more error 80073712).

Now my worry is on those corrupt files reported by the CBS log generated by
the SFC command.

Then perhaps you should contact MS Tech Support, too?!

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

Support for Windows Update:
http://support.microsoft.com/gp/wusupport

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is related
to a Security Update and cite the update's KB number (e.g., KB123456).

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

To whom are you replying in this 10-month-old thread?

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

Unlimited installation and compatibility support for Vista SP1 is available
at no charge through 18 Mar-09
• US:
http://support.microsoft.com/oas/def...4&gprid=500921

• CA:
http://support.microsoft.com/oas/def...4&gprid=500921

• UK:
http://support.microsoft.com/oas/def...4&gprid=500921

• AU:
http://support.microsoft.com/oas/def...4&gprid=500921

• Other: http://support.microsoft.com/oas/default.aspx | select Windows
Vista | select Windows Vista Service Pack 1

I tried the search for "pending.xml" as well and did not find it. However, I
went ahead and downloaded and installed the the latest Windows Update version
from the referenced site
(http://download.windowsupdate.com/v7...gent30-x86.exe) and then ran Windows Update and it worked.

I also did not have pending.xml and when trying to run WindowsUpdateAgent30-x86.exe received the same 80073712 error message. I first had to run WindowsUpdateAgent30-x86.exe /uninstall and then ran WindowsUpdateAgent30-x86.exe /wuforce

this doesnt work for me it keeps saying system cannot find specified path

What does not work for you.

Is there a solution for this problem without having to upgrade to 7?

what makes you think upgrading will resolve the problem?

[ludlow_4]

Today (23 May 2010) I followed the fix described in AWHP's 20-07-2007 post (almost 3 years after the original post) for my Vista32 system. It worked perfectly. A (belated) thanks to AWHP!