Failing Updates - multitude of corrupt files in WinSXS

Hi tom982,

well not to be one to jump the gun, but I rebooted after posting and it's popped up about the updates and they've installed straight off the bat.

Thanks VERY much for your help, now Windows is stable I'll look at cloning to a new HDD :)

Regards

MarkieVee
 
Hi tom982,

sorry - one last thing ..

Code: 
=================================Checking System Update Readiness.
Binary Version 6.1.7601.18741
2016-08-09 14:52


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


Customer Experience report successfully uploaded.  Thank you for participating.  For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

Regards

MarkieVee
 
You'll be relieved to hear that this is nothing to worry about and is perfectly normal. It's just caused by the inconsistent nomenclature of these packages.
 
Huzzah!

Thanks tom982 - an absolute star and a legend :)

I'll stand you a pint anytime :)

Chiz

MarkieVee
 
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