Re: Error number 80073712

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Ah,

Managed to delete the file.

After taking ownership of the file, I then manage to go to the file
properties and change the permissions to full control and now managed to
delete the file.

I have not rebooted yet so cannot confirm if this fix works but at least the
file is now deleted - thanks for your previous posting though.

"Glenn" wrote:


Hi,

I have followed all the instructions, managed to take ownership of the file
and also used the commands

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

You can do the delete here too with this command:

del C:\Windows\winsxs\pending.xml

However, when trying to delete the file, I get the error...

Access Denied.

I do have full administrative privilages but no matter what I do, I cannot
delete the file. I also tried to take ownership via the file properties but
all that is greyed out for adding security or users.

Any ideas how I can delete this file.

Thanks


"AWHP" wrote:

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/windowsupdate/redist/standalone/WindowsUpdateAgent30-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!

.

Relevant Pages

  • Re: Error number 80073712
    ... The issue is that the WUA 3.0 upgrade is corrupted, ... procedure to take ownership of the file: ... then manually install the WUA 3.0 downloadable from ... This should fix the Error 80073712 when the other solutions do not work. ...
    (microsoft.public.windowsupdate)
  • Re: Error number 80073712
    ... I have followed all the instructions, managed to take ownership of the file ... The issue is that the WUA 3.0 upgrade is corrupted, ... Type in the following commands: ... then manually install the WUA 3.0 downloadable from ...
    (microsoft.public.windowsupdate)
  • Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no longer work
    ... 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...) ... The issue is that the WUA 3.0 upgrade is corrupted, ... run a command prompt with "Run as Administrator". ...
    (microsoft.public.windowsupdate)
  • Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l
    ... 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...) ... The issue is that the WUA 3.0 upgrade is corrupted, ... run a command prompt with "Run as Administrator". ...
    (microsoft.public.windowsupdate)
  • Re: How to prevent access to other users Home directories?
    ... and, if necessary, chown in the Terminal to fix them (assuming you know ... If you click "Cancel", the box *appears* to remain checked, but if you try accessing restricted files/folders on that drive, or close & re-open the Get Info dialog, you'll find that the "ignore ownership" option is still turned off. ... There apears to be a bug in OS X where it prompts you to authenticate as an administrator to uncheck the option, ...
    (comp.sys.mac.apps)