CBS Registry Errors

Drewmann69 said:

Whelp, thus far RegistryBooster 2011 found 95 Errors, fixed them all, but I still have the same results CSI and CBS results in the CheckSUR.log from running the "System Update Readiness Tool" shown below;

Summary:
Seconds executed: 229
Found 271 errors
CSI Missing Deployment Key Total count: 195
CBS Watchlist Package Missing Total count: 76

With that, I then ran;

SFC /verifyonly

but that came back clean...


So, I went ahead and ran the second Batch file to reset and reregister WU Components. All went perfectly fine with the possible exception of this at the end;

"C:\Windows\System32>bitsadmin.exe /reset /allusers
BITSADMIN version 3.0 [ 7.5.7600 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.
BITSAdmin is deprecated and is not guaranteed to be available in future versions
of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cm
dlets.
0 out of 0 jobs canceled.
C:\Windows\System32>"

0 out of 0 Jobs? Was at least hoping for something more like 0 out of 1 Jobs canceled...

So, then I Imported the BitsTransfer Module and ran an Get-Command -Module BitsTransfer, but there's nothing listed that sounds like it would "Reset" anything...

Rebooting... We'll see where I'm at next...

Hello!

I bring bad news. CBS Registry Errors are always hard to fix. It is possible to fix 1 or 2, but it takes a long time:

CSI Missing Deployment Key Total count: 195
CBS Watchlist Package Missing Total count: 76

Technically, both of these ARE fixable. But there is no automated fixing tool yet, and it will take one massively long time to fix all of those! It takes me about 15-20 minutes to do 2-5, let alone 271!

Also, this reset tutorial will NOT fix either of these errors. It does not reset where these corruptions exist.

However, a Repair Install WILL fix these corruptions (or at least, I can't guarantee, but I have never seen it fail on these errors yet)

Repair Install
Clean Install Windows 7

Richard

EDIT: SFC won't fix this either...

Thanks Richard/Niemiro. I know you're coming to me as the barer of "bad news", as I see by your explanations, but I definitely want you to know that I appreciate it. I was also beginning to think that maybe a repair of the OS would work, due to some things I've read on other similar Forums - but I know the process is far different from 2003/XP, so thank big-time for the Link. I'll try this suggestion and will Post back my results for this System, which is a 2008 R2 x64 Hyper-V Cluster Node. With that, I'm going to do a little more research and see if there's anything above the normal repair Process I might need to take into consideration.

Thanks again for the info and the honesty! Definitely appreciate it!
Drew

P.S. For my own knowledge, cause I'm sure I'll run across this again, what is the Process for repairing both Errors?

CBS Watchlist Package Missing
CSI Missing Deployment Key

I've read another Forum on this, but the English was terribly broken, and it was fairly obvious to me that the Author was probably a Developer; not a Systems Admin (meaning things that seemed obvious to the Author really required a lot further/clearer explanation). Please let us all know what the precise steps are to repair these errors.

...and thanks in advance!!!

Drewmann69 said:

Thanks Richard/Niemiro. I know you're coming to me as the barer of "bad news", as I see by your explanations, but I definitely want you to know that I appreciate it. I was also beginning to think that maybe a repair of the OS would work, due to some things I've read on other similar Forums - but I know the process is far different from 2003/XP, so thank big-time for the Link. I'll try this suggestion and will Post back my results for this System, which is a 2008 R2 x64 Hyper-V Cluster Node. With that, I'm going to do a little more research and see if there's anything above the normal repair Process I might need to take into consideration.

Thanks again for the info and the honesty! Definitely appreciate it!
Drew

P.S. For my own knowledge, cause I'm sure I'll run across this again, what is the Process for repairing both Errors?

CBS Watchlist Package Missing
CSI Missing Deployment Key

I've read another Forum on this, but the English was terribly broken, and it was fairly obvious to me that the Author was probably a Developer; not a Systems Admin (meaning things that seemed obvious to the Author really required a lot further/clearer explanation). Please let us all know what the precise steps are to repair these errors.

...and thanks in advance!!!

]

Hello Drew!

It is no problem at all! I am just wondering here...if you remember...would that "Developer" happen to go under the name of Flavius? Do you remember? Don't worry about it if it isn't on the top of your head! Don't worry about searching!

The Repair Install is indeed very different since Vista, but it should fix these issues. I don't have time right now to explain, but I will come back within the next couple of days, weekend at latest, and give you a run down on how to fix these two errors.

There are two main problems with fixing Registry Errors:

1: Unlike with replacing a corrupt file (where once you have fixed that corruption, all should be well) with a Registry Error, they are less certain. Often the fix is inspecific.

"CBS Watchlist Package Missing": For this error, there is no known guaranteed solution. I delete the item off the watchlist, and then try to reinstall it. Usually it works. But it is just hoping that Windows will be able to rebuilt it with some encouragement. But surely, there will be some times when deleteing it causes more problems to materialise. All down to luck. With very many errors in your case, something bad is likely to happen to at least one of them!

"CSI Missing Deployment Key": This basically involves rebuilding the key and all associated subkeys and values. There is no perfect source of data. In particular, I have to estimate the visibilities and package states for your computers.

Now here is the odd thing. I have done this reasonably often. I believe that I am getting better from experience (although I will never know if I get each individual visibility and state correct) And so it is logical to assume that I have made some mistakes. And yet not a single person has come back with problems, either down the road, or immediately. Not a single one. There is some unexplained discrepancy here! With so many for me to guess, you would have problems. And you don't want a known unstable registry on a server!

I will show you how to fix these later on.

But my advice would be this (very strong advice): Fix file corruptions, don't fix registry corruptions.

Richard

Hello again, Drew!

Lucky guess... No offence to him what-so-ever, as I see he's helped out a lot of folks on this Board (and probably other Boards as well). I just found it extremely hard to follow the train of thought, and I didn't want to assume anything and then botch things up even worse than what they already are... Hope no one's offended, as that was never my intention.

Don't worry. No one is offended :) He is actually a native Polish speaker, and so English isn't his first language (although it is a whole lot better than my Polish!) However, he does know his stuff, and he gave up much of his time to teach me much of what I now know, and since then I have spent a long time chatting with others on how they do things, and I even have an apprentice of my own now :)

At any rate, I did some more research, didn't find too much regarding repairing a 2008 R2 Hyper-V Cluster Node, so I attempted to Repair the Windows Installation (same between 2008 R2 and Windows 7). Unfortunately, after it rebooted it started the repair process then BSoD'ed. I rebooted and let it come up again. It started up, but then immediately rebooted itself (probably to roll things back) and came back up again to a Login Screen. I logged in and the following message popped up;

-----
Install Windows
This version of Windows could not be installed.
Your previous version of Windows has been restored, and you can
continue to use it. Before trying to install this version of Windows
again, check online to see if it is compatible with your computer.
Go to the Microsoft Website (www.microsoft.com) and search for
"upgrade advisor".
-----

That is very unfortunate. Your corruptions are just too big and too numerous.

With that, e-yah, I think I'm gonna have to pick through those Errors from the CBS\CheckSUR.log file one by one for the next few days/week(s) till I get through all of them;

CBS Watchlist Package Missing
CSI Missing Deployment Key

Now, I wanted to mention that per your previous statement;

"...basically involves rebuilding the key and all associated subkeys and values. There is no perfect source of data..."

I actually DO have the other Cluster Node (exact same HW, OS, SW and most [not all] same Roles/Features installed) that I can totally use as a reference for good Reg Keys / Files / etc. The other 2008 Cluster Node is completely clean when I run the Update Readiness Tool" on it. Please let me know if this helps at all.

I think that it is time to Clean Install/re-image this machine. I personally only extremely rarely recommend this, but I do today, and here are the reasons why:

As long as the installed updates, and more importantly same packages are installed, then it *might* work OK.

However, there are a whole lot more corruptions that SURT is showing. "CSI Missing Deployment Key Total count: 195" << That is bad. However, it doesn't hint at anything too bad underlying. 195 registry keys are missing. Just run of the mill!

"CBS Watchlist Package Missing Total count: 76" << This is bad. Occasionally, confusions occur, and prerequisite and superceding update installs go wrong, and things become orphaned. I tell you now that this should not happen to 76 updates. This means that actually, you have some serious file corruptions (file corruptions to such an extent that SURT wants to remove all traces and not repair!)

This machine is well and truly screwed up. Unimaginably screwed up. More than SURT is showing! Much more!

And thanks a MILLION for offering to put together some instructions for repairing the CBS and CSI errors! Definitely appreciated!!!

Still don't have time yet, but will over the weekend, just for your general interest and knowledge bank!

P.S. For anyone interested, I also wanted to make mention that even though the attempt to Repair Windows 2008 R2 failed and then reverted itself back to where it was before, I noticed that my Hyper-V Networking Redirected Adapter (Sharing the Connectivity of the Host and VMs) was orphaned, causing Clustering to fail as well. This was easily repairable via the Hyper-V Manager console's "Virtual Network Manager..." then resetting my Static IP info and rebooting. After that, Fail-over Clustering started working again... Just wanted to make mention of this...)

Thanks for the info!

Right, exact steps later, but for general interest, here is what I would do to fix this machine:

1) I would copy the entire CBS registry key from the other machine to the corrupted one. I would do an import, and not a replace.

2) I would then run SURT again. If lots of files suddenly turn up as missing, I would remove entries to those from the CBS key (I assume that we have now put onto watchlist what was never installed)

I would also remove any new orphans.

3) I would delete every original orphaned package from the registry.

4) I would then run SURT, and fix all errors.

5) I would then try Windows Update.

6) Windows Update still doesn't work, so I read C:\Windows\Logs\CBS\CBS.log and C:\Windows\WindowsUpdate.log, and fix all errors.

You aren't actually going to try this, are you? Please say no! Please reinstall now (you can keep a Virtual PC image to play with if you wish, but I would never be able to get this machine stable again)

Richard

"(The results of this off topic issue continued here: CBS Registry Errors)"


Brink! Thanks for moving this Thread! I was actually going to ask that someone move it, cause I felt it was going off Topic from the original as well. :)

Hi Niemiro!

Don't worry. No one is offended :) He is actually a native Polish speaker, and so English isn't his first language (although it is a whole lot better than my Polish!) However, he does know his stuff, and he gave up much of his time to teach me much of what I now know, and since then I have spent a long time chatting with others on how they do things, and I even have an apprentice of my own now :)

And that would definitely be me! Your new Apprentice, and I can't speek a word of Polish... LOL

That is very unfortunate. Your corruptions are just too big and too numerous.

Maybe it was a fluke thing... I'm definitely willing to try it once or twice more. Can't hurt at this point right?

I think that it is time to Clean Install/re-image this machine. I personally only extremely rarely recommend this, but I do today, and here are the reasons why:

As long as the installed updates, and more importantly same packages are installed, then it *might* work OK.

However, there are a whole lot more corruptions that SURT is showing. "CSI Missing Deployment Key Total count: 195" << That is bad. However, it doesn't hint at anything too bad underlying. 195 registry keys are missing. Just run of the mill

Good to know. I'm betting most, if not all, of those are harvestable from the other Cluster Node that's clean...

"CBS Watchlist Package Missing Total count: 76" << This is bad. Occasionally, confusions occur, and prerequisite and superceding update installs go wrong, and things become orphaned. I tell you now that this should not happen to 76 updates. This means that actually, you have some serious file corruptions (file corruptions to such an extent that SURT wants to remove all traces and not repair!)

I probably need to provide the full History here of what I've done since the PSU Failure... Interestingly enough, I wasn't getting all of these Errors until I manually repaired just one Reg Key as follows (also pasting in the CheckSUR.log Summary where appropriate);

CheckSUR Summary Before Manual RegKey repair;
-----------------------------------------------

"Summary:
Seconds executed: 995
Found 5 errors
Fixed 3 errors
CSI Manifest Missing Total count: 1
CSI Missing Pinned Component Key Total count: 1
Fixed: CSI Missing Pinned Component Key. Total count: 1
CSI Missing Identity Total count: 2
Fixed: CSI Missing Identity. Total count: 2
CSI Corrupt Identity Total count: 1
CSI Missing C Mark Total count: 1
Fixed: CSI Missing C Mark. Total count: 1
Unavailable repair files:
winsxs\manifests\wow64_microsoft-windows-shell-accessories_31bf3856ad3¶4e35_6.1.7600.16385_none_553f1735531e611b.manifest"

PLEASE NOTE CORRUPT CHARACTER AFTER "31bf3856ad3..."

CORRUPTED KEY;
----------------
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-shell-accessories_31bf3856ad3¶4e35_6.1.7600.16385_none_553f1735531e611b]
"identity"=hex:4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,53,68,65,\
6c,6c,2d,41,63,63,65,73,73,6f,72,69,65,73,2c,20,43,75,6c,74,75,72,65,3d,6e,\
65,75,74,f2,61,6c,2c,20,56,65,72,73,69,6f,6e,3d,36,2e,31,2e,37,36,30,30,2e,\
31,36,33,38,35,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,\
66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,\
72,63,68,69,74,65,63,74,75,72,65,3d,77,6f,77,36,34,2c,20,76,65,72,73,69,6f,\
6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
----------------

AGAIN, PLEASE NOTE CORRUPT CHARACTER AFTER "31bf3856ad3..."
ALSO, 3RD LINE DOWN IN STRING HAS " 65,75,74,f2," BUT SHOULD BE " 65,75,74,72,"


DELETED KEY AND REPLACED (VERIFING RIGHTS) WITH FROM OTHER NODE;
-----------
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-shell-accessories_31bf3856ad364e35_6.1.7600.16385_none_553f1735531e611b]
"identity"=hex:4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,53,68,65,\
6c,6c,2d,41,63,63,65,73,73,6f,72,69,65,73,2c,20,43,75,6c,74,75,72,65,3d,6e,\
65,75,74,72,61,6c,2c,20,56,65,72,73,69,6f,6e,3d,36,2e,31,2e,37,36,30,30,2e,\
31,36,33,38,35,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,\
66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,\
72,63,68,69,74,65,63,74,75,72,65,3d,77,6f,77,36,34,2c,20,76,65,72,73,69,6f,\
6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
-----------

After I did this, things started behaving normally in Windows, AND Windows Update finally Poped up and said it needed 20 Updates. However, I then scanned with SURT with the following results;

"Summary:
Seconds executed: 843
Found 99 errors
CBS Watchlist Package Missing Total count: 99"

Then I applied ~18 of the Updates that MS checked by default (2 for .NET 3.5 SP1 HotFixes were not checked). That's when the CBS Count dropped to ~78 (oddly enough).

I then applied the .NET 3.51 SP1 HotFix Updates and that's when the CBS count dropped to 76 and I started seeing the 195 CSI Errors...

"Summary:
Seconds executed: 302
Found 271 errors
CSI Missing Deployment Key Total count: 195
CBS Watchlist Package Missing Total count: 76"

Right, exact steps later, but for general interest, here is what I would do to fix this machine:

1) I would copy the entire CBS registry key from the other machine to the corrupted one. I would do an import, and not a replace.

2) I would then run SURT again. If lots of files suddenly turn up as missing, I would remove entries to those from the CBS key (I assume that we have now put onto watchlist what was never installed)

I would also remove any new orphans.

3) I would delete every original orphaned package from the registry.

4) I would then run SURT, and fix all errors.

5) I would then try Windows Update.

6) Windows Update still doesn't work, so I read C:\Windows\Logs\CBS\CBS.log and C:\Windows\WindowsUpdate.log, and fix all errors.

You aren't actually going to try this, are you? Please say no! Please reinstall now (you can keep a Virtual PC image to play with if you wish, but I would never be able to get this machine stable again)

Richard

Whelp, LOL... I guess I look at it this way; I've got ~2TB of Data that needs to be moved off the C: Drive before I can Live Migrate VMs over to the surviving Cluster Node and Evict this Cluster Node, blow it away and start over. Then it will be a heck of a LOT of work to rebuild this Machine, but if it needs it then I'll have to do it. Probably one weekend when the Weather starts getting bad around here again... But in the meantime, I'd like to at least find out what a challenge I'm up against here - definitely with respect to being able to carry this knowledge forward to help others in the future (others who hopefully aren't so injured - lol). With that, THANK YOU BIG TIME for all your help, guidance and for taking the time out of your schedule to write the steps up (especially over the weekend man - THANKS)!!! And please let me know if you would like me to upload or paste any Logs or anything.

And in the meantime, I will Migrate the ~2TB from C: to D: and re-share it. One Local VM that I need to Migrate to CSVs as well. Then, I will definitely attempt to Repair Windows a couple more times to see if just maybe I'll get lucky... If not, then worst case scenario, I'll be in a much better position to rebuild if it definitely comes down to that... LOL What a mess... This stuff just take way too long any more... lol


Thanks,
Drew

Oh, one more (probably obvious) thing I should mention is that Server Manager will not open. I NOW crashes with the following Error;

"Microsoft Management Console
Microsoft Management Console has stopped working
A problem caused the program to stop working sorrectly.
Please close the program.
Close the program"

Before this mess (right after the PSU died) I could open Server Management, but it would not show anything (error out) in Features or Roles.

Hello Drew!

Since you are serious about fixing this machine, I am more than willing to help :) It will be a good challenge, and I will learn some new stuff, I am sure.

Please can you provide me with the logs?

A Repair Install doesn't just fail randomly. So it still won't install. However, if we fix it up to nearly perfect, and then do a Repair Install, we might just be able to fix this.

Also, before we start, I want to see which packages are corrupt. If they all originate from a few updates (1 update can contain many packages) we might be able to do an uninstall of that update, and then reinstall it (there are FAR more powerful ways of uninstalling an update than through Add/Remove programs :P)

I will have a look through your logs, and tell you exactly my plan of attack.

Well done on fixing that registry error. Good job!

Please create a new folder on your Desktop called LOGS, and paste in the C:\Windows\Logs\CBS\ folder, and C:\Windows\WindowsUpdate.log, right click on that new LOGS folder > Send to > Compressed (zipped) folder, and upload that here.

Thanks a lot!

Richard

Hmmm. What words of Polish do I know? A few, actually:

tak: yes
nie: no
dziękuję: thank you
babcia: grandmother
dziadek: grandfather
dom: house
knieja: forest

Right, I have run out! I think that I have spelled them correctly...