Windows update repeatedly failing with 3 updates

Page 1 of 7 123 ... LastLast

  1. Posts : 34
    Windows 7 Home Premium 64 bit
       #1

    Windows update repeatedly failing with 3 updates


    Hello

    Frustrated with trying to fix this myself and thought I would turn to the forum for some help. I have been unable to install KB 2929437, KB 2871997, or KB 2830477 either as a group or individually. The error codes are all different and are below:

    KB 2929437: error 8007054F
    KB 2871997: error 80070490
    KB 2830477: error 80070BC9

    Since this started, Windows Update was able to install several other updates but not these three for some reason. I have run the System Update Readiness Tool and the SFC scan without change in the errors. The SFC scan continues to show corrupt files but is unable to fix them.

    Problem #2 - I also appear to be unable to upload the zipped CBS log and continue to get internal server errors from the website when I try to attach the file. I would be happy to do so if anyone knows a way around this.

    Thanks in advance!

    sam
      My Computer


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

    Please follow the Windows Update Posting Instructions and post the requested data
    If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CBA files, for a number of reasons)
      My Computer


  3. Posts : 34
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

    Thanks for the reply and the tip on decreasing the size of the uploaded file. I have attached the CBS log with 4 of the cabnet files removed, let me know if you need them uploaded in individual zip files.

    I think I have completed all the steps in the posting instructions other than the upload, let me know if there are other steps I need to do.
      My Computer


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

    Here's the detail from CheckSUR

    Code:
    Checking Package Watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    Checking Component Watchlist
    (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    Checking Packages
    (f) CBS Registry Error 0x80070002 Package_114_for_KB2661254~31bf3856ad364e35~amd64~~6.1.1.3  failed to get CurrentState
    (f) CBS Registry Error 0x80070002 Package_114_for_KB2661254~31bf3856ad364e35~amd64~~6.1.1.3  failed to get Visibility
    ...and from SFC -
    Code:
     Line 27825: 2014-05-19 13:19:21, Info                  CSI    00000338 [SR] Repairing 2 components
     Line 27826: 2014-05-19 13:19:21, Info                  CSI    00000339 [SR] Beginning Verify and Repair transaction
     Line 27829: 2014-05-19 13:19:21, Info                  CSI    0000033b [SR] Cannot repair member file [l:22{11}]"bootres.dll" of Microsoft-Windows-BootRes, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 27832: 2014-05-19 13:19:23, Info                  CSI    0000033d [SR] Cannot repair member file [l:38{19}]"NlsLexicons0020.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    ...and from the background CBS log data...
    Code:
     Line 99169: 2014-05-19 13:26:03, Error                 CBS    Failed to create CSI transaction with id: TI5.30372743_1758105622:1/. A pending repair transaction already exists, reboot is required [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
     Line 99181: 2014-05-19 13:26:03, Error                 CBS    Failed to call external evaluate applicability on package: Package_1_for_KB2584146~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2584146-1_neutral_LDR [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
     Line 99183: 2014-05-19 13:26:03, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2584146-9_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
     Line 99185: 2014-05-19 13:26:03, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2584146~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2584146-13_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
    S
    I think it's time to break the general rule about the order of repairs, and attempt to fix the SFC problems first.

    With any luck this will allow the reboot to do the job it's trying to, and in the process, fix the problems showing in CheckSUR

    I'll post a fix protocol (hopefully) fairly soon.
      My Computer


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

    I've uploaded a file - csbaa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    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:\csbaa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\csbaa
    or
    DIR E:\csbaa



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



    XCOPY <drive>:\csbaa <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
      My Computer


  6. Posts : 34
    Windows 7 Home Premium 64 bit
    Thread Starter
       #6

    Great, thanks so much for your help. I will work through these steps and let you know how it goes.
      My Computer


  7. Posts : 34
    Windows 7 Home Premium 64 bit
    Thread Starter
       #7

    Okay, went through the steps above and ran SFC again. It still came back with corrupted files that could not be entirely repaired. Attached is the CBS zip.
      My Computer


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

    Still the same errors - which means that someone made a mistake somewhere.
    Either I uploaded the wrong files, or you made an error somewhere in the process.
    Please open an Elevated COmmand Prompt, and run the following commands.

    DIR C:\csbaa
    DIR C:\Windows\winsxs\csbaa

    Post the results

    Here are some instructions to make life easier :)
    1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
    2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
    3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.
      My Computer


  9. Posts : 34
    Windows 7 Home Premium 64 bit
    Thread Starter
       #9

    Hi there. The mistake is likely on my end based on past attempts at these things. Here is the result of the command prompt, let me know if I should repeat the steps from the Repair Environment.

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>dir c:\csbaa
    Volume in drive C has no label.
    Volume Serial Number is 06A0-9124

    Directory of c:\csbaa

    05/19/2014 05:19 PM <DIR> .
    05/19/2014 05:19 PM <DIR> ..
    05/19/2014 05:19 PM <DIR> amd64_microsoft-windows-bootres_31bf3856a
    d364e35_6.1.7601.17514_none_9d42c69298905ee5
    05/19/2014 05:19 PM <DIR> amd64_microsoft-windows-naturallanguage6_
    31bf3856ad364e35_6.1.7601.17514_none_fc00d9a9415b5f6e
    0 File(s) 0 bytes
    4 Dir(s) 20,648,534,016 bytes free

    C:\Windows\system32>dir c:\windows\winsxs\csbaa
    Volume in drive C has no label.
    Volume Serial Number is 06A0-9124

    Directory of c:\windows\winsxs

    File Not Found

    C:\Windows\system32>
      My Computer


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

    That's as it should be - all I can think is that you made a mistake somewhere with the command issued in the Repair Environment.

    Please try again - paying particular attention to the command and their syntax.

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



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

    XCOPY <drive>:\csbaa <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
      My Computer


 
Page 1 of 7 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 18:35.
Find Us