Unable to install update kb2756921, problem with winsxs(corrupted)

Thanks for reposting - welcome to the forum!

This is from the SFCDetails file

Code:

2013-02-23 20:13:57, Info                  CSI    00000455 [SR] Repairing 1 components
2013-02-23 20:13:57, Info                  CSI    00000456 [SR] Beginning Verify and Repair transaction
2013-02-23 20:13:57, Info                  CSI    00000459 [SR] Cannot verify component files for system.runtime.serialization.resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"ru-ru", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

It appears not to have been found by CheckSUR, so we'll have to do a manual replacement.
The problem here is that I don't have a Russian copy of the appropriate file.

Can you get hold of either an installation disk (any edition of Windows 7) or do you have another PC you can copy the file from?
If we assume that you have another PC, copy the files

C:\Windows\Winsxs\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16385_ru-ru*.*
to your machine - put it in the folder C:\goraa\Manifests (which you will need to create)


Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\goraa
hit the enter key - if you get a 'Not Found' error try
DIR D:\goraa
or
DIR E:\goraa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\goraa <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

It may be worth running a new CheckSUR scan as well - post the CheckSUR.log file.

It seems to me that it's likely that your earlier attempts to fix the problem may well have made it worse.
The registry errors in that CheckSUR report are unusual to say the least - and may result from other system problems such as the use of Language Packs on systems not supposed to take them.

You may find that a repair install is going to be the easiest option now.

If you want to carry on trying to fix this - all you need for the moment is the .manifest file - we won't know if anything else is wrong until that is corrected.
Then we can worry about the rest :)

Interesting error in the SFC....

Code:

2013-02-25 13:55:30, Info                  CSI    000001f0 Manifest hash for component [ml:280{140},l:196{98}]"msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16385_ru-ru_ddd0024544b2f993" does not match expected value. 
 Expected:{l:32 b:12927a6554382a9829345d58ad8164dff1271f4297169f9975dd5742abe9e800}
    Found:{l:32 b:12927a6554382a9829345d7dad8164dff1271fc697169f9975dd57e6abe9e800}.

I'd have expected a greater difference if there were anything odd about the file - instead there are just two characters (hex pairs)

I'm beginning to suspect that the problem is actually in the registry.
Please run the following commands on at least two machines, and compare the output

Code:

 
REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
REG QUERY HKLM\COMPONENTS\DerivedData\Components\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16385_ru-ru_ddd0024544b2f993 /S
REG UNLOAD HKLM\COMPONENTS
 
.

windows 7 pro 32bit russian sp1 lenovo x200

C:\Windows\system32>REG QUERY HKLM\COMPONENTS\DerivedData\Components\msil_system
.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16385_ru-ru_ddd002454
4b2f993 /S

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_system.runtime.seriali
zation.resources_b77a5c561934e089_6.1.7600.16385_ru-ru_ddd0024544b2f993
identity REG_BINARY 73797374656D2E72756E74696D652E73657269616C697A6174
696F6E2E7265736F75726365732C2043756C747572653D72752D72752C2056657273696F6E3D362E
312E373630302E31363338352C205075626C69634B6579546F6B656E3D6237376135633536313933
34653038392C2050726F636573736F724172636869746563747572653D6D73696C
S256H REG_BINARY 388FD1AB18D804C3327AE8586AF17349D39CB625E9BAFAEBE3E0B
065C04C1D3C
c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_f57dda463e42efcc
REG_BINARY
c!wcf-http-ac..anguagepack_31bf3856ad364e35_6.1.7600.16385_b479f1bae3b15d4d
REG_BINARY
c!wcf-nonhttp..anguagepack_31bf3856ad364e35_6.1.7600.16385_9a80c3f00e5928b6
REG_BINARY
f!system.runtime.serializat_515882fe013793b6 REG_BINARY 53007900730074
0065006D002E00520075006E00540069006D0065002E00530065007200690061006C0069007A0061
00740069006F006E002E005200650073006F00750072006300650073002E0064006C006C00
c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7601.17514_f7aeee0e3b317366
REG_BINARY
c!wcf-http-ac..anguagepack_31bf3856ad364e35_6.1.7601.17514_b6ab0582e09fe0e7
REG_BINARY
c!wcf-nonhttp..anguagepack_31bf3856ad364e35_6.1.7601.17514_9cb1d7b80b47ac50
REG_BINARY


C:\Windows\system32>REG UNLOAD HKLM\COMPONENTS
Операция успешно завершена.

Very odd results - the SHA256 values for the two are vastly different (and should be the same, so far as I know)

I suspect that the second machine is the problem one??