[SOLVED] CheckSUR IE-Hyphenation and IE-Spelling Unavailable repair files

[SplinteredEdge]

Greeting SysNative :thumbsup2:

A pleasure to meet you fine folks. In my searches today I have found that the community here at SysNative might just be the best at repairing component and package corruption. Lucky for me I have a distinct feeling that you might have ran into my issue before. I apologize if this takes the form of a repost, however after reading some threads here in the forum is seems that I wouldn't want to pilot the SFCfix tools without some collaboration.

Lets start with those system specs:

Windows 7 Professional vl x64 (SP1 - 6.1.7601.17514) - Timestamped 4/12/2011

• Windows 7 is current installed on a laptop for use as a Imaging Master - Currently in Audit Mode via a simple unattend.xml.
• From Audit mode, i allowed the system to rest over night and then installed the following this morning:

Windows6.1-KB947821-v34-x64.msu, Windows6.1-KB2966583-x64.msu, and WindowsUpdateAgent-7.6-x64.exe​

• I then rebooted and ran Microsoft Update to completion; I excluded drivers and MSE. This was successful for all passes. Reboot.
• CleanMGR was ran a few times to clean up Windows update cruft. I have been as careful as I know how. CleanMGR = Big CBS log.
• I noticed a very large CBS.log which lead me to clear the log and rerun checksur from the MSU. I then looked at the CHECKSUR.LOG to find the following errors:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2015-10-29 16:08


Checking Windows Servicing Packages


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


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 186
 Found 2 errors
  CBS MUM Corrupt Total count: 2


Unavailable repair files:
	servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
	servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
	servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
	servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

Everything seems to work, but this error is digging into the fabric of my being. I am happy to run or test anything. I will be making a DISM capture of this disk first thing tommorow morning so that we can have some fun.

Okay here is the info on my attached logs:

• Ran CHKDSK C: /x /f and rebooted, scan was happy with no errors or bad sectors.
• I cleared CBS and CheckSUR logs
• I cleared C:\Windows\Temp
• ReRan SFC /SCANOW to generate a nice CBS.log (655k) - No corruption detected
• ReRan Windows6.1-KB947821-v34-x64.msu to generate a new CheckSUR.log - No corruption detected - CheckSUR.log
• ReRan DISM /online /cleanup-image /scanhealth (Windows 7 version) - Corruption was indeed detected - CheckSUR.log
• ReRan DISM /online /cleanup-image /scanhealth (Win 10 ADK version) - Corruption was indeed detected - CheckSUR.log

 

[SplinteredEdge]

Bump

 

[SplinteredEdge]

I went ahead and ran the tests again with the same results. SFCFix.txt now attached with an updated CBS.zip.

 

[BrianDrab]

Hi and welcome to Sysnative. Please do the following.

Step#1 - Fix Corrupt/Missing Files
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the attached file, Packs.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing the folder Packages
5. Open the Packages folder and copy the files into the following folder. If the Packages folder doesn't exist within Servicing you will need to create it.
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
6. Run the System Update Readiness Tool (SURT) again.
7. When the SURT finishes installing, zip up and attach the following log file:
   C:\Windows\Logs\CBS\CheckSUR.log

 

[SplinteredEdge]

Thanks for the response BrianDrab. I am getting started with this now and expect some results in about 15 minutes. I will report back immediatly.

 

[SplinteredEdge]

I copied these packages into C:\Temp\CheckSUR\Packages C:\Windows\Temp\CheckSUR\Packages as intended and then completed the followinging in this order:

· I cleared CBS and CheckSUR logs
· ReRan CheckSUR (Windows6.1-KB947821-v34-x64.msu) - No corruption detected - CheckSUR.log
· ReRan DISM /online /cleanup-image /scanhealth - Corruption was indeed detected - CheckSUR.log

The results are very similar.
CheckSUR, no issues found.
DISM /online /cleanup-image /scanhealth; same issues found.

CheckSUR Results

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-11-02 10:54


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 226
 No errors detected

DISM /online /cleanup-image /scanhealth

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2015-11-02 10:59


Checking Windows Servicing Packages


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


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 82
 Found 2 errors
  CBS MUM Corrupt Total count: 2


Unavailable repair files:
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

New CBS.ZIP attached, I'm happy to try any other suggestions. My research shows that we might be fighting a long standing bug with Win7 and not an actually broken package.

Thanks for your help so far, please let me know what you think.

 

[BrianDrab]

I copied these packages into C:\Temp\CheckSUR\Packages as intended and then completed the followinging in this order:

You need to ensure you copy them into C:\Windows\Temp\CheckSUR\Packages

 

[SplinteredEdge]

I apologize for mistyping, the correct path is C:\Windows\Temp\CheckSUR\Packages as you have provided. This is indeed the path used during my last round of testing.

 

[BrianDrab]

Thank you. It appears that these errors in the log are benign and nothing to be worried about. They shouldn't affect the operation of your Windows Update. It's a false/positive with IE11 detection.

 

[SplinteredEdge]

:thumbsup2: I have to agree, BrianDrab :thumbsup2:

Thank you for the piece of mind and expert collaboration. I hope that this post can be used as a way to advise anyone in the future else who might experience this same issue. This appears to be present on all Windows 7 systems that are upgraded fully via windows update. The only time these errors are not present are when alternative means are used to update the system.