| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 134870 | 2013-08-25 20:48:00 | error 0x80070002 | jcr1 (893) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1352064 | 2013-08-25 20:48:00 | 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. |
jcr1 (893) | ||
| 1352065 | 2013-08-25 21:35:00 | Dont use reg cleaners. They'll make things worse. Is this the fixit you ran / what you tried ?? (support.microsoft.com). Looks like .net framework probs can cause this error too | Speedy Gonzales (78) | ||
| 1352066 | 2013-08-25 21:47:00 | Thanks Speedy. Yes, that's the one. |
jcr1 (893) | ||
| 1352067 | 2013-08-25 21:49:00 | Did you try to do it yourself as well (under fix it myself)? What firewall is installed (if youre not using Windows firewall)?? |
Speedy Gonzales (78) | ||
| 1352068 | 2013-08-25 22:34:00 | 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 (893) | ||
| 1352069 | 2013-08-25 22:42:00 | 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: |
jcr1 (893) | ||
| 1352070 | 2013-08-25 23:08:00 | You may have to download / then run this (windows.microsoft.com) 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 |
Speedy Gonzales (78) | ||
| 1352071 | 2013-08-25 23:23:00 | 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. |
jcr1 (893) | ||
| 1352072 | 2013-08-25 23:34:00 | 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 | Speedy Gonzales (78) | ||
| 1352073 | 2013-08-26 00:12:00 | 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. |
jcr1 (893) | ||
| 1 2 | |||||