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

Page 3 of 3 FirstFirst 123

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #21

    The easiest thing in that case is to copy the file from the other computer.

    C:\Windows\winsxs\Manifests\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16 385_ru-ru_ddd0024544b2f993.manifest

    Copy the file to your desktop, and put it into a new folder called grdac

    Now copy the folder to C:\


    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:\grdac
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\grdac
    or
    DIR E:\grdac


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

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


    (Please note - this is NOT quite the same command as previously!)
    (e.g.XCOPY P:\wfire P:\windows\winsxs\Manifests /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 SkyDrive Public folder, and post a new link




      My Computer


  2. Posts : 16
    Windows 7 64bit pro russian
    Thread Starter
       #22

    it didn't help =(
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #23

    Hmmm
    Code:
    2013-03-15 21:56:41, Info                  CSI    00000329 [SR] Repairing 1 components
    2013-03-15 21:56:41, Info                  CSI    0000032a [SR] Beginning Verify and Repair transaction
    2013-03-15 21:56:41, Info                  CSI    0000032b 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}.
    2013-03-15 21:56:41, Info                  CSI    0000032c Unable to load manifest for component [ml:280{140},l:196{98}]"msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16385_ru-ru_ddd0024544b2f993"
    2013-03-15 21:56:41, Info                  CSI    0000032d [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)
    2013-03-15 21:56:41, Info                  CSI    0000032e Repair results created:
    POQ 137 starts:
     
    POQ 137 ends.
    2013-03-15 21:56:41, Info                  CSI    0000032f [SR] Repair complete
    I'm almost certain now that the problem is in the registry - in the COMPONENTS hive.
    The cause is a pair of bitflips The problem is how to correct it.

    I think I have a way to do it - I'll do some testing and see what happens.
    back tomorrow :)
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #24

    Please run the following commands on the affected computer, and on another Win7x64 computer (running Russian!)

    Code:
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
    REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16385_ru-ru_ddd0024544b2f993 >%userprofile%\desktop\npkey.log
    REG UNLOAD HKLM\COMPONENTS
     
    .
    a file npkey.log will be created on the desktop - please upload each file to your reply (you'll need to rename the one from the 'good' machine so I know which one it is.)
      My Computer


  5. Posts : 16
    Windows 7 64bit pro russian
    Thread Starter
       #25

    from my home broken pc.
    on monday, i'll add file from working pc
    Last edited by gorod; 18 Mar 2013 at 07:34.
      My Computer


  6. Posts : 16
    Windows 7 64bit pro russian
    Thread Starter
       #26

    Hm. Any suggestions?
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #27

    Ooops! - it dropped off my radar....

    OK - I have the data, so give me a few minutes, and I'll post the fix (I hope!)
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #28

    Open an Elevated Command Prompt, and run the following commands

    Code:
     
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
    REG ADD HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7600.16385_ru-ru_ddd0024544b2f993 /v S256H /t REG_BINARY /d 12927A6554382A9829345D7DAD8164DFF1271FC697169F9975DD57E6ABE9E800 /F
    REG UNLOAD HKLM\COMPONENTS 
     
    .
    close the window, and reboot, then run SFC again - it should pass :)
    Then try the update again
      My Computer


  9. Posts : 16
    Windows 7 64bit pro russian
    Thread Starter
       #29

    Thanks, i'll try it and posted results after it.
      My Computer


 
Page 3 of 3 FirstFirst 123

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:10.
Find Us