Windows Update not working (Current Error: 80070246)

Awesome. I've got your SOFTWARE hive too, that's in a private area rather than being attached to the end of your thread.

Before I continue I'd like to say a few things. Firstly, sorry this is taking so long with seemingly no improvement. The problem is once I've fixed some things up, more keep appearing. However, I do have a plan worked out and I am working my way through it, we should start seeing some significant reduction in the SURT errors shortly. However, the bitshifts you have are a sure sign of faulty RAM - either the old sticks you replaced caused this or the new ones are faulty. I am betting that it was the old ones, but I'd still like you to run Memtest when you get the chance.

If you're ever interested in what I'm doing, what I'm planning to do or why I'm doing anything, please ask!

So, here's the plan of attack as it stands:

  • CBS Registry Errors
  • S256H errors
  • Fix SOFTWARE hive bitshifts
  • Other bitshift repairs
  • Package replacement

Once we've completed that list, the SURT should report no errors. Well, that's the hope anyway, we'll have to wait and see!

Let's start with the first two, which I can do at once. This should reduce the SURT errors.

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, SFCFix.txt, and save this to your Desktop. Ensure that this file is named SFCFix.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 SFCFix.txt.
  5. Drag the file SFCFix.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/d46geoe9xj1pvep/SFCFix.txt

Once you've done that, run SURT and attach the log.

Stephen
 
I'll try to find a stick so that I can run the Memtest, but for the time being, we'll have to operate with the assumption it is the last RAM (at least I hope it is).

Anyway, Stephen, you have been a HUGE (and I mean it) help so far and I can't thank you enough for it. As I said before, you can bet my fiftieth child will be named Stephen/Stephina Balboa Maximus Kenobi the Third. That's a promise.

All this process has been far from "seemingly no improvement". As I stated previously, I managed to update quite a lot of queued updates and said update aparently resolved the BSOD problem (if I pinpointed the cause right and I think I did). Right now, the only important update that keeps returning an error message is a "W7 service pack 1 (KB976932)" and we are working on it, as you so diligently is resolving a problem after another.

Again, I can't thank you enough for the help you have given me so far.

Having said that, I'll return to you later with the last request and, possibly, the MemTest done.
 
You're most welcome, you are fantastic to work with which makes my life so much easier and fun!

I'm glad we're making progress and that the BSODs have stopped - great news! :D I've got your SOFTWARE hive repaired and ready to go, so once you've done the previous post's steps, then we can move on to that fairly quickly. There's light at the end of the tunnel, and I'm making good headway with the other bitshifts throughout the COMPONENTS hive.

As I said before, you can bet my fiftieth child will be named Stephen/Stephina Balboa Maximus Kenobi the Third. That's a promise.
Click to expand...
:lol: I like the name!

Stephen
 
I let the MemTest run for more than 2 hours and here is the results. I guess it's safe to say the faulty RAM was the previous one, right?

Oh, and here is the log.

Code: 
SFCFix version 2.3.0.0 by niemiro.
Start time: 2014-08-04 03:03:36.054
Using .txt script file at C:\Users\ANTONIO\Desktop\SFCFix.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB981852~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1_for_KB2862772~31bf3856ad364e35~x86~~9.1.1.0.

Failed to import registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-m..tlocation.resources_31bf3856ad364e35_6.1.7600.16385_en-us_0c3f5887c4ba0dee. A root key cannot be created under that hive.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB981852~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB981852~31bf3856ad364e35~amd64~~6.1.1.1.
WARNING: Failed to create backup for registry key -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1_for_KB2862772~31bf3856ad364e35~x86~~9.1.1.0.

Successfully deleted registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1_for_KB2862772~31bf3856ad364e35~x86~~9.1.1.0.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB981852~31bf3856ad364e35~amd64~~6.1.1.1.
RegistryScript:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 2.3.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2014-08-04 03:03:36.287
Script hash: 6LYhlrWfAL5XZhJs4lkr4aX5aLq6haRNG76F8XmdyRU=
----------------------EOF-----------------------
 

Attachments

  • 2014-08-03 16.06.32.jpg
    2014-08-03 16.06.32.jpg
    196.6 KB · Views: 4
SFCFix is being finicky with your computer, and not doing exactly what I want, so I'm going to fix everything up my end and then give you the repaired hives to replace. I was hoping I could do it with SFCFix because it's normally quicker, but since it's already failed on two separate attempts, it'll be easier for me to repair it my end. This should, all going well, be the second to last fix!

This repair takes care of the failed SFCFix script, multiple bitshifts and other errors detected by the SURT.

Replace COMPONENTS Hive

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. Please download the below file, components.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing a file: components (it has no file extension)
  5. Then navigate to C:\Windows\system32\config and rename the file components to components.bak.
  6. Copy (Ctrl+C) and Paste (Ctrl+V) the components file on your Desktop into this folder.
  7. Run the System Update Readiness Tool (SURT) again and when it finishes installing, attach the log to your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log


https://www.dropbox.com/s/xcall6rm4nklp2b/COMPONENTS.zip

Note: If, at any point, you are displayed an error saying the file is in use, or access denied, reboot and try again.

Stephen
 
Agraavan said:
I'm already at the "COMPONENTS(3).bak" ><
Click to expand...
Yeah... Sorry about that!

I wanted to do this with SFCFix, but there's a bug in it at the moment that it preventing me from doing so. So I'm having to do it the manual way I'm afraid! Niemiro is currently working on a fix for SFCFix which should be out in the next few days, but since we're so close now, I'm sure you can do one more hive replacement :p

But look - we really are nearly there now!
Code: 
Summary:
Seconds executed: 500
 Found 21 errors
 Fixed 19 errors
  CSI Manifest and S256H Do Not Match Total count: 2
  CSI Missing Component Key Total count: 3
  Fixed: CSI Missing Component Key.  Total count: 3
  CSI Missing Identity Total count: 3
  Fixed: CSI Missing Identity.  Total count: 3
  CSI Missing C Mark Total count: 3
  Fixed: CSI Missing C Mark.  Total count: 3
  CSI Located Replacement: Invalid (S256H) Total count: 36
  CSI F Mark Missing Total count: 10
  Fixed: CSI F Mark Missing.  Total count: 10

Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-font-truetype-batang_31bf3856ad364e35_6.1.7600.16385_none_13de7dc07ffbe591.manifest
    winsxs\manifests\amd64_microsoft-windows-hal-events_31bf3856ad364e35_6.1.7600.16385_none_8851d1e6c9538100.manifest

That leaves just two errors! :D And I've fixed them up my end. SFCFix would normally do this, but as I said, you're going to do this the old fashioned way. This should hopefully get Windows Update working again, but there is one more thing I need to fix up after this. :)

Replace COMPONENTS Hive

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. Please download the below file, components.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing a file: components (it has no file extension)
  5. Then navigate to C:\Windows\system32\config and rename the file components to components.bak.
  6. Copy (Ctrl+C) and Paste (Ctrl+V) the components file on your Desktop into this folder.
  7. Run the System Update Readiness Tool (SURT) again and when it finishes installing, attach the log to your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log


Note: If, at any point, you are displayed an error saying the file is in use, or access denied, reboot and try again.

https://www.dropbox.com/s/ic2n01qn1iimheq/COMPONENTS.zip

I've got my fingers crossed, but Windows Update should be working now! Hopefully its been worth the wait! :D

Stephen
 
Actually it was just a way to ask if I was doing it right just renaming all the files as components.bak and letting windows add the numbers at the end. ¬¬ I really don't care if it takes 30 backups if it means we will fix every error there is on those logs.

I'll ran the update after rebooting the PC to see if it worked as intended and edit this post with the results.

Here is the new log:

[edit] No cigar. I'm still getting an 80070246 error when I try to download this update: "Windows 7 Service Pack 1 for systems based on x64 (KB976932)"
 

Attachments

Can you run SURT once more? Then attach your whole CBS folder to your next post. Thanks.
 
Hi,

Well, let's start with the good news! This is the latest log from the SURT:

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 25.0
2014-08-05 22:05

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 553
 No errors detected

Hurrah! But there's still obviously an issue:

Code: 
2014-08-05 19:50:32, Error                 CSI    0000000b@2014/8/5:22:50:32.601 (F) d:\win7sp1_gdr\base\lstring\lblob.cpp(2221): Error STATUS_ILLEGAL_CHARACTER originated in function RtlTranscodeLBlobs expression: __rv.UcsCharacter != (0xffffffff)
[gle=0x80004005]
2014-08-05 19:50:35, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(582) #116301# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::EnumDeploymentReferences(flags = 00000003, tlcid = @0x80bef50, pszSubscription = (null), pszCodebase = (null))
[gle=0x80070246]
2014-08-05 19:50:35, Info                  CBS    Failed to call EnumDeploymentReferences on deployment: amd64_wvmic.inf_31bf3856ad364e35_6.1.7600.16385_none_5dd6b07b661d8010 [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to get component state. [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to get current state of the deployment [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to get Transaction State for package: Microsoft-Hyper-V-Guest-Integration-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, update: Hyper-V-vmic [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to get current state. [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to populate updates for package: Microsoft-Hyper-V-Guest-Integration-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385 [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to add package: Microsoft-Hyper-V-Guest-Integration-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385 [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to process package watchlist. [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Info                  CBS    Failed to prepare starting packages [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014-08-05 19:50:35, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2014

I think this is in your SOFTWARE hive, which whilst I did fix, I would like to do it again with a new copy from your computer.

SFCFix SOFTWARE Collection


  1. Download SFCFix.exe using the following link and save the tool to your Desktop: [sfcfixdownload]Download SFCFix[/sfcfixdownload]
  2. Download SFCFix.txt and save this to your Desktop as well: https://www.dropbox.com/s/zmwdi2tk09dohfn/SFCFix.txt?dl=1
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFix.txt.
  4. Drag the file SFCFix.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your COMPONENTS hive to our server.


Stephen
 
Hi,

As promised, here is a fix for your SOFTWARE hive. The SOFTWARE hive is a boot critical hive, so your computer won't turn on at all if its damaged. For good measure, we'll perform a backup before replacing it. You can't back it up the way we did the COMPONENTS hive, since it is constantly in use, so I have a tool to do that for me.

RegBak

Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.



  • Right-click on regbak.zip then select Extract all... and extract the files to your Desktop

    For 32-bit (x86) editions of Windows, double-click on regbak.exe
    For 64-bit (x64) editions of Windows, double-click on regbak64.exe​

    If you are unsure whether you have x86 or x64 Windows, see here
  • Without changing any options, click Next. RegBak will now backup all of your registry hives.


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 file below, SFCFix.zip, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file 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/vm2mei0468v4w0l/SFCFix.zip

Stephen
 
This seems kinda dangerous. What exactly is the purpose of the backup if it is in the computer that won't turn on at all if anything goes wrong? Should I put it in a external source? If so, what have to be done in case everything don't go acording to the plan? You scared me. *bites nails*

Ow, and I don't have to extract the SFCFix.zip before dragging it onto the .exe, am I right?

(I'll proceed with it tonight, anyway)
 
Nothing to be scared of. :)

The backup is only there in case of an emergency, we should never need it. Even if Windows can't boot normally, you can boot into the recovery environment and then copy the backup from the backup folder to the correct location. Sorry - I didn't mean to scare you, I just wanted to take the necessary precautions in the very unlikely event it does go wrong.

Stephen
 
You are enjoying my fear, aren't you, you soulless monster? :p

Just to be sure, I don't have to extract the SFCFix.zip before dragging it onto the .exe?
 
:lol:

Yeah, no need to unzip it - just drag SFCFix.zip onto SFCFix.exe :)

Stephen
 
I just noticed this thread, thanks for your contribution to Sysnative.
If there are any BSODs I'll analyse them for you, I'll just subscribe and watch over this thread.
Another way to monitor Stephen's skills, I've never done much with Windows updates or SFC fixes.
 
I can't edit my posts after 15 minutes so I'll post again.

Can you just upload the dump files anyway, even if you're not getting them anymore as I'm still interested.
They seem to be mainly network related.

Go to
Code: 
C:/Windows/minidump

Copy the files to the desktop, compress them in a .zip folder and upload them here.

I'd like a Kernel memory dump as well as it might give me something to blog about as minidumps don't contain much information.

Go to
Code: 
C:/Windows/MEMORY.dmp

Copy it to the desktop and compress it in a .zip folder as well, however this time you'll need to upload it to a file sharing site like Onedrive as it's too large to upload directly.

The Kernel dump file isn't needed but I'd like to take a look anyway.
 
I see what is going on here, I'm starting to get on everyone nerves so you are joining forces to get rid of me sooner rather than later...

Here is the SFCFix log:

Code: 
SFCFix version 2.3.0.0 by niemiro.
Start time: 2014-08-08 02:09:27.078
Using .zip script file at C:\Users\ANTONIO\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Sysnative\config\SOFTWARE

The file \\?\C:\Windows\Sysnative\config\SOFTWARE is in use and must be replaced over a reboot.

Successfully pended file for replace over reboot: \\?\C:\Windows\Sysnative\config\SOFTWARE
PowerCopy:: directive completed successfully.




Reboot:: directive completed successfully.




PostRebootCorruptionDetection::
Hash failure for file \\?\C:\Windows\Sysnative\config\SOFTWARE.
 Expected: jXJawQ15OW3TGsaT+PelLrEuopRU0MaLMfGs9xwKoHU=
 Found: Failed to generate hash - file may be in use.
PostRebootCorruptionDetection:: directive failed to complete successfully.




PostRebootRestorePermissions::
Successfully restored ownership for C:\Windows\Sysnative\config\SOFTWARE
Successfully restored permissions on C:\Windows\Sysnative\config\SOFTWARE
PostRebootRestorePermissions:: directive completed successfully.




Failed to process all directives successfully.
SFCFix version 2.3.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2014-08-08 02:22:44.731
Script hash: 
----------------------EOF-----------------------

Jared said:
I just noticed this thread, thanks for your contribution to Sysnative.
If there are any BSODs I'll analyse them for you, I'll just subscribe and watch over this thread.
Another way to monitor Stephen's skills, I've never done much with Windows updates or SFC fixes.
Click to expand...
No problem at all. Au contraire, it was the least I could do after all the support I have been having.

Well, you weren't kidding when you said it was too large to upload, the file has almost 1gb. As soon as I have a link to provide, I'll post it here. In the meantime, welcome to my chamber of misery, where everytime we think we are getting somewhere, my computer throw a curve ball at us. Thank you for taking your time to try and help me, even though I'm a helpless case. I sure can use all the help I can get, especially with the BSOD occurences, sice Stephen have been extremely helpful and eficient with my problem regarding the Windows Update.

I'm attaching the minidumps to this post and, as said before, I'm soon gonna post the link to the MEMORY.dmp.

[EDIT] Oops, forgot the minidumps.
And here it is the MEMORY.dmp link: https://dl.dropboxusercontent.com/u/49343986/MEMORY.rar
 

Attachments

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