CBS Registry Errors

[Drewmann69]

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

EDIT:
------

No difference;

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


If all the First Batch file does is wipe out the WU History from Programs & Features then I'm not certain that will help the situation that I'm seeing with the "Update Readyiness Tool". If I'm mistaken, or if you or anyone have/has any other suggestions for me to try please let me know. I'd really like to get this fixed and then update to SP1 for 2008 R2. In turn, I'll definitely continue to Post my findings. I haven't been able to fine anything solid Google'n this yet...

 

[niemiro]

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)

http://www.sevenforums.com/tutorials/3413-repair-install.html
http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Richard

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

 

[Drewmann69]

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!!!

 

[niemiro]

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

 

[Drewmann69]

Lucky guess... No offense 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 intension.

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".
-----

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. And thanks a MILLION for offering to put together some instructions for repairing the CBS and CSI errors! Definitely appreciated!!!

Thanks,
Drew

EDIT:
------
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...)

 

[niemiro]

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

 

[Drewmann69]

"(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.

 

[Drewmann69]

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... :devil: This stuff just take way too long any more... lol


Thanks,
Drew

 

[Drewmann69]

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.

 

[niemiro]

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 )

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

 

[Drewmann69]

Awesome Niemiro!!!

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 )

I'm right on board with all of this! Here are (should be anyway) all of the Logs you've requested. For security purposes, COMPUTER, DOMAIN and USERNAME(S) have been blocked out where they exist.

dziękuję,
Drew

 

[niemiro]

No problem, Drew! This is a fascinating challenge!

However, I want to delay things *again*, and first fix another small corruption (very much like the one you found)

From your CBS.log (x many)

2011-07-01 17:33:33, Info                  CBS    Invalid character in name: Package_2_for�KB2345316 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Error                 CBS    Failed to validate component name: Package_2_for�KB2345316 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Error                 CBS    Failed to load identity from attributes. [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to create identity from string: Package_2_for�KB2345316~31bf3856ad364e35~amd64~~6.1.1.6. [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to get identity from key form: Package_2_for�KB2345316~31bf3856ad364e35~amd64~~6.1.1.6 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to populate children. [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to initialize internal package for package: Microsoft-Hyper-V-Common-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Delay load failed for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Error                 CBS    Delay Initialization Failed [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Session: 30160950_2267298141 initialized by client WindowsUpdateAgent.
2011-07-01 17:33:33, Info                  CBS    Invalid character in name: Package_2_for�KB2345316 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Error                 CBS    Failed to validate component name: Package_2_for�KB2345316 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Error                 CBS    Failed to load identity from attributes. [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to create identity from string: Package_2_for�KB2345316~31bf3856ad364e35~amd64~~6.1.1.6. [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to get identity from key form: Package_2_for�KB2345316~31bf3856ad364e35~amd64~~6.1.1.6 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to populate children. [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Failed to initialize internal package for package: Microsoft-Hyper-V-Common-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Info                  CBS    Delay load failed for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x80070057 - E_INVALIDARG]
2011-07-01 17:33:33, Error                 CBS    Delay Initialization Failed [HRESULT = 0x80070057 - E_INVALIDARG]

Could you have a look in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect

and basically go hunting for: Package_2_for�KB2345316~31bf3856ad364e35~amd64~~6.1.1.6

and if you find it, change it to an underscore.

I think that this corruption will be located there...hopefully you will be able to find it!

Richard

 

[Drewmann69]

Good catch my Friend! Can't believe I missed that one, as it was right in front of my FACE! LOL Sometime we look too deep...

At first I searched the entire leg of the Registry that you mentioned, but everything looked fine. I then searched the entire HKLM for the string "KB2345316~31bf3856ad364e35~amd64~~6.1.1.6" and found / fixed it under the following;

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Hyper-V-Common-Drivers-Package~31bf3856ad364e35~amd64~~0.0.0.0]
"Package_for_KB2345316~31bf3856ad364e35~amd64~~6.1.1.6"=dword:00000002
"Package_for_KB2345316_RTM~31bf3856ad364e35~amd64~~6.1.1.6"=dword:00000002
(FIXED HERE) "Package_2_for_KB2345316~31bf3856ad364e35~amd64~~6.1.1.6"=dword:00000002
"Package_for_KB2525835~31bf3856ad364e35~amd64~~6.1.1.2"=dword:00000002
"Package_for_KB2525835_RTM~31bf3856ad364e35~amd64~~6.1.1.2"=dword:00000002
"Package_8_for_KB2525835~31bf3856ad364e35~amd64~~6.1.1.2"=dword:00000002
"Package_for_KB2525835_SP1~31bf3856ad364e35~amd64~~6.1.1.2"=dword:00000002
"Package_2_for_KB2525835~31bf3856ad364e35~amd64~~6.1.1.2"=dword:00000002


Seems to be fine everywhere else in the reg (about ~55 hits total). I also ensured the COMPONENT leg of the Registry was loaded by running Windows Update and scanning for Updates - just to be sure nothing was screwed up in there as well.

Repaired, rebooted, ran SURT (it fixed 1 Error this time around), re-ran SURT again and here's the Post of the CheckSUR.logs after that. (NOTE: I had to take Ownership and give Administrators full rights, but reversed this back to SYSTEM as Owner and Read-only for Admins after the fact.)

Server Manager is now FINALLY working properly for Role and Features!!! So we made progress!!! Still only one "Important" update in Windows Update (2008 R2 Service Pack 1), and two "Optional" Driver Updates that I care nothing about at this point...

THANKS BRUTHA!!!
Drew

 

[Drewmann69]

P.S. For giggles, I re-ran RegistryBooster 2011 and it found 9 System Related Reg Errors. Out of these, 8 are "System Software Settings" and 1 is "ActiveX, OLE, COM sections". I'm holding off telling it to repair these unless you agree. My thinking is why not let it fix 'em, but I don't want to let it repair these if you're not on board with it Niemiro. Please let me know...

Drew

 

[niemiro]

Very well done! I really didn't know where that corruption was going to be, so couldn't be of much help, so well done

Well, I bring important news. One of the reasons why I sent you away to fix that was because I wanted more time to think over this case. And I believe that I have now worked out exactly what is causing this issue, and so many corrupt registry keys/values.

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 )

I was looking through, trying to make sense of so many different errors (go through the CBS.persist.logs, and you will see so many more, and varied errors) Could I find a pattern...yes!

All of the packages do not come from a few discrete updates, actually, they all come from core Windows. The only thing I can think of for this, is a badly failed SP1 update. Basically, those components were in the process of being updated to SP1, and then SP1 fails/crashes/something, and they all become corrupt. That is why you have so many corrupt registry keys/values, and that is why it is those particular registry keys/values.

This leads to a lot of questions (and one of those questions will, I am sure, be "What is the fix!")

Do I want to fix all of these (which means removing package from package watchlist). Do I want to fix just the missing Deployment Keys? If I remove all of these Core (but not necessarily critical) components, are there SP1 components to stand in their place. Would I cause more harm by removing them.

Taking as a fact (unless you have a better theory) that SP1 is half installed, and half not installed (rather than not installed after multiple failures) do I want to get to a state of SP1 installed, or a state of SP1 not installed.

Difficult questions! For better or worse, I have made up my mind. I wish to try to uninstall SP1, (which avoids much of the possibly dangerous removing or not removing of package watchlist components) and then with SP1 uninstalled, I plan to do a Repair Install. After that, we shall re-run SURT, I shall go through the logs, and then if all looks well, try SP1 again.

But why did SP1 fail? If these errors are caused by a failure of SP1, what caused SP1 to fail. IMPORTANT QUESTION: Did you PSU fail while installing SP1, and therefore cause these corruptions, or did it fail earlier, causing a corruption which failed SP1? I went through the other logs...

and each of these had many repetitions:

2011-05-28 06:42:12, Error                 CSI    00000a2c (F) STATUS_OBJECT_NAME_NOT_FOUND #70972327# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xe2cf30->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[213]"\Registry\Machine\COMP\u804fNENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-bubbles.resources_31bf3856ad364e35_en-us_51f2b3972f87c6d0\v!6.1.7600.16385"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14865144 (0x00e2d2f8))[gle=0xd0000034]
2011-05-28 06:42:12, Error                 CSI    00000a2d@2011/5/28:10:42:12.214 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2011-05-28 06:42:12, Error                 CSI    00000a2e (F) STATUS_OBJECT_NAME_NOT_FOUND #70972326# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0xe2d390, key = NULL, disp = (null))[gle=0xd0000034]
2011-05-28 06:42:12, Error                 CSI    00000a2f (F) STATUS_OBJECT_NAME_NOT_FOUND #70972321# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
2011-05-28 06:42:12, Error                 CSI    00000a30 (F) STATUS_OBJECT_NAME_NOT_FOUND #70907804# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
2011-05-28 06:42:12, Info                  CBS    Failed to get CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2011-05-28 06:42:12, Error                 CBS    Failed to initialize store parameters with boot drive:  and windows directory:  [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2011-05-28 06:42:12, Error                 CSI    00000a31 (F) STATUS_OBJECT_NAME_NOT_FOUND #71046189# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xe2cf30->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[213]"\Registry\Machine\COMP\u804fNENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-bubbles.resources_31bf3856ad364e35_en-us_51f2b3972f87c6d0\v!6.1.7600.16385"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14864080 (0x00e2ced0))[gle=0xd0000034]
2011-05-28 06:42:12, Error                 CSI    00000a32@2011/5/28:10:42:12.698 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]

^^ This one disappeared as quickly as it came. I will investigate this only as required.

2011-05-21 12:29:29, Info                  CBS    Obtained poqexec from Cbs key. C:\Windows\System32\poqexec.exe /display_progress \SystemRoot\WinSxS\pending.xml
2011-05-21 12:29:29, Info                  CBS    Removed poqexec from Cbs key.
2011-05-21 12:29:29, Info                  CBS    Removed CCP impactful-commit disabling value.
2011-05-21 12:29:29, Info                  CBS    Running poqexec with: C:\Windows\System32\poqexec.exe /noreboot /transaction 182068 /display_progress \SystemRoot\WinSxS\pending.xml
2011-05-21 12:29:29, Info                  CBS    Waiting for poqexec.exe to complete...
2011-05-21 12:29:29, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 3. Percent progress: 15.
2011-05-21 12:29:34, Info                  CBS    Waiting for poqexec.exe to complete...
2011-05-21 12:29:39, Info                  CBS    Waiting for poqexec.exe to complete...
2011-05-21 12:29:44, Info                  CBS    Waiting for poqexec.exe to complete...
2011-05-21 12:29:45, Info                  CBS    SQM: Reporting poqexec status with status: 0xc0000043, failed file: install.ins, interfering process: , context: Shutdown, first merged sequence: 200
2011-05-21 12:29:45, Info                  CBS    SQM: Upload requested for report: PoqexecStatus, session id: 142861, sample type: Standard
2011-05-21 12:29:45, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2011-05-21 12:29:45, Info                  CBS    Failure in poqexec.exe while processing updates. [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
2011-05-21 12:29:45, Info                  CBS    Set the CCP impactful-commit disabling value
2011-05-21 12:29:45, Error                 CBS    Shtd: Failed while processing critical primitive operations queue. [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
2011-05-21 12:29:45, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 3. Temporary Rollback.
2011-05-21 12:29:45, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 3. Temporary Rollback.

^^ Please may you create a new logs folder, and this time add

C:\Windows\Winsxs\Pending.xml* (basically, every Pending.xml, if any)
C:\Windows\winsxs\poqexec.log
C:\Windows\winsxs\cleanup.xml

Some of the above may not exist. Just whatever exists, please

2011-05-13 03:29:34, Error                 CSI    00000012 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #112011# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150004]
2011-05-13 03:29:34, Error                 CSI    00000013@2011/5/13:07:29:34.469 (F) d:\w7rtm\base\wcp\componentstore\csd_winners.cpp(550): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirectTransaction::PerformChangeAnalysis expression: m_Analysis->AllCompositionsWereFound()
[gle=0x80004005]
2011-05-13 03:29:34, Error                 CSI    00000014 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #112010# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150004]
2011-05-13 03:29:34, Error                 CSI    00000015 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #112009# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150004]
2011-05-13 03:29:34, Error                 CSI    00000016 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #112008# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0150004]
2011-05-13 03:29:34, Info                  CSI    00000017 TLC operation Install (0) incomplete for [Microsoft-Windows-ServerDesktopExperience-Deployment, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral]), missing compositions
    Microsoft-Windows-Shell-Accessories, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2011-05-13 03:29:34, Error                 CSI    00000018 (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #165515# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150004]
2011-05-13 03:29:34, Error                 CSI    00000019@2011/5/13:07:29:34.874 (F) d:\w7rtm\base\wcp\componentstore\csd_winners.cpp(550): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirectTransaction::PerformChangeAnalysis expression: m_Analysis->AllCompositionsWereFound()
[gle=0x80004005]
2011-05-13 03:29:34, Error                 CSI    0000001a (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #165514# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150004]
2011-05-13 03:29:34, Error                 CSI    0000001b (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #165513# from CCSDirectTransaction::GenerateComponentChangeList(...)[gle=0xd0150004]
2011-05-13 03:29:34, Error                 CSI    0000001c (F) STATUS_SXS_ASSEMBLY_NOT_FOUND #165512# from Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(...)[gle=0xd0150004]
2011-05-13 03:29:34, Error                 CSI    0000001d (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #108847# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x800736b3]
2011-05-13 03:29:34, Error                 CSI    0000001e (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #104835# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47 (0x0000002f), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x800736b3]
2011-05-13 03:29:34, Error                 CSI    0000001f (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #104834# 1973324 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)
[gle=0x800736b3]
2011-05-13 03:29:34, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2011-05-13 03:29:34, Info                  CBS    Setting RollbackFailed flag to 0
2011-05-13 03:29:34, Info                  CBS    Clearing HangDetect value
2011-05-13 03:29:34, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2011-05-13 03:29:34, Info                  CBS    Exec: Restoring driver operations because of a CSI commit failure.
2011-05-13 03:29:34, Error                 CBS    Exec: Failed to pend CSI transaction because transactions cannot be merged: 0. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2011-05-13 03:29:34, Info                  CSI    00000020@2011/5/13:07:29:34.968 CSI Transaction @0x1e824e0 destroyed
2011-05-13 03:29:34, Info                  CBS    Perf: InstallUninstallChain complete.
2011-05-13 03:29:34, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2011-05-13 03:29:34, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2011-05-13 03:29:34, Info                  CBS    WER: Generating failure report for package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, status: 0x800736b3, failure source: Execute, start state: Installed, target state: Installed, client id: RMT
2011-05-13 03:29:34, Info                  CBS    Failed to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2011-05-13 03:29:34, Info                  CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it...
2011-05-13 03:29:34, Info                  CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it...
2011-05-13 03:29:35, Info                  CBS    Reboot mark refs: 0
2011-05-13 03:29:35, Info                  CBS    SQM: Reporting selectable update change for package: Microsoft-Windows-TabletPC-Server-InkSupport-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, update: InkSupport, start: Staged, applicable: Installed, target: Installed, client id: RMT, initiated offline: False, execution sequence: 141, first merged sequence: 141
2011-05-13 03:29:35, Info                  CBS    SQM: Upload requested for report: UpdateChange_InkSupport_Microsoft-Windows-TabletPC-Server-InkSupport-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, session id: 142860, sample type: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Reporting package change for package: Microsoft-Windows-TabletPC-Server-InkSupport-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, current: Installed, pending: Default, start: Installed, applicable: Installed, target: Installed, limit: Installed, hotpatch status: DisabledBecauseNoHotpatchPackagesInitiated, status: 0x0, failure source: Execute, reboot required: False, client id: RMT, initiated offline: False, execution sequence: 141, first merged sequence: 141
2011-05-13 03:29:35, Info                  CBS    SQM: Upload requested for report: PackageChangeBegin_Microsoft-Windows-TabletPC-Server-InkSupport-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, session id: 142859, sample type: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Reporting package change completion for package: Microsoft-Windows-TabletPC-Server-InkSupport-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, current: Installed, original: Installed, target: Installed, status: 0x800736b3, failure source: Execute, failure details: "(null)", client id: RMT, initiated offline: False, execution sequence: 141, first merged sequence: 141
2011-05-13 03:29:35, Info                  CBS    SQM: execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2011-05-13 03:29:35, Info                  CBS    SQM: Failed to initialize Win SAT assessment. [HRESULT = 0x80040154 - Unknown Error]
2011-05-13 03:29:35, Info                  CBS    SQM: average disk throughput datapoint is invalid [HRESULT = 0x80040154 - Unknown Error]
2011-05-13 03:29:35, Info                  CBS    SQM: Upload requested for report: PackageChangeEnd_Microsoft-Windows-TabletPC-Server-InkSupport-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, session id: 142862, sample type: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Reporting selectable update change for package: Microsoft-Windows-ServerDesktopExperience~31bf3856ad364e35~amd64~~6.1.7600.16385, update: DesktopExperience, start: Staged, applicable: Installed, target: Installed, client id: RMT, initiated offline: False, execution sequence: 141, first merged sequence: 141
2011-05-13 03:29:35, Info                  CBS    SQM: Upload requested for report: UpdateChange_DesktopExperience_Microsoft-Windows-ServerDesktopExperience~31bf3856ad364e35~amd64~~6.1.7600.16385, session id: 142860, sample type: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Reporting package change for package: Microsoft-Windows-ServerDesktopExperience~31bf3856ad364e35~amd64~~6.1.7600.16385, current: Installed, pending: Default, start: Installed, applicable: Installed, target: Installed, limit: Installed, hotpatch status: DisabledBecauseNoHotpatchPackagesInitiated, status: 0x0, failure source: Execute, reboot required: False, client id: RMT, initiated offline: False, execution sequence: 141, first merged sequence: 141
2011-05-13 03:29:35, Info                  CBS    SQM: Upload requested for report: PackageChangeBegin_Microsoft-Windows-ServerDesktopExperience~31bf3856ad364e35~amd64~~6.1.7600.16385, session id: 142859, sample type: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Reporting package change completion for package: Microsoft-Windows-ServerDesktopExperience~31bf3856ad364e35~amd64~~6.1.7600.16385, current: Installed, original: Installed, target: Installed, status: 0x800736b3, failure source: Execute, failure details: "(null)", client id: RMT, initiated offline: False, execution sequence: 141, first merged sequence: 141
2011-05-13 03:29:35, Info                  CBS    SQM: execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2011-05-13 03:29:35, Info                  CBS    SQM: Failed to initialize Win SAT assessment. [HRESULT = 0x80040154 - Unknown Error]
2011-05-13 03:29:35, Info                  CBS    SQM: average disk throughput datapoint is invalid [HRESULT = 0x80040154 - Unknown Error]
2011-05-13 03:29:35, Info                  CBS    SQM: Upload requested for report: PackageChangeEnd_Microsoft-Windows-ServerDesktopExperience~31bf3856ad364e35~amd64~~6.1.7600.16385, session id: 142862, sample type: Standard
2011-05-13 03:29:35, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
2011-05-13 03:29:35, Info                  CBS    Enabling LKG boot option
2011-05-13 03:29:35, Info                  CBS    Restored system sleep block state: 0x80000000
2011-05-13 03:29:35, Info                  CBS    Exec: Processing complete.  Session: 30150975_2073748683, Package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2011-05-13 03:29:35, Error                 CBS    Failed to perform operation.  [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2011-05-13 03:29:35, Info                  CBS    Session: 30150975_2073748683 finalized. Reboot required: no [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2011-05-13 03:29:35, Info                  CBS    Session: 30150975_2188096884 initialized by client RMT.
2011-05-13 03:29:36, Info                  CSI    00000021@2011/5/13:07:29:36.793 CSI Transaction @0x1e82f30 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [26]"TI5.30150975_2188096884:1/"

^^ Finally, this is the one which I think needs the most investigation.

I really don't know if this is going to work, but I think that this really is our best bet. I wish to see if I can properly role back this SP1 install.

lol. Back to Flavius again! After all, you only have a selection of me, Flavius, and MowGreen (and soon to be Marsmimar)!

He honestly does know his stuff...

http://www.sevenforums.com/tutorials/109213-windows-update-uninstall-console-level.html

Basically, open an Elevated Command Prompt: http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html

and type in: wusa /uninstall /kb:976932

This method is the best, if you can. It won't take long to tell you that it isn't happy if it isn't happy! (OK, that sentence was pretty lame )

Otherwise, it is big download time I am afraid (sorry) Download Details - Microsoft Download Center - Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932)

I am only continuing to tell you this, because I have a time saving trick for later!

wusa /uninstall C:\Temp\windows6.1-KB976932-X64.exe

Lastly, try PKGMGR. Hopefully, we won't get here.

Firstly, use my tool to extract the Service Pack: http://www.sevenforums.com/tutorials/155584-windows-update-extract-update.html (I find it SO much more convenient that using the Command Prompt - and I have to extract very many updates each day in order to help everyone) (it isn't actually too helpful for this, but will be good practice, because I have many time saving tools, and you might just need to become acquainted with some of them! Go up a directory from the automatically opened Extracted directory to find the .cab file.)

start /w pkgmgr /m:C:\Temp\windows6.1-KB976932-X64.cab /up /s:C:\Sandbox

The very best of luck,

Richard

 

[niemiro]

Just forgot one little thing...

If your Windows Update is set to Automatically install, then could you please hide SP1, and if it isn't, can you please NOT attempt SP1 until I can assess the situation. Thanks a lot!

P.S. For giggles, I re-ran RegistryBooster 2011 and it found 9 System Related Reg Errors. Out of these, 8 are "System Software Settings" and 1 is "ActiveX, OLE, COM sections". I'm holding off telling it to repair these unless you agree. My thinking is why not let it fix 'em, but I don't want to let it repair these if you're not on board with it Niemiro. Please let me know...

I personally don't really bother with Registry Cleaners, but I can't see it doing too much more harm at this point, since I have now found answers to some of what is going on here.

Richard

 

[Drewmann69]

Outch... LOL I can pretty much assure you my friend (despite the d@mning evidence in the logs) that SP1 for 2008 R2/Win7 was NEVER attempted as an install on this machine. The initiative to move this Cluster to SP1 was brought up, and after discussion of us making sure that both Cluster Nodes were absolutely, positively on the same Patch Level BEFORE attempting an SP update we then started getting the flakeyness of the PSU dieing. At first, we thought that Windows was flaking out because this Node was over heating (dust and crud in the vents, heatsyncs, fans, etc... With that , we downed it, unplugged it, took it out to the Air Compressor and blew every spec of dust out of it. It came back up, seemed to run fine for over a week and we thought all was finally well. We then went to update it first (all Updates aside from SP1), as the 1st Node in the Cluster, but it BSoDed in the middle of an Update (so my colegue reminded me) but not certain which one. We then toubleshoot further and finially found that the PSU was causing the issue due to low voltages on the + sides. We ordered another PSU, but unfortunatley this System BSoD'ed probably a couple more times before we could down and replace.

At any rate, here's the results of the Commands you suggested;

ATTEMPT #1
wusa /uninstall /kb:976932
======================
Windows Update Standalone Installer

Installer encountered and error: 0x8000ffff

Catastrophic failure
=================================


ATTEMPT #2
wusa /uninstall C:\Temp\windows6.1-KB976932-X64.exe (Made absolutely sure that SP1 was DL'd and saved to this exact name in this exact Path)

================
Windows Update Standalone Installer

Installer encountered an error: 0x8007065e

Data of this type is not supported.
==============================


ATTEMPT #3
(DL'd your tool, excellent by the way!!!, and used it to Extract SP1)

(Confirmed Paths) C:\>start /w pkgmgr /m:C:\Temp\windows6.1-KB976932-X64\Extracted\windows6.1-KB97
6932-X64.cab /up /s:C:\Sandbox

=================
Windows Package Manager

Operation failed with 0x8007000B (isn't this the same error that you sometimes get when WU is broken on machines?)

An attempt was made to load a program with an incorrect format.

======================================


Short of it, SP1 was unfortunately never installed on this Machine as far a I know, but we planned on it in the future. This just points to Windows being really messed up like you stated way earlier I guess... lol At any rate, please don't feel pressured by any of this, as this is first and foremost my problem. Second, the Sever / Cluster Node is totally usable now (thanks to your help earlier with the Pii sign corruption I missed in the Reg). And third, at this point of functionality, this doesn't have to be fixed right away. Like you said, this is a kewl challenge for us both, and what's really kewl is that no one will suffer if it takes us several months to finally figure out. But in the end, we'll ALL benefit from our work on this!


Enjoy the rest of your weekend my friend, and we'll keep pecking away at this! We'll figure it out eventually!
Drew

P.S. Since you didn't mention the 9 RegBoosters Errors that I mentioned earlier I went a head and told it to fix them. At this point, what could it hurt... =)

 

[Drewmann69]

Oh Poo... lol I think you asked for these Logs... Here they are...

LOL

Thanks,
Drew

 

[Drewmann69]

If your Windows Update is set to Automatically install, then could you please hide SP1, and if it isn't, can you please NOT attempt SP1 until I can assess the situation. Thanks a lot!

No problem. WU was set to "Check for updates, but let me choose whether to download and install them..."

I definitely won't attempt any install of SP1 till we're through all of this and truely ready for it.

Thanks,
Drew