Windows 7 Pro x86, constantly de-regestering itself

Page 4 of 5 FirstFirst ... 2345 LastLast

  1. Posts : 21
    Win7Ultimate x64, Win7Pro x64, Win8Pro x64
    Thread Starter
       #31

    Here's the CBS.log
      My Computer


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

    As I thought - it's almost certainly a bitflip in the registry causing the manifest error.
    The S256 hash value differs from the found value by only one bit....

    Expected:{l:32 b:8e98bc15c20c1b3cd3e871c52786e47815e132c0ade91cbdaba5da9f2fb29bc3}
    Found: {l:32 b:8e98bc15c20c1b3cd3e871c52786e47855e132c0ade91cbdaba5da9f2fb29bc3}

    It's almost impossible for that to happen with a corrupted file, so the value in the registry must be wrong.

    I'll adjust the COMPONENTS hive accordingly (after checking the value elsewhere) - that should get rid of the rest of the errors :)
      My Computer


  3. Posts : 21
    Win7Ultimate x64, Win7Pro x64, Win8Pro x64
    Thread Starter
       #33

    That would be grand, thanks!
      My Computer


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

    Ooops! - this slipped off the desk

    I'll do it tonight :)
      My Computer


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

    OK - done and confirmed... and we have an easier way to fix it than messing around with detached COMPONENTS hives :)

    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\x86_mdm5674a.inf_31bf3856ad364e35_6.1.7600.16385_none_e6de8df1e7b331d5 /v S256H /t REG_BINARY /d bc15c20c1b3cd3e871c52786e47855e132c0ade91cbdaba5da9f2fb29bc3 /F
    REG UNLOAD HKLM\COMPONENTS
    close the window, and reboot - then run another SFC scan and post the CBS.log
      My Computer


  6. Posts : 21
    Win7Ultimate x64, Win7Pro x64, Win8Pro x64
    Thread Starter
       #36

    Here's the CBS log
      My Computer


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

    Hmmm -
    Code:
     Line 4921: 2013-03-22 20:50:40, Info                  CSI    000001be [SR] Repairing 4 components
     Line 4922: 2013-03-22 20:50:40, Info                  CSI    000001bf [SR] Beginning Verify and Repair transaction
     Line 4927: 2013-03-22 20:50:40, Info                  CSI    000001c2 [SR] Cannot verify component files for mdm5674a.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
     Line 4928: 2013-03-22 20:50:40, Info                  CSI    000001c3 [SR] Cannot verify component files for Microsoft-Windows-fde, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
     Line 4931: 2013-03-22 20:50:41, Info                  CSI    000001c5 [SR] Cannot repair member file [l:24{12}]"Wildlife.wmv" of Microsoft-Windows-VideoSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    Odd - I seem to have 'lost' the first two Bytes of data from the expiated value for the S256H....
    let me try that again......

    In an Elevated Command Prompt, run the following commands.

    Code:
     
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
    REG ADD HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_mdm5674a.inf_31bf3856ad364e35_6.1.7600.16385_none_e6de8df1e7b331d5 /v S256H /t REG_BINARY /d 8e98bc15c20c1b3cd3e871c52786e47855e132c0ade91cbdaba5da9f2fb29bc3 /F
    REG UNLOAD HKLM\COMPONENTS

    We also seem to have picked up another manifest problem.

    Please run CheckSUR again, and post the new log
      My Computer


  8. Posts : 21
    Win7Ultimate x64, Win7Pro x64, Win8Pro x64
    Thread Starter
       #38

    Appologies for the delay, had a few other issues that had to take priority.
    Thanks for your support so far.
      My Computer


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

    No problem - I have plenty of other stuff to keep me over-occupied :)
      My Computer


  10. Posts : 21
    Win7Ultimate x64, Win7Pro x64, Win8Pro x64
    Thread Starter
       #40

    Thank you very much for your help Sir, you can close the ticket. The PC has been hung, drawn and quartered.
    Thanks again!
      My Computer


 
Page 4 of 5 FirstFirst ... 2345 LastLast

  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 07:17.
Find Us