Windows Update fails (KB2705219, KB2786400, KB2773072)

[hsint]

Hi,

My windows update fails with error codes 800B0100 & 80070490.

I've been trying to solve this for some time already using CheckSur, downloading the failed packages and copying the manifests, mum & cat to appropriate folders. While this solved many missing file errors in the CheckSur log some remain, and I can't figure out where to get these files.

Attached the CBS log (zipped) and CheckSur.log

Help would be appreciated

 

[NoelDP]

Shouldn't be too much of a problem to sort

Here's the problem fil list from the CheckSUR...

Unavailable repair files:
 winsxs\manifests\msil_system.resources_b77a5c561934e089_6.1.7601.22126_en-us_508ba5e0b0e37ff9.manifest
 winsxs\manifests\msil_system.resources_b77a5c561934e089_6.1.7601.17966_en-us_675d4a9e97388b01.manifest
 servicing\packages\Package_for_KB2773072~31bf3856ad364e35~amd64~~6.1.1.5.mum
 servicing\packages\Package_for_KB2773072~31bf3856ad364e35~amd64~~6.1.1.5.mum
 servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2773072~31bf3856ad364e35~amd64~~6.1.1.5.cat
 servicing\packages\Package_for_KB2773072~31bf3856ad364e35~amd64~~6.1.1.5.cat
 servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2786400~31bf3856ad364e35~amd64~~6.1.1.0.cat

... and from the CBS.log file....

 Line 203133: 2013-02-08 17:13:35, Info                  CSI    000004bd [SR] Repairing 1 components
 Line 203134: 2013-02-08 17:13:35, Info                  CSI    000004be [SR] Beginning Verify and Repair transaction
 Line 203139: 2013-02-08 17:13:35, Info                  CSI    000004c1 [SR] Cannot verify component files for System.Resources, Version = 6.1.7601.17966, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-us", VersionScope neutral, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 203144: 2013-02-08 17:13:35, Info                  CSI    000004c3 [SR] Repair complete

I'll post a fix protocol for them later.

 

[NoelDP]

I've uploaded a file - hsiaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder hsiaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[hsint]

Thanks for the swift reply.

That seems to have done the trick with regards to CheckSur. CheckSur log says all errors fixed. I've attached the logs anyway (so you can see the horrendous number of errors I had that I managed to fix myself ).

However when I run Windows Update it still gives the same errors on the same 3 updates. Maybe I need to reboot first? I'll try that now.

 

[hsint]

I rebooted and tried windows update again. Still no luck. Same errors. I reran CheckSur after that one more time but that came back without any errors or warnings.

Summary:
Seconds executed: 124
No errors detected

I reran sfc /scannow but that also yielded no errors.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

Any ideas?

 

[NoelDP]

What error message do you get??
Please run through the full Windows Update posting instructions again, and post the data requested.

 

[hsint]

Hi,

1. I have rerun CheckSur again (Checksur.log attached)

2. I have rerun sfc /scannow again (CBS.log attached)

3. KB2705219 fails with error code 80070490
KB2773072 fails with error code 800B0100
KB2786400 fails with error code 800B0100

I think that is all that is described in the posting instructions?

 

[Parman]

Try redownloading the updates.

MS12-054: Description of the security update for Windows Networking Components: August 14, 2012


An update is available that changes the default settings of the shaping behavior for Arabic text rendering in Windows 7 and Windows Server 2008 R2

I couldnt find an update for KB2773062 are you sure the number is correct?

 

[hsint]

You are correct, I made a typo in that issue nr. I had it correct it the topic title . I edited my posted above to show the correct nr.

I have downloaded the installers for the patch via the links you provided, and then ran them by hand

KB2705219 still fails. I don't think it gives a reason on screen but it flicks by rather fast. Is there a log of this somewhere?

KB2786400 seems to go alright. It finishes without an error and tells me I have to reboot which I will do after posting this.

I grabbed the installer for KB2773072 from Download Update for Windows 7 for x64-based Systems (KB2773072) from Official Microsoft Download Center
Running this seems to go fine as well, asking for a reboot.

That suggests only a remaining issue with KB2705219, which I apparently have for quite some time already, as this one from October 2012?

I'll reboot and report back with the results from Windows update.

 

[hsint]

Alright I'm back again. KB2786400 & KB2773072 are gone from the pending updates in Windows Update and show as successfully installed in the update history. However KB2705219 is still there, and still fails to install with error 80070490.

Any ideas?

 

[NoelDP]

While the SFC log is clear, there are problems in the rest of the CBS log - mostly to do with KB2647753.

I would suggest uninstalling that update, if you can, from Installed Updates, and then reinstalling it manually.

If it won't uninstall normally, try running this command from an Elevated Command Prompt...

wusa /uninstall /kb:2647753

and rebooting

 

[hsint]

I have uninstalled update KB2647753 from Installed Updates as recommended.
Next I rebooted.
Then I downloaded the update from Download Update for Windows 7 for x64-based Systems (KB2647753) from Official Microsoft Download Center
However when I try to run this update it tells me this update is not applicable for my computer. If that is so, how did I get it installed in the first place?

Anyway, after this I tried to install KB2705219, but still no luck.

Next I ran Check for Updates in Windows update, and KB2647753 appears as an outstanding update, so I tried to install it from Windows update (unselecting KB2705219 so only KB2647753 is installed). Interestingly that worked.

So I tried KB2705219 again, once from Windows update and once from the downloaded installer. Both time a failure.

So I ran CheckSur & SFC again. Logs attached. I also found a WindowsUpdate.log so I attached that as well in case it is helpful.

 

[NoelDP]

The problem seems to be caused by this error
2013-02-09 11:20:31, Error CBS Failed to resolve package 'Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1' [HRESULT = 0x80070490 - ERROR_NOT_FOUND]


- which is a little strange, since you're actually attempting to install a later version of the patch!

I can only think that WU is confused about which version it's working on, for some reason - and therefore we need to reset it.

I would suggest running the fixit from here... How do I reset Windows Update components? and see if that helps - note that it will delete your update history (but not the updates - they will still be installed, and listed in the Installed Updates list)

 

[hsint]

Hi,

I'm not sure if I'm following your instructions correctly. I clicked the link you provided and ran the FixIt. It says it has fixed problems, but when I look in the update history afterwards the history is still there. :banghead:

Installing the update still fails.

I'm not sure I ran the correct FixIt. Somehow the site redirects and I ended up getting two fixits, with a different name (MicrosoftFixit.wu.MATSKB.Run.exe & MicrosoftFixit.wu.LB.32283874439356161.2.1.Run.exe). Maybe the website redirects mess up due to language issues (it's redirecting me to a dutch page eventhough my windows is english)

I ran both FixIts btw, but no result.

Btw, the weird thing is, I have the file in the error message you show sitting in my C:\Windows\Temp\CheckSUR\servicing\Packages folder. Not sure where it came from. The only difference is that the filename is all lowercase while your error message has some upper case letters.

• package_2_for_kb2705219~31bf3856ad364e35~amd64~~6.1.1.1.cat
• package_2_for_kb2705219~31bf3856ad364e35~amd64~~6.1.1.1.mum

 

[NoelDP]

Don't worry about that - it's from the CheckSUR tool itself. (that's why the tool is such a large download - it has a lot of the relevant package and manifest files within it)

 

[NoelDP]

it's the MATSKB fixit - the one from the page itself, rather than the overlay - that you need to run.

 

[hsint]

I just ran the MATSKB fixit, selecting runas administrator to make sure that wasn't a limitation, and made sure I had Windows Update closed. While this fixit seems to clear some history (initially my Windows Update told me it was up to date) it does not clear the Update History. Also within 1 minute Windows was able to tell me there was an update available. The dreaded KB2705219.

Rerunning KB2705219 from Windows update or from the .msu still does not work.

I'm quite comfortable with computers but I'm well beyond my depth here. Is there any information I can provide?

 

[NoelDP]

OK - in that case we'll go the more aggressive route...
download Fixit 50202 from You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services and run it in default mode - then reboot and run it again in Aggressive mode -this WILL delete your history.
Wait at least 15 minutes before rebooting again (the system may need time to rebuild certain data stores).

After the reboot, wait another 15 minutes, then try installing the update from the msu file - post your results, and the result of another SFC /SCANNOW

 

[hsint]

OK.

So that did indeed erase the update history. After the Fixit the waiting rebooting waiting etc as you described I ran the MSU --> Failed.

Ran SFC again as instructed. See attached CBS log

 

[NoelDP]

That's brought the problem down to a single error in the CBS log.

Package_2_for_KB2705219~31bf3856ad364e35~amd64~~6.1.1.1

this in turn relates to another error...
2013-02-10 22:00:06, Error CBS Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-02-10 22:00:06, Info CBS WER: Generating failure report for package: Package_for_KB2705219~31bf3856ad364e35~amd64~~6.1.2.0, status: 0x80070490, failure source: Execute, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
2013-02-10 22:00:06, Info CBS Failed to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

I think we may be able to resolve this one fairly simply


I've uploaded a file - hstaa.zip - to my SkyDrive at Noel's SkyDrive
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:\hstaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\hstaa
or
DIR E:\hstaa

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

XCOPY <drive>:\hstaa <drive>:\windows\servicing\packages /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


then, run a manual Check for Windows Updates.
what happens?