Windows Updates failing with Error Code 80070246

Hi Steve,

Sorry for leaving you in the dark here.

Basically, you have a corruption somewhere in your registry that is causing Windows Update to fail. These corruptions normally occur in the COMPONENTS hive. This is easier to fix, because DISM/the SURT on Windows 7 can detect and log these problems for me to fix. However, your corruption does not occur in the COMPONENTS hive, which is why I asked for those files. Those are the other likely locations for a corruption to occur.

The problem now is finding out where exactly the corruption is. With no logs or information to go on, it's not easy.

SFCFix is the only real help I have here, and is currently undergoing staff testing before release. The release will fix the crash that occured on your system when running Bitshift::, but another crash has been discovered and needs to be fixed before release. Trust me when I say the developer is working hard on this! We're currently on the 7th beta release. It really shouldn't be long now.

I'm also currently taking some time away from the forum, so my time here is significantly less at the moment.

I'll let you know ASAP when I find something.

Sorry about all this,
Stephen
 
Right, a new version of SFCFix has been released, and should no longer crash on BitShift runs. So let's see what it says:

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.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


https://www.dropbox.com/s/wf0u9dgkxfsskvv/SFCFixScript.txt?dl=1

Stephen
 
Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-08-25 22:48:19.634
Using .txt script file at C:\Users\steve_000\Desktop\SFCFixScript.txt [0]








BitShift::
No corruptions detected.
BitShift:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-08-25 22:50:25.652
Script hash: hBI6Mql4H4Bclpn1EppfVE6OvuMnGbPTS9YilWvhfmA=
----------------------EOF-----------------------
 
Hello stevenjw, welcome to Sysnative!

Stephen is busy with school at the moment so he's asked me to look at this thread for him.

I have some good news and some bad news. The good news is that I've managed to track down the corruption that Stephen was looking for, the bad news is that it's too severe to repair. The only way to fix this is to reinstall Windows I'm afraid, but something went catastrophically wrong in your computer to make this mess and I'd like to look into a possible cause of this.

How old is this computer? Have you ever replaced parts in it? If so, what?

Tom
 
Hi Tom,

Well, that's pretty much just bad news. IMHO Microsoft does not make re-installing Window easy, especially after you've been running for a while and installed a lot of applications.

This is an older laptop, but I sprang for the top of the line in order for it to hold up long term. Well, it's done that with enough CPU, memory, and video for my needs even now. I upgraded to SSD when I upgraded from XP to a fresh install of Windows 8 Pro. That was just after the time a power surge took out the on-board ethernet. Everything else appeared to be fine including the OS, so I simply picked up a GB ethernet PC-card. The machine has been running fine ever since. So, even though I had a hardware issue, I did a fresh install of Windows 8 after on a new SSD. I'm not sure what would have corrupted it since then.

I was getting a BSOD recently, but it was due to an old card-reader driver. A Sysnative team found that out for me and I upgrade that to a driver supported by Windows 8 64bit. I still get a rare BSOD and they've determined that it's my NVidia driver. However, it's the latest for my GT9600M and a search reveals that I'm not the only one with NVidia driver issues. NVidia has gone downhill in IMHO, but being a laptop, I'm stuck with them and will apply any new ones that come along. The BSOD issue is very infrequent, so I live with it.

Given that you can't fix my upgrade issue, I'll ignore/hide those updates and not go to 8.1. I'll milk this hardware and software until I decide to I can't live without something else. I can use my NUC HTPC as my desktop and move over / install what I need from this laptop. Then install Windows 7 or Linux on the laptop for a backup. I should have upgraded to Windows 7 and not 8. Big mistake on my part.

Thanks for looking into this.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top