Win 7 Update errors, Readiness Test returning 5000+ errors Help


  1. Posts : 4
    Win 7 64 bit, Home Premium, Ultimate and Enterprise
       #1

    Win 7 Update errors, Readiness Test returning 5000+ errors Help


    Need some guidance.

    I'm trying to help a friend who got hit by something, virus, malware etc. Cleaned that up but....

    In looking over his Win 7 64bit Home Premium system, I noticed his Windows Update had not run in over a year. So I tried to run it manually and have been going down a rabbit hole ever since.

    It looks like something has completely removed all the subkeys to "Component Based Servicing" which is core to the whole Update process. TrustedInstaller is throwing all sorts of 126 errors.

    I tried to run an sfc /scannow and it fails

    So last I ran a Readiness Test. Whoa, it fixed 8 and left 5478 errors. Almost all related to the regkeys needed for Component Based Servicing.

    Is there an overall re-install for Windows Update and it's dependent components? Is there any chance this laptop can be saved? I've run out of idea's. All googled fixes have failed so I'm open to all suggestions at this point

    Thx
      My Computer


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

    Pleasefollow the WindowsUpdate Posting Instructions and post the requested data
      My Computer


  3. Posts : 4
    Win 7 64 bit, Home Premium, Ultimate and Enterprise
    Thread Starter
       #3

    Detail for Windows Update errors


    Noel

    Thanks for looking at this. Below is the list requested:

    1.) Ran SURT, both CBS.log and CheckSUR.txt attached

    2.) Tried to run sfc /scannow, it errors with "Windows Resource Protection could not start repair service"

    3.) Ran Windows Update: Error code: 80080005 Windows Update encounterd unknown error

    Thx, John
      My Computer


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

    I think the basic problem relates to these two errors in the CheckSUR log....
    Code:
    Checking Package Watchlist
    (f) CBS Registry Error 0x00000002 Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect  Failed to open store key
     
    Checking Packages
    (f) CBS Registry Error 0x00000002 Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\  Failed to open store key
    The question arises as to whether this is because the keys don't exist, or because the permissions have been 'adjusted' in some way.

    Please be VERY careful when following these directions - errors in Regedit can prevent your machine booting at all!


    Open Regedit

    Navigate to the

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

    key




    right-click on the key to highlight it and select Permissions

    Please confirm that there are 4 entries.
    Users
    Administrators
    SYSTEM
    TrustedInstaller

    All entries should have Read permissions, except for TrustedInstaller, which has Full permissions.

    Click on the Advanced button
    in the Permissions tab, all users should say <not inherited> and <This key and subkeys'

    Put a tick in the 'Replace all child object permissions ...' box, and click Apply, and OK (twice) to get back to Regedit
    Are the Keys Packages and PackageDetect visible now? can you read the content?

    If so, run another CheckSUR scan and post the results.
    Last edited by NoelDP; 11 Sep 2013 at 09:56. Reason: correct error
      My Computer


  5. Posts : 4
    Win 7 64 bit, Home Premium, Ultimate and Enterprise
    Thread Starter
       #5

    Noel

    Checked the key and all 4 entries existed with the correct permissions
    I then went into advance and applied the tick as requested

    Nothing new showed up underneath "Component Based Servicing". The only subkey that exists is "Version" which I added per other instructions I tried to get the TrustedInstaller to work correctly, which it did not.

    John
      My Computer


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

    In that case, the only thing I can suggest is that you do a repair install - the registry is too far gone to allow manual repair.
      My Computer


  7. Posts : 4
    Win 7 64 bit, Home Premium, Ultimate and Enterprise
    Thread Starter
       #7

    Thanks for the help. That is what I was suspecting. Any suggestions on if I can do a non-distructive re-install?
      My Computer


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

    That's what a repair install is :)
    See here for instructions...
    https://www.sevenforums.com/tutorials/3413-repair-install.html
      My Computer


 

  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 05:15.
Find Us