Mum not found in the KB cab

OK - CheckSUR run... and has the same results as you do!

Code:

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

This looks to me as if it may be a hangover from the Win8 version which has multiple language options.....
I'll have a play...
first - actually run IE10 for the first time...
then do another check for updates....
nothing found.
(doublechecking -KB2680838 is NOT installed, but it is no longer offered!?! - it was an optional update previous to the IE10 install)




There is one thing in the registry - the InstallName is 'update.mum' rather than a proper filename - so it may be that causing the problem...
test that...
change it to Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
..and run CheckSUR again.....

..that was a bust!
OK - change the mum file instead.....

Nope - it might have cured it, but it also creates another error (as is to be expected)

I think this is one of MS's famous 'by design' things :) - and best left alone, so long as it doesn't interfere with anything else.

Check the Installed Updates listing, rather than the History - does it show in there??

..and doing a Check for Updates doesn't see it?

Please run Belarc Advisor - www.belarc.com - and see what it reports for it (don't post the report, as it contains your product Keys for Windows, Office and many more!)

OK - so what's the exact error currently when you attempt to install KB2790113?