Windows update repeatedly failing with 3 updates

[curseofsambowie]

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

 

[NoelDP]

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)

 

[curseofsambowie]

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.

 

[NoelDP]

Here's the detail from CheckSUR

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 -

 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...

 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.

 

[NoelDP]

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

 

[curseofsambowie]

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

 

[curseofsambowie]

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.

 

[NoelDP]

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.

 

[curseofsambowie]

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>

 

[NoelDP]

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

 

[curseofsambowie]

Okay, ran it again and now SFC scan without an errors! I will try windows update again now and see how it goes. Attached is the CBS zip after the most recent clean SFC scan.

 

[curseofsambowie]

Hmm. Well tried installing KB2871997 without success, again received error 80070490.

Should I try any other updates or alternative next steps?

Thanks, sam.

 

[NoelDP]

Not surprising - we haven't yet addressed the errors in the CheckSUR report.

First we need to update the CheckSUR scan, in case the repairs we've already done make a difference - please run the CheckSUR tool again, and post the new C:\Windows\Logs\CBS\CheckSUR.log file

 

[curseofsambowie]

Ah, I was over eager to get things moving apparently. Attached is the checkSUR log, let me know if that is the right one.

 

[NoelDP]

That's the one

Here's the error list...

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

Let's see if another tool helps clear those errors in default mode.

Please download SFCFix from here... http://www.sysnative.com/niemiro/apps/SFCFix.exe and save it to your desktop (we'll need it later anyhow, I think)

Once saved, double-click on it and accept the warnings. It'll run, and create a file SFCFix.log on the desktop - please upload it to your reply.

 

[curseofsambowie]

Hello. Downloaded SFCfix and ran, but appears to have run into an error. Attached is the log.

 

[curseofsambowie]

A little more info. Desktop is on a separate drive from C:\windows and sfcfix originally could not write txt log file because it was looking for the desktop folder there. I just created a folder called desktop and then was able to run sfcfix but resulted in log attached above.

 

[NoelDP]

A little more info. Desktop is on a separate drive from C:\windows and sfcfix originally could not write txt log file because it was looking for the desktop folder there. I just created a folder called desktop and then was able to run sfcfix but resulted in log attached above.

Hmm...
That could well still be a problem - maybe moving the SFCFix.exe to somewhere else on the C: driver would be a good idea - perhaps create a folder C:\SFCFix and put it there, then run it again.

I'll flag the developer and see if it's a known problem.

 

[curseofsambowie]

Making the C:\sfcfix actually seems to have worked. Attached is the new log, program reported that there were some errors that it was unable to fix.

 

[NoelDP]

So far, so good

Let's see what's left.
Please tun CheckSUR again and post the new CheckSUR.log file