Hello, I'm having a problem of unable to perform window updates due to problem 80070002, have ran the hotfix and tried the steps listed on Microsoft website but it didnt work (steps: deactivate the window update and rename softwaredistribution and reactivate window update), any help is greatly appreciated.
Window 7 64-bit Window Update error 80070002
- Thread starter urban1937
- Start date
Hello, and welcome to Sysnative!
Before I attempt to repair your PC, can you please run the System Update Readiness Tool one more time, and then post a new C:\Windows\Logs\CBS\CheckSUR.log. This is quite an unusual request, and it has nothing to do with the long length of the logfile (I have tools to strip out all of the fixed lines), I am actually concerned about progression, and wish another run in order to compare differences.
Thank you.
Richard
Before I attempt to repair your PC, can you please run the System Update Readiness Tool one more time, and then post a new C:\Windows\Logs\CBS\CheckSUR.log. This is quite an unusual request, and it has nothing to do with the long length of the logfile (I have tools to strip out all of the fixed lines), I am actually concerned about progression, and wish another run in order to compare differences.
Thank you.
Richard
Hello again Lawrence :)
Thank you very much for that. You did it perfectly :)
Unfortunately, there's a second issue. One of my jobs on any Windows Update thread is to consider the root cause. And unfortunately, I don't think yours was just bad luck. In actual fact, I think it is caused by hardware failure, specifically bad RAM. I know that this is probably the last thing you want to hear right now, but it unfortunately looks that way. Please follow these instructions to test this assertion of mine: Test RAM With Memtest86+
With hardware failure, it's always better to know for sure than to not know. RAM is very cheap these days, and is usually financially viable to replace, and I'll talk you through all of your options if it comes to it. But to start off with, we need to know whether it's actually the RAM or not, or whether it's not hardware at all. I will temporarily put the fix on hold until we get to the bottom of any hardware problems. Otherwise new problems will start popping up faster than I can fix them. Once it's all over, I'll make a totally new assessment.
However, if in the last couple of months you have already found and removed a failed RAM stick, then of course the above doesn't apply :)
Richard
Thank you very much for that. You did it perfectly :)
Unfortunately, there's a second issue. One of my jobs on any Windows Update thread is to consider the root cause. And unfortunately, I don't think yours was just bad luck. In actual fact, I think it is caused by hardware failure, specifically bad RAM. I know that this is probably the last thing you want to hear right now, but it unfortunately looks that way. Please follow these instructions to test this assertion of mine: Test RAM With Memtest86+
With hardware failure, it's always better to know for sure than to not know. RAM is very cheap these days, and is usually financially viable to replace, and I'll talk you through all of your options if it comes to it. But to start off with, we need to know whether it's actually the RAM or not, or whether it's not hardware at all. I will temporarily put the fix on hold until we get to the bottom of any hardware problems. Otherwise new problems will start popping up faster than I can fix them. Once it's all over, I'll make a totally new assessment.
However, if in the last couple of months you have already found and removed a failed RAM stick, then of course the above doesn't apply :)
Richard
Thanks for letting me know what's going on with my computer Richard. Sounds right, the RAM is 2 years old and hasn't been removed since I first bought this PC, so it could be the cause, I will have the test done and let you know about the result and will have the ram replaced if that is the cause. Thank you soooo much :)
Lawrence
Lawrence
Yes, that unfortunately means that your RAM has failed. Chances are that it's only one stick, but as RAM needs to be paired, you may end up having to replace two sticks. Where did you get this computer from? Can you please give me the make and model number. Is it still covered by warranty?
If it's not, we'll show you how to statically discharge yourself, open up your PC, then pop out the RAM sticks (they're usually very easy to access and remove). You will have to run the machine with memtest86+ one stick at a time until you find the bad one, as the current results cannot tell us which stick has failed, only that at least one stick has failed. Then you'll move the stick to another slot and try again, just to check it's the stick and not the connector (slot) on the motherboard that's bad.
Finally, we'll help you identify RAM which is compatible with your computer, and then you can put the new stick/sticks in.
How does that sound? Is this something you would be happy to undertake if we talk you through it? It really isn't that hard to replace RAM, you literally just discharge yourself, reach in, press the release catch, pull it out.
But...I'm not the one to talk you through this. I'm a Windows Update specialist, not a hardware expert. You don't want me guessing, you need somebody who actually knows. So, can you please make a new thread in the hardware forum here: Hardware - Sysnative Forums
linking to this thread, and the right people will respond and help.
Thank you.
Richard
If it's not, we'll show you how to statically discharge yourself, open up your PC, then pop out the RAM sticks (they're usually very easy to access and remove). You will have to run the machine with memtest86+ one stick at a time until you find the bad one, as the current results cannot tell us which stick has failed, only that at least one stick has failed. Then you'll move the stick to another slot and try again, just to check it's the stick and not the connector (slot) on the motherboard that's bad.
Finally, we'll help you identify RAM which is compatible with your computer, and then you can put the new stick/sticks in.
How does that sound? Is this something you would be happy to undertake if we talk you through it? It really isn't that hard to replace RAM, you literally just discharge yourself, reach in, press the release catch, pull it out.
But...I'm not the one to talk you through this. I'm a Windows Update specialist, not a hardware expert. You don't want me guessing, you need somebody who actually knows. So, can you please make a new thread in the hardware forum here: Hardware - Sysnative Forums
linking to this thread, and the right people will respond and help.
Thank you.
Richard
Hello Richard, Good news! I've been following the instructions for removing the case and RAM on the page you provided earlier and have found the bad RAM. Mine is not a manufacture PC but a self-built PC which is relatively easy to get remove of RAM without breaching of warranty :) I've once again ran the System Update Readiness Tool and post the CheckSUR.log to see if the hardware problem still exists and what to do with the window update errors. Thank you sooooo much and I really appreciate it.
Lawrence
Lawrence
Attachments
Hello again :)
That's really great news. I'm sorry that it turned out to be hardware failure, but at least you've found and fixed it now before any further damage occurred.
The software corruption that occurred before you removed the bad RAM is obviously still present, but I hope that I can fix it up for you. At this time I cannot promise anything, as you have very complex and difficult corruptions, however, I'll give it my best shot and we'll probably get it resolved. I've seen plenty worse in my time, if that's any consolation :)
We are now about to begin the fix process. If at any time you have any questions, no matter of what variety (whether they are about how to carry out the instructions, or what the instructions do), please do not hesitate to ask. I will always be more than happy to explain what the instructions do.
Here, this script will upload the Windows Update portion of your registry to an area of our server accessible only to the Windows Update staff and administrators. No personally identifiable information is uploaded, only Windows Update's backend data on which updates are currently installed. Your issues are of a complexity that I need to see them in front of me hence the upload, I cannot fix them off just the logfile.
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Thanks!
Richard
That's really great news. I'm sorry that it turned out to be hardware failure, but at least you've found and fixed it now before any further damage occurred.
The software corruption that occurred before you removed the bad RAM is obviously still present, but I hope that I can fix it up for you. At this time I cannot promise anything, as you have very complex and difficult corruptions, however, I'll give it my best shot and we'll probably get it resolved. I've seen plenty worse in my time, if that's any consolation :)
We are now about to begin the fix process. If at any time you have any questions, no matter of what variety (whether they are about how to carry out the instructions, or what the instructions do), please do not hesitate to ask. I will always be more than happy to explain what the instructions do.
Here, this script will upload the Windows Update portion of your registry to an area of our server accessible only to the Windows Update staff and administrators. No personally identifiable information is uploaded, only Windows Update's backend data on which updates are currently installed. Your issues are of a complexity that I need to see them in front of me hence the upload, I cannot fix them off just the logfile.
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download SFCFix.exe and save this to your Desktop.
- Download the file below, SFCFixScript.txt, and save this to your Desktop.
- Save any open documents and close all open windows.
- On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
- Drag the file SFCFix.txt onto the file SFCFix.exe and release it.
- SFCFix will now process the script.
- Upon completion, a file should be created on your Desktop: SFCFixScript.txt.
- Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please.
Thanks!
Richard
Hi Richard, I've done all the above steps but not sure if this is the right thing as it only contains a few lines. Thank you so much for helping me out Richard :)
SFCFix version 2.1.0.0 by niemiro.
Start time: 2014-02-04 08:40:51.069
Using .txt script file at C:\Users\user\Desktop\SFCFixScript.txt
Collect:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.1.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-02-04 08:40:52.819
----------------------EOF-----------------------
SFCFix version 2.1.0.0 by niemiro.
Start time: 2014-02-04 08:40:51.069
Using .txt script file at C:\Users\user\Desktop\SFCFixScript.txt
Collect:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.1.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-02-04 08:40:52.819
----------------------EOF-----------------------
Has Sysnative Forums helped you? Please consider donating to help us support the site!