Windows 7 Update Failure

Page 1 of 4 123 ... LastLast

  1. Posts : 16
    Windows 7 Pro 64 bit
       #1

    Windows 7 Update Failure


    Been having window 7 pro update problem for about a year now. I had to reload OS twice. It works for several months and then the same problem. Now I can't even update anything. Below are the error messages I get. The 1st screenshot is when I launch windows update. The 2nd is when I click check for update. These are new after I ran SURT. Now Im also getting the BSOD when I'm working at least every hour. I also cannot run sfc/scannow. i gives me the error message "Windows Resource Protection ould Not Start the Repair Service"

    Attachment 325143

    Attachment 325144

    Attachment 325145

    I really do not want to reinstall the OS and all my applications for the 3rd time. Thanks for you help in advance.
      My Computer


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

    The fact that you are getting the same problem after a reinstall indicates that you may be making the same mistake each time.

    Having said that, the indications are that there may be a hardware problem with your machine - possibly either RAM or the hard drive.
    There are a number of errors in the CheckSUR results which are the result of bitflips - where a single character has been altered in a registry entry. One or two is not that unusual - but you have more than a dozen.

    I can fix these, but it's likely to happen again unless you isolate and eliminate the cause.
    I would suggest starting by testing the RAM for errors.
    https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
      My Computer


  3. Posts : 16
    Windows 7 Pro 64 bit
    Thread Starter
       #3

    Thank you very much for replying to my post and helping me out on this. I ran the program to test the memory and found out one of the two memory stick I have had a lot of errors. I removed it and will be operating with just one 4 gb memory stick. I plan on replacing the bad memory stick after all is running properly. What should I do now.
      My Computer


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

    Now it's worth attempting to fix things :)

    Here's the errors from your CheckSUR log -
    Code:
    Checking Component Store
    (w) CSI Catalog Unexpected error 0x0000007B winsxs\Catalogs\d3f3cda49e73801e5>112079337222fd17c5c463345c30e97aa89665c78a9ae9.cat prnso002.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_a40b8d090725cd0f Unexpected error from GetFileAttributes
    (f) CSI Corrupt Identity 0xC0150017 prnrc00b.iff-LanguagePack, Culture=en-US, ^ersion=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=aed64, versionScope=NonSxS prnrc00b.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_21c1e7c0923bd:02 Bad identity
    (f) CSI Corrupt Identity 0xC0150017 prnsv003.inf-LanguagePack, Culture=en-US, Version=6.1.7600.16385, PublicKeqToken=31bf3856al364e35, ProcessorArchitecture=amd64, versionScope=NonSxS prnsv003.in..afguagepack_31bf3056ad364e35_6.1.7600.16385_1fabel0a7d64655f Bad identity
    (f) CSI Missing Deployment Key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7601.17514_b0b6d224b8dc761e HKLM\Components\CanonicalData\Deployments 
    (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-c..lter-mime.resources_31bf3856ad364e35_7.0.7600.16385_en-us_8k3d316c0f30da5d identity and keyform do not match; keyform is wrong.
    (f) CSI Missing Deployment Key 0x00000000 fb7778d5678..193640d7d57_31bf3856ad364e35_8.0.7601.18283_7bef8e4f4633868a HKLM\Components\CanonicalData\Deployments 
    (f) CSI Corrupt Identity 0xC0150017 Mikrosoft-Windows-SpeechCommonNoIA64.Resources, Culture=en-US, Version=6.1.7600.16385, PublicKeyTocen=31bf3856ad364e35, ProcessorArchitecture=wow64, versionScope=NonSxS wow64_microsoft-windows-s..monnoia64.resources_31bf3856ad364e35_6.1.7600.16385_en-us_bb5a1c1019ca8439 Bad identity
    (f) CSI Manifest Missing 0x00000002 wow64_microsoft-windows-s..monnoia64.resources_31bf3856ad364e35_6.1.7600.16385_en-us_bb5a1c1019ca8439.manifest wow64_microsoft-windows-s..monnoia64.resources_31bf3856ad364e35_6.1.7600.16385_en-us_bb5a1c1019ca8439 
    (f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-sysdmhardware.Resources, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35,(ProcessorArchitecture=amd64, vezsionScope=NonSxS amd64_microsoft-windows-s..mhardware.resources_31bf3856ad364e35_6.1.7600.16385Wen-us_46b0ac990f93475a Bad identity
    (f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-s..mhardware.resources_31bf3856ad364e35_6.1.7600.16385Wen-us_46b0ac990f93475a.manifest amd64_microsoft-windows-s..mhardware.resources_31bf3856ad364e35_6.1.7600.16385Wen-us_46b0ac990f93475a 
    (f) CSI Missing Deployment Key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_4e7e08030744cc06 HKLM\Components\CanonicalData\Deployments 
    (f) CSI Missing Deployment Key 0x00000000 prnrc00b.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_21c1e7c0923bd202 HKLM\Components\CanonicalData\Deployments 
    (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-e..mmandline.resources_31bf385>ad364e35_6.1.7680.16385_en-us_988e3b2110ef94f2 identity and keyform do not match; keyform is wrong.
    (f) CSI Missing Deployment Key 0x00000000 prnsv003.in..anguagepack_31bf3856ad364e35_6.1.7600.16385_1fabed0a7d64655f HKLM\Components\CanonicalData\Deployments 
    (f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-CorruptedFileRecovery.Resources,(Culture=en-US, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_microsoft-windows-c..erecovery.resourcesW31bf3856ad364e35_6.1.7601.17514_en-us_28408dcd10e57d87 Bad identity
    (f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-c..erecovery.resourcesW31bf3856ad364e35_6.1.7601.17514_en-us_28408dcd10e57d87.manifest amd64_microsoft-windows-c..erecovery.resourcesW31bf3856ad364e35_6.1.7601.17514_en-us_28408dcd10e57d87 
    (f) CSI Corrupt Component Keyform 0x00000000 identity x86_mikrosoft-windows-{..resources.resgurces_31bf3856ad364e35_6.1.7600.16385_en-us_fb5b73230e7e4241 identity and keyform do not match; keyform is wrong.
    (f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-DirectShow-DV.Resources,(Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x06, versionScope=NonSxS x86_mikrosoft-windows-d..ctshow-dv.resources_31bf3856ad364e35_6.1.7600.16385_en-us_181bfd47120ca6b5 Bad identity
    (f) CSI Manifest Missing 0x00000002 x86_mikrosoft-windows-d..ctshow-dv.resources_31bf3856ad364e35_6.1.7600.16385_en-us_181bfd47120ca6b5.manifest x86_mikrosoft-windows-d..ctshow-dv.resources_31bf3856ad364e35_6.1.7600.16385_en-us_181bfd47120ca6b5 
    (f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-ie-imagesuppor|_31bf3856ad364e;5_11.2.9600.16428_none_204bdbe2081cad53 identity and keyform do not match; keyform is wrong.
    (f) CSI C Mark Deployment Missing 0x00000000 c!1e9d2f218e3..74e9c311d59_31bf3856ad364e35_8.0.7601.22479_c035f80e wow64_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7601.22479_none_e82507b9896b3378 
    (f) CSI C Mark Deployment Missing 0x00000000 c!1e9d2f218e3..74e9c311d59_31bn3856ad364e35_8.0.7601.22479_c035f80ef4c018fe amd64_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7601.22479_none_ddd05d67550a717d 
    (f) CSI C Mark Deployment Missing 0x00000000 c!30aa6ee29eb..cb1e85a7e93_31bf3856ad364e35_8.0.7601.18283_47a0fbcc amd64_30aa6ee29eba43c740daccb1e85a7e93_31bf3856ad364e35_8.0.7601.18283_none_47a0fbccaae00edb 
    (f) CSI C Mark Deployment Missing 0x00000000 c!1e9d:f218e3..74e9c319d59_31bf3856ad364e35_8.0.7601.22479_c035f80ef4c018fe amd64_1e9d2f218e316dbfe45fc74e9c311d59_31bf3856ad364e35_8.0.7601.22479_none_c035f80ef4c018fe 
    (f) CSI C Mark Deployment Missing 0x00000000 c!8b022193660..2a974cec77a_31bf3856ad364e35_8.0.7601.22479_2da0655c amd64_8b022193660a192ccd0f42a974cec77a_31bf3856ad364e35_8.0.7601.22479_none_2da0655cdb1206c2 
    (f) CSI C Mark Deployment Missing 0x00000000 c!30aa6ee29eb.&cb1e85a7e93_31bn3856ad364e35_8.0.7601.18283_47a0fbcc wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18283_none_962b3d5ce4658c41

    I need to have a look at your COMPONENTS registry hive

    Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.
      My Computer


  5. Posts : 16
    Windows 7 Pro 64 bit
    Thread Starter
       #5
      My Computer


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

    OK - I've completed the first round of error-corrections...


    I've uploaded a file - eduaa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it to your desktop.
    Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

    Create a new System Restore point

    Open an Elevated Command Prompt, and run the following commands.

    REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
    COPY %userprofile%\desktop\eduaa\COMPONENTS C:\Windows\System32\config

    If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

    Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.
      My Computer


  7. Posts : 16
    Windows 7 Pro 64 bit
    Thread Starter
       #7

    I did the two commands and it went well. Attached is the new Checksur.Log file

    Attachment 325449
      My Computer


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

    That's still dated 7th July - did you remember to delete the copy you made earlier and create a new one?
      My Computer


  9. Posts : 16
    Windows 7 Pro 64 bit
    Thread Starter
       #9

    Im sorry but how do I creat a new one.
      My Computer


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

    OK - just do the following...

    Open Windows Explorer, and navigate to the C:\Windows\Logs\CBS folder
    in there you should see the CheckSUR.log file we need (if not we have a problem!) right-click on it and select Send to... then Desktop (create Shortcut). Close the window.

    In your reply here, click o the paper-clip icon - click on the Browse button at the top of the upload window that should open, and find the Desktop entry there. open that, and you should find an entry saying 'CheckSUR.log - Shortcut' click on that to highlight it, then click Open - then click the Upload button. Once it's finished uploading, click the 'Close this window' button, then complete your post and click Submit.
      My Computer


 
Page 1 of 4 123 ... 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 01:53.
Find Us