SBS 2008 80070002 Window update error

S

Steff

Member
Joined
Jan 16, 2013
Posts
14
Hi guys,

I have been dumped this server to support and cannot perform a windows update on it, after looking around the net and following the Microsoft tech net articles the problem is still as bad as it was.

I have included the

CheckSUR.log

Code: 
=================================Checking System Update Readiness.
Binary Version 6.0.6002.22574
Package Version 17.0
2013-01-15 14:00


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)    CSI Missing Identity    0x00000000    appid    997b39ff514..133943f107e_31bf3856ad364e35_6.0.6002.18051_08a93a15f5dabdc9    
(f)    CSI Missing Identity    0x00000000    appid    eb2417eefc6..a7f6dd8927d_31bf3856ad364e35_6.0.6002.22191_ae6f834625c1eb6d    
(f)    CSI Corrupt Component Keyform    0x00000000    identity    amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.0.6002.18051_none_da82f09f183625f3    identity and keyform do not match; keyform is wrong.
(f)    CSI Missing Identity    0x00000000    appid    9cba5d04767..a4348dc9c83_31bf3856ad364e35_6.0.6001.18247_5be6b4165d74d60a    
(f)    CSI Missing Identity    0x00000000    appid    250114d8f47..7bb1e4f86c1_31bf3856ad364e35_6.0.6002.18024_2b9fc7983ccacae0    
(f)    CSI Missing Identity    0x00000000    appid    aefd71f6096..5c7649e08e6_31bf3856ad364e35_6.0.6001.18272_f69d94185413bc32    
(f)    CSI Missing Identity    0x00000000    appid    f6c1f8e4567..ba11bdd0cea_31bf3856ad364e35_6.0.6001.22447_baf0352d04434572    
(f)    CSI Missing Identity    0x00000000    appid    91c5988f269..2a20c6b443b_31bf3856ad364e35_6.0.6002.22223_f9e1c2c8b50e7d0f    
(f)    CSI Missing Deployment Key    0x00000000    01e8e8841df..169ca4d40fa_31bf3856ad364e35_6.0.6002.22200_2946fa3a7ba0ec6a    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    ff946ff4168..2751f30be34_31bf3856ad364e35_6.0.6001.18311_c02d263a900ebc65    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    a1ce75f878c..ad04b66bbe8_31bf3856ad364e35_6.0.6001.18272_6731fd1001ef50f7    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    eafda48660c..438a0b1606a_31bf3856ad364e35_6.0.6001.18311_6ef218342fb41d55    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    08267af3f9e..31a34bd978a_31bf3856ad364e35_6.0.6001.22497_a6aa4a80e79e7b47    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    e5ae7e64e77..c66fae2c37c_31bf3856ad364e35_6.0.6001.18311_cf57ff2c6df1120a    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    b3e606be9fb..245a45ff882_31bf3856ad364e35_6.0.6002.18051_18447e23d775cf50    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    3a6ca4ae7d7..362d30452b5_31bf3856ad364e35_6.0.6001.18311_5c57b46756115582    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    04fe2f538bc..dfd9733e2aa_31bf3856ad364e35_6.0.6002.18091_c1e2a386c6912288    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    796da4c4ea2..f77698dae63_31bf3856ad364e35_6.0.6002.22200_72ad617e4eb913ba    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    c3afff87fd8..0e2e17b4227_31bf3856ad364e35_6.0.6002.18051_e4c39abc8548c32a    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    a3f0769f6e5..95a6d000735_31bf3856ad364e35_6.0.6001.22497_21734bd0593c1c96    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    e5a8c4b9d08..8e25ed9340d_31bf3856ad364e35_6.0.6001.18311_91e3e83b2a42b7a8    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    ed27934c872..58e4665c8a0_31bf3856ad364e35_6.0.6001.18311_dc6b6b862ebb5d07    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    3eca8ca0ea8..f116fafb09f_31bf3856ad364e35_6.0.6001.22497_b22158c11e9534e6    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    9f2370063ee..f2ae5bf244e_31bf3856ad364e35_6.0.6001.22497_3b1e6deff6abacae    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    c71478d496f..230b6849466_31bf3856ad364e35_6.0.6002.18091_3cda47afcf8bc666    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    e10f1ac00d0..82721e4822a_31bf3856ad364e35_6.0.6001.22497_d0032e43b0636f07    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    56ffac6c905..fe523b12113_31bf3856ad364e35_6.0.6002.22152_c8d402b0ff16cae0    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    4058ba680d1..82988b65393_31bf3856ad364e35_6.0.6002.18091_9cda14d0fb690a03    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    3bd4e74ca1f..1fec0516711_31bf3856ad364e35_6.0.6001.22497_805bb396bfda15df    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    8d864dcbcc8..12485f24cf8_31bf3856ad364e35_6.0.6001.22497_18ebe2a47ac1f478    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    43dbe06136f..250ad85560d_31bf3856ad364e35_6.0.6002.22152_43860badf19ece66    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    8cbdefc29cc..b4a848d509c_31bf3856ad364e35_6.0.6002.18091_4669520f1a450ec5    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    ecb6f129171..fc2cab3e0b3_31bf3856ad364e35_6.0.6002.22200_298acbcab6f17efe    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    7b942d00bdc..3d8288250d6_31bf3856ad364e35_6.0.6001.18311_50adfe0e373ff632    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    4e2d9301c25..5bea6b05e70_31bf3856ad364e35_6.0.6002.22200_d31dd0cb972815e6    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Deployment Key    0x00000000    33cf990fe6d..47bb87a65f7_31bf3856ad364e35_6.0.6002.22200_71b8e56a88c4e618    HKLM\Components\CanonicalData\Deployments    
(f)    CSI Missing Winning Component Key    0x00000000    amd64_microsoft-windows-gdi_31bf3856ad364e35_6.0.6001.18272_none_05a808e8131abf15        
(f)    CSI Missing Winning Component Key    0x00000000    wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.0.6002.18051_none_8a3af92c3f4efb97        
(f)    CSI Missing Winning Component Key    0x00000000    amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.0.6002.18051_none_7fe64eda0aee399c        
(f)    CSI Missing Winning Component Key    0x00000000    x86_microsoft-windows-font-embedding_31bf3856ad364e35_6.0.6001.18272_none_b57678331f2ab896        
(f)    CSI Missing Winning Component Key    0x00000000    wow64_microsoft-windows-gdi_31bf3856ad364e35_6.0.6001.18272_none_0ffcb33a477b8110        
(f)    CSI Missing Winning Component Key    0x00000000    amd64_microsoft-windows-font-embedding_31bf3856ad364e35_6.0.6001.18272_none_119513b6d78829cc        


Summary:
Seconds executed: 825
 Found 42 errors
  CSI Missing Deployment Key Total count: 28
  CSI Corrupt Component Keyform Total count: 1
  CSI Missing Identity Total count: 7
  CSI Missing Winning Component Key Total count: 6
Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

and attached it, any help would be wonderful!

View attachment CheckSUR.log
 
Hello Steff, and welcome to Sysnative :)

I will get a reply to you as soon as possible. Unfortunately, we are absolutely snowed under with work at the moment, and your 42 errors might take me or Tom a few days to put a fix together for.

I am very sorry about this, and I thank you for your patience.

Richard
 
Hello again Steff :)

Can you please do one final step for me before I provide you with a fix:

Export CBS folder

  1. Click the Start button
    StartButton_16x16.gif
    then click Computer.
  2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
  3. Find and double click on the Logs folder.
  4. Right-click on the CBS folder, and select Copy.
  5. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
  6. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
  7. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.

Thank you!

Richard
 
Hi Richard,

I cant thank you enough for the time and effort you put in on top of your work load, its a real pain having to support a server that was dumped in my lap broken.

View attachment CBS.zip
 
Steff said:
Hi Richard,

I cant thank you enough for the time and effort you put in on top of your work load, its a real pain having to support a server that was dumped in my lap broken.

View attachment 3057
Click to expand...

Hello Steff :)

This is going to be a multi-part fix. You will not notice any immediate improvement after just the first post or two, but hopefully after three or four we will have you back up and running again. The fact that this is a server adds a few complications, but I am hoping that we can work around those, rather than hit a dead end. Anyway, won't find out until we try :)

I am just putting together the first registry fix to cover the bulk of your corruptions, and then we tweak until we get it perfect. While I am making that, I would like to deal with one of the more complicated corruptions.

First, please use an Elevated Command Prompt: How to start an Elevated Command Prompt in Windows 7 and Vista

and run:

reg export HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.0.6002.18005_0028c5a9\ComponentFamilies\x86_microsoft-windows-p..-wsman-pluginworker_31bf3856ad364e35_none_9a4e9c942522ba6c %userprofile%\Desktop\RegistryExport1.reg

Please right click on the created .reg file > Edit (to open in Notepad), and check it came out OK. Then right click on it > Send to > Compressed (zipped) folder, and upload it here.

Next, please browse to that key in regedit, and open up its subkeys. You should see one which may look like this: ㉦㘵瀡灳畬楧睮牫搮汬 (not sure whether you will be able to see this, but anyway, it looks like Chinese or similar characters).

Basically, that shouldn't be like that. Now, before I see the registry export, I cannot be quite sure of how this key *should* look.

Please note down and send me the contents of that key if it hasn't shown up nicely in the registry export.

I will let you know what to do with it later. You are probably going to have to fix it manually, because it will trip up some of the tools we use, but I can't yet tell you what the good data is for you to correct it yet. All in good time :)

Your next set of instructions will come as soon as I can.

Richard
 
Hello again Steff :)

I did say this one was going to be tricky! Can you please use regedit to delete that key. I will re-create it later.

If you can't delete it, please let me know. Then we might have to crack open some more powerful tool. If necessary, I will take the registry hive to my computer and manually repair the binary.

Deleting unopenable keys can be difficult. But it can be done.

Richard
 
No problem.

Please download the Freeware RegBak from here: Acelogix Software - Download products

Navigate to C:\Windows\RegBak\{Date}\ and copy the COMPONENTS file to your Desktop.

Now right click on it > Send to > Compressed (zipped) folder.

Then please upload it to your favourite file sharing website (it will be too big for here). If you have a Microsoft Account, SkyDrive could be a good choice: https://skydrive.live.com/, but any other will do just fine.

Thank you!

Richard
 
Hi Steff,

If I may jump in to your Thread.....:grin1:

Do you have WSUS configured in your SBS 2008 Server? I am managing an SBS 2011 Server and I have WSUS configured and no issues so far. Having WSUS configured is quite helpful, it also does Windows Updates all Client PCs in your network but a simple GPO setup is needed.
 
2xg said:
Hi Steff,

If I may jump in to your Thread.....:grin1:

Do you have WSUS configured in your SBS 2008 Server? I am managing an SBS 2011 Server and I have WSUS configured and no issues so far. Having WSUS configured is quite helpful, it also does Windows Updates all Client PCs in your network but a simple GPO setup is needed.
Click to expand...

Yea the server was originally configured with WSUS, but this was also broken (not updating server/clients).
 
Hello Steff :)

I am still working on this. I also live in the UK, and spent the weekend digging snow also. Currently trying to clear my large backlog of work.

Windows Update will not work again until the errors found by SURT have been fixed. I will try to get a reply ASAP, although the fact that you have a server makes my job slightly harder.

Richard
 
Hi Richard,

thanks for the response, no pressure just the very idea that it might be fixable is fine with me because its either this or a reinstall!

and I very much appreciate it and shall buy you a beer some day !
 
Have you also tried all the suggestions here on how to repair WSUS?

One thing that I've always done especially knowing that dealing with a Server can be cumbersome, is contacting Microsoft. Since this is WU related issue you will get free assistance from them. Just my 2 cents of course.
 
Last edited:
I cannot even access role manager within the server as I get the same error as the posted windows update error, so there is next to no chance of getting WSUS installed as the server currently is.
 
Hi....are you referring it to the Server Manager or only when you click on Roles, see image attached (snip from my SBS Server Manager)?
I cannot even access role manager within the server as I get the same error as the posted windows update error
Click to expand...
SBS2011-Server Manager.PNG
Is your SBS Console also affected? Is this fully functional?
Are all SBS Services needed all Started?
Any other Server Roles (e.g....IIS, File Services etc) how about SQL or Exchange Server if you have this installed affected and not working?

Sorry for the questions...:grin1:
 
Last edited:
@2xg, unfortunately, this is not a simple configuration problem. The logfile in the first post shows 42 corruptions, and these are what is causing the problem. The portions of registry shown to be corruption hold the current servicing state, simplistically what updates are installed, so that Windows Update can work out what to download and install. When this becomes corrupt, nothing Windows Update related, not the normal interface or SURT, or sometimes Add/Remove Windows Features, etc. etc., can work.

@Steff, unfortunately, I am unable to fix this. Most of the corrupt components are SBS specific, and none of my normal techniques aimed at client OSes work. Although I downloaded and updated a trial of SBS 2008, it did not have all of the data on it I need for a fix. I was missing data for just a few components, but unless I can find everything, Windows Update will never work again. So the fact that I can fix 90%+ is useless. Only 100% will make a difference.

I am really sorry it came to this, but I just cannot track down all of the data I need for a fix.

The only suggestion I can make now is a Repair Install: https://www.sysnative.com/forums/wi...-install-windows-windows-7-windows-vista.html

Richard
 
Hi Niemiro,

Thanks for your feedback, I truly understand what's going on here. I have been dealing with SBS Server since the 2003 version and I've seen/troubleshoot the worst scenarios that could happen, we are now using SBS 2011 Server. Post# 17 are questions for Steff to see of those Roles and Apps and affected and if they are, this concerns the entire SBS which can be resolved by either calling Microsoft or an SBS Consultant if the OP has Technet or MSDN subscription, the fees can be $0 up to $260 per incident call and they will be able to fix this thru a remote session. I would highly recommend calling Microsoft bec. they have experts and excellent customer service, this is from my experience dealing with them
 
2xg said:
Hi Niemiro,

Thanks for your feedback, I truly understand what's going on here. I have been dealing with SBS Server since the 2003 version and I've seen/troubleshoot the worst scenarios that could happen, we are now using SBS 2011 Server. Post# 17 are questions for Steff to see of those Roles and Apps and affected and if they are, this concerns the entire SBS which can be resolved by either calling Microsoft or an SBS Consultant if the OP has Technet or MSDN subscription, the fees can be $0 up to $260 per incident call and they will be able to fix this thru a remote session. I would highly recommend calling Microsoft bec. they have experts and excellent customer service, this is from my experience dealing with them
Click to expand...

Thank you very much for your input. I did not intend to undervalue your advice in any way, and I sincerely hope that no offense was caused. My apologies.

Richard
 
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