[SOLVED] Windows Update error 80070246

S

servabofidem

New member
Joined
Jun 6, 2015
Posts
4
Windows update is not working... I know I had a bad stick of ram, and I'm sure this had something to do with it...

I Ran SFCFix... which is kind of neat...
AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 10
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.


​
cbs.log has a recurring complaint about an illegal character, but I cannot figure out what it's complaining about now..\
2015-06-09 22:05:39, Info CSI 00000008 PopulateComponentFamilies ignoring identity-less key [l:202{101}]"amd64_microsoft-windows-i..emsuppgrt.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5bddn0f86941k657"
2015-06-09 22:05:45, Error CSI 00000009@2015/6/10:02:05:45.876 (F) d:\win7sp1_gdr\base\lstring\lblob.cpp(2221): Error STATUS_ILLEGAL_CHARACTER originated in function RtlTranscodeLBlobs expression: __rv.UcsCharacter != (0xffffffff)
[gle=0x80004005]
2015-06-09 22:05:45, Info CBS Failed to get CSI store. [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
2015-06-09 22:05:45, Error CBS Failed to initialize store parameters with boot drive: and windows directory: [HRESULT = 0x80070246 - ERROR_ILLEGAL_CHARACTER]
​


I've attached a zipped copy of my CBS directory... done everything I can think to try....

I'd really appreciate any help. Thank you all for being here to help people like me.
 

Attachments

Hi and welcome to Sysnative and sorry for the delay. Yes, bad RAM can cause this issue to happen, especially the ILLEGAL_CHARACTER error. You have corruption within your registry. To resolve I will need a copy of your COMPONENTS hive. Please follow the instructions below.

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.
 
This may take another round of fixes but I believe I fixed the initial corruption. Please do the following.

Step#1 - Replace Manually
 1. Download COMPONENTSNEW.ZIP and save to your desktop.
2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
3. Now we have the COMPONENTS file that we will be using to replace your current one.
4. Navigate to C:\Windows\System32\config
5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again.
6. Take the file from the ComponentsNew folder on your desktop and paste it into C:\Windows\System32\config

Step#2 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Hi,

your hint to SUR and CheckSUR.log helped me to solve the problem on one of my boxes. What I've done:


  1. After WinUpdate endet with 0x80070246, I found msg ILLEGAL_CHARACTER in C:\Windows\Logs\CBS\CBS.log
  2. Installed (=run) hotfix KB947821 (SUR). The output in C:\Windows\Logs\CBS\CheckSUR.log showed the following uncorrectable errors:
    (f) CSI Corrupt Identity 0xC0000161 (not UTF8) 599cdµ9ae02..866ad36e35_6.1.7601.17647_adc247a524feP6c2 Bad identity
    (f) CSI Corrupt Identity 0xC0000161 (not UTF8) x86_06ed18c944520f95e685029ebd16aee3_1bf3856ad364e35W6.1.7601.21747_none_b0081b2e8eda39b7 Bad identity
    (f) CSI Could Not Open file 0x0000007B winsxs\Manifests\x86_06ed18c944520f95e685029ebd16aee3_1bf3856ad364e35W6.1.7601.21747_none_b0081b2e8eda39b7.manifest x86_06ed18c944520f95e685029ebd16aee3_1bf3856ad364e35W6.1.7601.21747_none_b0081b2e8eda39b7
    (w) CSI Replacement File: CreateFile Failed 0x0000007B
  3. REG LOAD HKLM\COMPONENTS C:\WIndows\System32\config\COMPONENTS
  4. Searched part of key "x86_06ed18c944520f95e685029ebd16aee3_" .
    It was important to take a part of the key without the corrupted (special) characters.
    The keypart was found in HKLM\COMPONENTS\DerivedData\Components in two registry entries:
    corrupted with special characters (notepad++ showed them as ASCII controlcodes, f.e. <DC3>) and uncorrupted.

    So, the "Bad identity" for key x86_06ed18c944520f95e685029ebd16aee3_<DC3>1bf3856ad364e35W6.1.7601.21747_none_b0081b2e8eda39b7 results from a corrupted character.
  5. As there are two nearly identical keys with nearly identical contents, I exported (=backup) both keys to files, then deleted the one with the corrupted character.
  6. Searched further - no other occurence of the corrupted key.
    This explains msgs "Could not open file" and "CreateFile failed" - nothing in the system for the corrupted and therefore unknown key.
  7. REG UNLOAD HKLM\COMPONENTS
    After running SUR again, the errors for this corrupted key are gone.
  8. For the other corrupted key, I got msgs:
    (f) CSI Corrupt Identity 0xC0000161 (not UTF8) 599cdµ9ae02..86029163d8_31bf;856ad36e35_6.1.7601.17647_adc247a524feP6c2 Bad identity
    (f) CSI Missing Deployment Key 0x00000000 599cd79ae02..860291635d8_31bf3856ad364e35_6.1.7601.17647_adc247a524fe16c2 HKLM\Components\CanonicalData\Deployments
    So, two nearly identical keys, but one with special characters (ex. the "greek mu").
  9. Again REG LOAD
    Searched for part of second bad identity: "e35_6.1.7601.17647_adc247a524feP6c2", so in addition to the corrupted key, I found a nearly similar entry but without special characters in HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments
  10. Changed the wrong 599cd... key after the correct key in HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
  11. Again REG UNLOAD
    Run SUR again - now I got two error messages for 599cd... key (CSI Corrupt Identity, CSI Catalog Missing), but both were fixed by SUR.
  12. Run SUR again - no errors.
  13. Now, WindowsUpdate run without problems
In principle, one has to correct the invalid key-registry-relations of the CSI.
It's hard to believe that they result from hardware errors, since - according to google - many people got them.
 
You must log in or register to reply here.
Back
Top