Windows Update Error Code 8008370B

tom982 said:

Hi NLK,

I was afraid that icacls might fail for the folder, but it was worth a try. Looks like we're doing this manually!

Can you navigate to:

C:\Windows\winsxs\

And find the following folder:

amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24

Right click > Properties > Security > Advanced > Owner > Edit

Click on Administrators and tick the box labelled Replace owner on subcontainers and objects. Press Apply then OK. Close the Advanced Security Settings for amd64... window, you should now be back to the original security tab. Click Edit, select Administrators, tick Full Control then press Apply then OK. Leave this folder open as we will be putting files inside this.

Now download these files:

https://dl.dropbox.com/u/16537616/SF.../NLK_Files.zip

Extract the contents to the folder that we were just dealing with that should still be open. Just copy and paste the two files and the folder into

C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\

Merge the folder with the existing one if it prompts you.


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: SFC.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.

Then run the SURT and post the logs please :)

Tom

Tom,

After changing permissions to the appropriate folder and adding the folder/files from your zip.

The SFCFix results are as follows:

Code:

SFCFix version 1.3.1.0 by niemiro.
Start time: 2013-03-09 19:39:22.653
Using .txt script file at C:\Users\NLK\Desktop\SFCFix.txt




TrustedInstaller::
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\Amd64\tsmxu003.ini
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\Amd64\tsmxu003.xml
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\Amd64\tsmxu003.gdl
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\Amd64\tsmxuPipelineConfig.xml
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\Amd64\tsmxuui3.dll
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\Amd64\tsmxcman.gpd
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\Amd64\tsmxbman.gpd
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\prnts003.cat
Successfully set file ownership to TrustedInstaller for C:\Windows\winsxs\amd64_prnts003.inf_31bf3856ad364e35_6.1.7600.16385_none_1a5ec630d9861d24\prnts003.inf
TrustedInstaller:: directive completed successfully.




Successfully processed all directives.
SFCFix version 1.3.1.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2013-03-09 19:39:22.673
----------------------EOF-----------------------

The resultant CBS zip from the SURT is attached with the following summary:
Summary:

Seconds executed: 327
Found 9 errors
CSI Manifest Missing Total count: 1
CSI Manifest and S256H Do Not Match Total count: 1
CSI Located Replacement: Invalid (S256H) Total count: 11
CSI Payload File Missing Total count: 2
CSI Missing Winning Component Key Total count: 5

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-v..ualpc-vmm.resources_31bf3856ad364e35_7.1.7600.16393_sv-se_3fee309205435163.manifest
winsxs\manifests\amd64_netfx-system.drawing_b03f5f7f11d50a3a_6.1.7600.16385_none_05221d84ee493566.manifest

Progress this time. Standing by for your next reply.

Thank You,

NLK

tom982 said:

Hi NLK,

Bingo! That's finally done it.

Would you mind zipping up and attaching this file for me please?

C:\Windows\winsxs\Manifests\amd64_netfx-system.drawing_b03f5f7f11d50a3a_6.1.7600.16385_none_05221d84ee493566.manifest

Tom

Hello Tom,

Please see the attached per your request.

Regards,

NLK

tom982 said:

Hi NLK,

Sorry for the delay. The manifest SHA256 hash is proving a little more difficult to fix than first anticipated! I will keep you posted as soon as I've made some progress.

Tom

Good day Tom,

Thank You for your outstanding efforts as well as the update. Never a reason for you to apologize to me.

Standing by.

Best Regards,

NLK

tom982 said:

Hi NLK,

You know, in all of my time here, I've never come across someone so appreciative of the help. Some will cruise through without saying thank you once, others say the odd thank you but you're up and above the rest.

Do you remember the process to swap the COMPONENTS hives? If so, can you use the latest hive:

https://dl.dropbox.com/u/16537616/NLK-v4.zip

I think I've finally nailed this SHA256 hash.

Tom

Hello Tom,

As you are taking your valuable time to use your expertise in order to help me, I feel like I could never thank you enough and I'd be doing you a disservice to not express my gratitude irrespective of any outcome.

Per your latest instructions, I applied the new components file, restarted, and ran the SURT with the following summary of the attached CBS zip:

Summary:
Seconds executed: 464
Found 12 errors
Fixed 4 errors
CSI Manifest Missing Total count: 1
CSI Catalog Missing Total count: 3
Fixed: CSI Catalog Missing. Total count: 3
CSI Missing C Mark Total count: 1
Fixed: CSI Missing C Mark. Total count: 1
CSI C Mark Deployment Not Marked Total count: 1
CSI Payload File Missing Total count: 2
CSI Missing Winning Component Key Total count: 4

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-v..ualpc-vmm.resources_31bf3856ad364e35_7.1.7600.16393_sv-se_3fee309205435163.manifest

Standing By for your reply.

Best Regards,

NLK

tom982 said:

Hi NLK,

Excellent! I'm glad that S256H problem has finally disappeared. Usually registry corruption changes one or two characters in a text string but the whole S256H value was different which confused me as I thought it couldn't possibly be corruption and put the difference down to a mistake at my end. But I took a shot in the dark, replaced the whole value with a clean one and it worked! Now I would like to fix the remaining missing payload files:

Code:

(f)    CSI Payload File Missing    0x00000000    prnts003.inf_loc    amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28    
(f)    CSI Payload File Missing    0x00000000    tsmxuui3.dll.mui    amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28

Navigate to the C:\Windows\winsxs\amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Under the Owner tab, click Edit.
Click "Other Users and Groups".
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK THREE times.
Click on the Permissions tab.
Under type Deny, single click on any entries and click Remove. (N.B.: There may not be any Deny entries, in which case just ignore this step. Just remove any that do exist)
Click OK.
Click Edit (now on the standard file Property window under the Security tab).
Click Add.
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK.
Single click on Everyone and then tick the "Full Control" box under Allow.
Click OK TWO times.

Now please extract and copy the attached files (prnts003.inf_loc and tsmxuui3.dll.mui) into C:\Windows\winsxs\amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28\

Finally:

Navigate to the C:\Windows\winsxs\amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Click on the Permissions tab (should be the default tab).
Click Change Permissions
Select and click Remove onthe ALLOW: Everyone entry you just added.
Click OK.
Go to Owner tab.
Click Edit.
Click "Other Users and Groups".
Paste in "NT Service\TrustedInstaller"
Click OK.
Put the check in "Replace owner on subcontainers and objects".
Click Yes on any message boxes which pop-up.
Click Continue on any Access is Denied messages.
Click OK out of the final message box.
Click OK out of everything.

Tom

Hello Tom,

I will follow the instructions when I get home in a couple of hours. Thanks as always.

Cheers,

NLK

tom982 said:

Hi NLK,

Excellent! I'm glad that S256H problem has finally disappeared. Usually registry corruption changes one or two characters in a text string but the whole S256H value was different which confused me as I thought it couldn't possibly be corruption and put the difference down to a mistake at my end. But I took a shot in the dark, replaced the whole value with a clean one and it worked! Now I would like to fix the remaining missing payload files:

Code:

(f)    CSI Payload File Missing    0x00000000    prnts003.inf_loc    amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28    
(f)    CSI Payload File Missing    0x00000000    tsmxuui3.dll.mui    amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28

Navigate to the C:\Windows\winsxs\amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Under the Owner tab, click Edit.
Click "Other Users and Groups".
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK THREE times.
Click on the Permissions tab.
Under type Deny, single click on any entries and click Remove. (N.B.: There may not be any Deny entries, in which case just ignore this step. Just remove any that do exist)
Click OK.
Click Edit (now on the standard file Property window under the Security tab).
Click Add.
Click Advanced.
Click "Find Now".
Scroll down and double click on Everyone.
Click OK.
Single click on Everyone and then tick the "Full Control" box under Allow.
Click OK TWO times.

Now please extract and copy the attached files (prnts003.inf_loc and tsmxuui3.dll.mui) into C:\Windows\winsxs\amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28\

Finally:

Navigate to the C:\Windows\winsxs\amd64_prnts003.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_4a778fe507163f28\ folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Click on the Permissions tab (should be the default tab).
Click Change Permissions
Select and click Remove onthe ALLOW: Everyone entry you just added.
Click OK.
Go to Owner tab.
Click Edit.
Click "Other Users and Groups".
Paste in "NT Service\TrustedInstaller"
Click OK.
Put the check in "Replace owner on subcontainers and objects".
Click Yes on any message boxes which pop-up.
Click Continue on any Access is Denied messages.
Click OK out of the final message box.
Click OK out of everything.

Tom

Hello Tom,

I performed the steps outlined in your instructions. Should I restart the computer and run SURT?

Standing by for your reply.

Best Regards,

NLK