PDA

View Full Version : error 0x80070002



jcr1
26-08-2013, 08:48 AM
Anyone got any ideas about how I can fix the above error (and one or two others involving updates)?

I'm running win7 pro, which I installed October 2009, and so far I've tried repair, from the install disk - this just gave me the message that my current install was more "up-to-date" (or words to that effect). I've tried microsoft's "fixit tool" and also tried renaming updates from services.msc - as per microsoft's help page,on this.

I'm really loathe to install one of those Reg Fixing type tools, as I suspect that more than a few of them are bad stuff - and they cost!

I think I see a clean install coming on, but I'd like to try to fix it without going to that extreme, first.

Speedy Gonzales
26-08-2013, 09:35 AM
Dont use reg cleaners. They'll make things worse. Is this the fixit you ran / what you tried ?? (http://support.microsoft.com/kb/910336). Looks like .net framework probs can cause this error too

jcr1
26-08-2013, 09:47 AM
Thanks Speedy.

Yes, that's the one.

Speedy Gonzales
26-08-2013, 09:49 AM
Did you try to do it yourself as well (under fix it myself)?

What firewall is installed (if youre not using Windows firewall)??

jcr1
26-08-2013, 10:34 AM
I did try that fixit myself - to no avail.

I have Windows firewall, none other. I don't know whether that's good or not?

jcr1
26-08-2013, 10:42 AM
I just tried to update and got these error codes;

Code 80073712 Windows Update encountered an unknown error
Code 52F Ditto

My machine's a mess:eek:

Speedy Gonzales
26-08-2013, 11:08 AM
You may have to download / then run this (http://windows.microsoft.com/en-US/windows7/What-is-the-System-Update-Readiness-Tool)

Get the 32 or 64 bit install. Depending on the version of windows. The 32 bit install is just over 150mb, the 64 bit 390 mb. It looks like that 52F error can happen if your Office 2003 install is corrupt. If it's installed. It may or may not apply to other versions of Office too

jcr1
26-08-2013, 11:23 AM
Great minds think alike:)

I'm just doing that even as we speak.
I figured it must be something to do with Office updates and it is 2003 I'm running.

Speedy Gonzales
26-08-2013, 11:34 AM
By the corrupt install, I mean the folder Office creates (msocache on C) is corrupt. You could try doing a repair of Office, see if that fixes the 52F error

jcr1
26-08-2013, 12:12 PM
I'll give that a go.

In the meantime, that file you suggested, I ran it, and now I don't get the 0x80070002 error when I start the computer - so far, so good. But, when I try to update I still get those other errors; 52F etc.

Speedy Gonzales
26-08-2013, 12:16 PM
At least one of the errors have been fixed (hopefully). If you havent installed any updates for Office yet, uninstall it, then use the fixit for Office 2003 (http://support.microsoft.com/kb/971179)

Then I would delete the msocache folder on C (If its there). Then reinstall Office again. See how that goes

jcr1
26-08-2013, 01:09 PM
That's sorted Office 2003; thanks Speedy.
Just working on error 80073712 now. I'm running the update diagnostic tool again - slim hope - but one never knows....

Speedy Gonzales
26-08-2013, 01:21 PM
That readiness tool should fix that error. If that doesnt work run a command prompt as admin. Then type sfc /scannow

jcr1
26-08-2013, 08:07 PM
The readiness tool couldn't quite do it. As a matter of fact, I have reason to believe, that it killed BankLink - and for a while I thought, "there goes a couple of weeks work":crying
But, thank goodness for backups and I was able to get my data restored:D

I did the scannow command as administrator, but that checked out OK.

Still 3 important updates to do and I'm a bit perplexed at this stage. But we've made some improvements. Thanks for your support Speedy.