[SOLVED] Windows update fails to install KB2809289 with error 80073712

Hi Tom,
you're welcome. I'm an expert user (actually I'm a developer) and usually I'm able to fix problems by myself. But this time I was stuck in front of this Windows Update problem, so complex and so specific. The only suggested solution on the internet (even on Technet) was to repair or reinstall Windows...
Finally, you found the right direction for the solution and from them on I was able to go on my own :smile9: . But ehy, someone had to show me the way!!
Also, I'm used to sharing back my experience with people who helped me, this is the minimum I could do to give something back. Maybe it can be useful for others..

Btw, you're once again right: I was running SURT, thinking everything was fine now, but instead no, there's still some issue.
Here's the CheckSUR.log
Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-18 21:12

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-Italian~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-Italian~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 166
 Found 4 errors
  CBS MUM Corrupt Total count: 4

Unavailable repair files:
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.cat
These seem related to the successful IE10 install, looking at version numbers (10.2...)

fralken
 
Hi fralken,

Oh nice, I suspected you had a background with computers and that explains it! There are very few of us who work on Windows Update errors (specifically) and you certainly came to the right place, as a forum we are still growing but we definitely get our fair share of Windows Update threads.

One thing that I've only just picked up on in your CheckSUR log: Package Version 18.0. The latest version of the System Update Readiness Tool is Version 26, so you're a little out of date! I know it's a big download but I would highly recommend using the latest version here just to make sure we're scanning as thoroughly as possible. You might notice at the bottom of your CheckSUR log, in the Unavailable repair files section, each file is listed twice:

Code: 
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-Italian~31bf3856ad364e35~~~10.2.9200.16437.cat

This is one of the bugs that has been fixed since version 18 :)

Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2013] from Official Microsoft Download Centre

As for the errors found in your CheckSUR log, these are nothing to worry about and can safely be ignored. niemiro kindly looked into this for me and has concluded that this is due to a bug in the SURT (even in version 26) in how it detects the names of the IE10 packages. Microsoft is aware of this bug so I would expect this will be fixed in the next version of the SURT.

Tom
 
Hello Tom,
that's weird, because I actually run the version you linked (Windows6.1-KB947821-v26-x64.msu).
It's strange that's still version 18 and not 26.
But are you sure it should log "Package Version 26"?

fralken
 
Hi fralken,

Sorry for the confusion, strangely Package Version 18 is the latest version, despite the System Update Readiness Tool is in version 26. In all of the logs I've worked with in the past, I've never noticed the mismatch :p

Tom
 
Hi Tom,
ok then. Since both you and niemiro confirm that SURT error logs are false positives (and I agree), we can definitely say that this problem is solved.
Thank you very much for your great help, without it I would surely have to repair install windows.

fralken
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top