Missing Deployment Key

[jayrod12]

Hey guys,

With all the issues I'm having with my work computer and windows update(being taken care of in another thread) I decided to run SURT on a colleagues new computer.

The CheckSUR log shows 4 missing deployment keys, I'm assuming this is an easy fix I'm just not sure how to do it myself.

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 19.0
2013-08-16 14:44
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Missing Deployment Key 0x00000000 policy.8.0...vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_4db266e67dd280ef HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_03ca5532205cb096 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 policy.8.0...vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_6b86c0e9b0196766 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_3b0e32bdc9afe437 HKLM\Components\CanonicalData\Deployments 
Summary:
Seconds executed: 882
 Found 6 errors
  CSI Missing Deployment Key Total count: 4
  CBS MUM Corrupt Total count: 2
Unavailable repair files:
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat

Thanks in advance,

 

[tom982]

Hi Jared,

This one is a lot nicer than your other log!

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.

Tom

 

[jayrod12]

Tom,

See attached. And in case Richard is looking at this too, I first attempted to run the script using SFCFix version 2 because that's what I had already on the desktop however it never processed the script. It just sat at the processing directive stage for quite a bit.

I reran the script using the original SFCFix and it ran fine.

On the topic of the other thread, Richard mentioned you guys might have something to try. Any idea when you guys want to try it?

Thanks,

Jared

SFCFix version 1.5.7.0 by niemiro.
Start time: 2013-08-19 13:08:46.860
Using .txt script file at C:\Users\WIN7PRO\Desktop\SFCFix.txt
 

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\policy.8.0...vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_4db266e67dd280ef
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_03ca5532205cb096
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\policy.8.0...vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_6b86c0e9b0196766
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_3b0e32bdc9afe437
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\policy.8.0...vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_4db266e67dd280ef.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_03ca5532205cb096.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\policy.8.0...vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_6b86c0e9b0196766.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_3b0e32bdc9afe437.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 1.5.7.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2013-08-19 13:08:48.436
----------------------EOF-----------------------

 

[niemiro]

Hello Jared :)

Tom is currently away on a last minute holiday, so you've got me again

Thanks for letting me know about this problem with SFCFixVersion2. I shall look into possible reasons why it hung.

However, that looks to have dealt with all of your issues. I think you've probably had this explained to you already in your other thread, or by SFCFix or something, but those IE10 corruptions in this SURT log are nothing to worry about. SURT was created before IE10, and is not entirely compatible with IE10 - it detects as corrupt some files which are not corrupt. So, the long and short of it is that this problem is fixed as far as I am concerned.

Does your colleague's Windows Update now work? If not, please upload a full set of CBS logs.

Thank you.

Richard

P.S. I'm still working on the fix for your computer. Whilst we have an idea, the coding was not simple. However, it is now very nearly done.

 

[jayrod12]

Hey Richard,

Thanks for jumping in on this.

Windows update does work now. However just for shits and giggles I ran SURT again. Log attached.

I'm now well aware of the IE10 junk and it's problems with SURT. Anyway, the fix allowed windows update to run however it appeared to cause other issues, or at least uncovered other issues.

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 19.0
2013-08-20 07:58
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Mismatched Identity 0x00000000 appid policy.8.0...vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_6b86c0e9b0196766 appid and keyform do not match; appid is wrong.
(f) CSI Corrupt Identity 0xC0150019 Microsoft.VC80.OpenMP, microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.4053_3b0e32bdc9afe437 Bad identity
(f) CSI Mismatched Identity 0x00000000 appid policy.8.0...vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_4db266e67dd280ef appid and keyform do not match; appid is wrong.
(f) CSI Corrupt Identity 0xC0150019 Microsoft.VC80.MFCLOC, microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.4053_03ca5532205cb096 Bad identity
Summary:
Seconds executed: 482
 Found 6 errors
  CSI Corrupt Identity Total count: 2
  CSI Mismatched Identity Total count: 2
  CBS MUM Corrupt Total count: 2
Unavailable repair files:
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat