Jump to content
Microsoft Windows Bulletin Board

Error number 80073712


Recommended Posts

Guest naraku4656
Posted
i have no idea what this means and how do i fix it
Guest TaurArian
Posted

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

Posted

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

Guest chris-stone@comcast.net
Posted

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?

Guest Hoock the Spook
Posted

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!

Posted

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!

>

Guest Alwei
Posted

FOUND A Solution :-) 80073712 / WIndows Vista Updatewill no longer work

 

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

Guest kungfunun@gmail.com
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no longer work

 

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/windowsupdate/redist/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

Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

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

 

"kungfunun@gmail.com" 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/windowsupdate/redist/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

>

>

>

Guest kungfunun@gmail.com
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

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

Guest kungfunun@gmail.com
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

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.

Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

you're most welcome :-)

 

 

 

"kungfunun@gmail.com" wrote:

>

>

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

>

>

Guest dsgtrain@googlemail.com
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

I can't seem to find the file 'pending.xml'. Yet I get the error code

80073712

Guest lbp1126
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

I just posted a fix that worked for me. Try it

 

"dsgtrain@googlemail.com" wrote:

> I can't seem to find the file 'pending.xml'. Yet I get the error code

> 80073712

>

>

Guest Michaelg50
Posted

As a result of this comand:

 

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

 

your user name will display which you can use in place <YourUsername> in

this command (drop the < and >, one space after G and no space after

<YourUsername>):

 

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

 

If the del command works (no errors displayed) you can go on and do the

download of Windows Update. It worked for me!

 

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

> >

  • 4 weeks later...
Guest lifeguard_guy2002
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

thanx i was having problems with the second line too and that way that you

did it worked like a charm thanx.

 

"kungfunun@gmail.com" wrote:

>

>

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

>

>

Posted

Tried this, Now NEW Code C015001A??

 

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

> >

  • 1 month later...
Guest mwm5200
Posted

I did this and then received the following Error: 80070002

I received this when I clicked on your link to download the WUA file.

Please help!

 

 

 

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

> >

  • 4 weeks later...
Guest bigcri@hotmail.com
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

bigcri@hotmail.com

 

I am having problems getting administrator privleges just to correct error

coden 80073712. Please help.

 

 

"lbp1126" wrote:

> I just posted a fix that worked for me. Try it

>

> "dsgtrain@googlemail.com" wrote:

>

> > I can't seem to find the file 'pending.xml'. Yet I get the error code

> > 80073712

> >

> >

  • 2 weeks later...
Guest fetchboi88
Posted

oh my lord!!!! thank you so much!!! I've been looking for a solution to this

since like may and i only JUST found this and it worked!!!!

 

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

> >

  • 2 weeks later...
Posted

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!

> >

Posted

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!

> > >

Guest lleiderm
Posted

Re: FOUND A Solution :-) 80073712 / WIndows Vista Update will no l

 

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.

 

Any suggestions?

Lloyd

  • 2 weeks later...
Guest Radagast
Posted

Hey, I was having the exact same problem with windows live update and this

fix really help me, and now it is working just fine, although the first time

I tried to do an update it gave me the blue screen of death, the 2nd was

easy. How did you come up with this fix that Microsoft doesn't even give it

in their website?

 

Cheers

  • 3 weeks later...
Guest THE COMPUTER LAB
Posted

This procedure fixed my problem instantly! Thanks!

 

 

"mwm5200" <mwm5200@discussions.microsoft.com> wrote in message

news:65693FD7-F939-4A7F-AF6F-381600767570@microsoft.com...

>I did this and then received the following Error: 80070002

> I received this when I clicked on your link to download the WUA file.

> Please help!

>

>

>

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

>> >

×
×
  • Create New...