GadgetAngel
New member
Hello,
I'm hoping some one here can help. I have tried everything.
I'm trying to install "Cumulative Security Update for Internet Explorer 10 for Windows 7 Service Pack 1 for x64-based systems (KB2879017)".
Windows Update throws error code 0x800700D.
So I run Microsoft System Update Readiness Tool (SUR) and I find the following message in the CheckSUR.log file:
"Checking Package Manifests and Catalogs
(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"
How do I fix this problem with the .mum file being the wrong name?
I have attached a picture of the Windows update error.
View attachment 289030
I have attached the CBS.log and the CheckSUR.log.
View attachment 289031
The text in the CBS.log file is too long to show but the text for the CheckSUR.log is as follows:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 20.0
2013-10-09 14:17
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(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
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 83
Found 1 errors
CBS MUM Corrupt Total count: 1
Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
=====================================================================
View attachment 289032
Any help in this matter would be appreciated.
I have had a real hard time getting this computer to install updates and had to reset windows components more than once. I really don't want to do that again.
This problem looks like the IE 10 install did not go correctly. So I need help fixing it. Anyone with an idea on how to fix the .mum file being the wrong name?
I'm hoping some one here can help. I have tried everything.
I'm trying to install "Cumulative Security Update for Internet Explorer 10 for Windows 7 Service Pack 1 for x64-based systems (KB2879017)".
Windows Update throws error code 0x800700D.
So I run Microsoft System Update Readiness Tool (SUR) and I find the following message in the CheckSUR.log file:
"Checking Package Manifests and Catalogs
(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"
How do I fix this problem with the .mum file being the wrong name?
I have attached a picture of the Windows update error.
View attachment 289030
I have attached the CBS.log and the CheckSUR.log.
View attachment 289031
The text in the CBS.log file is too long to show but the text for the CheckSUR.log is as follows:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 20.0
2013-10-09 14:17
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(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
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 83
Found 1 errors
CBS MUM Corrupt Total count: 1
Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
=====================================================================
View attachment 289032
Any help in this matter would be appreciated.
I have had a real hard time getting this computer to install updates and had to reset windows components more than once. I really don't want to do that again.
This problem looks like the IE 10 install did not go correctly. So I need help fixing it. Anyone with an idea on how to fix the .mum file being the wrong name?
My Computer
At a glance
Windows 7 SP1 x64 OS installed on Intel Solid...Intel Core 2 QUAD Pro-Q9550S 2.83 GHz with 12...8192 MB - tested with memtest86+ and it passe...none, on motherboard Intel Q35 Express Chipset
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Intel DQ35JO motherboard, case manufacturer is unknown
- OS
- Windows 7 SP1 x64 OS installed on Intel Solid State drive -480 GB
- CPU
- Intel Core 2 QUAD Pro-Q9550S 2.83 GHz with 12MB Cache, 65W
- Motherboard
- Intel DQ35JO version D82085-804
- Memory
- 8192 MB - tested with memtest86+ and it passed, 800 MHz
- Graphics Card(s)
- none, on motherboard Intel Q35 Express Chipset
- Hard Drives
- ACHI enabled
Intel SSDSC2CW480A3 - Solid State Drive (SSD) 480 GB -OS installed on Solid State Drive
ST3500320AS - 500 GB
ST3120026AS - 120 GB
- Case
- Unknown
- Cooling
- CPU Intel fan, Two case fans push pull configuration
- Keyboard
- old PS2 keyboard via PS2 to USB adapter
- Mouse
- Logitech Marble Mouse ball
- Internet Speed
- 10/100/1000 via Intel 82566DM-2 Gigabit Network Connection
- Antivirus
- MS Security Essentials
- Browser
- IE 10 or Google Chrome v30.0.1599.69 m
- Other Info
- Latest BIOS updated from the Intel website. I know the memory is good because at first I could not install Windows 7 x64 due to memory stick problems. One of the memory sticks had to be replaced. Re-ran memtest86+ to ensure that the new stick was good and it ran all night with out error.
