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
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.
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)
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.
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
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)
it's the MATSKB fixit - the one from the page itself, rather than the overlay - that you need to run.
Last edited by NoelDP; 09 Feb 2013 at 17:52. Reason: still learning to spell :)
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?
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
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
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?
Quote
