I have Windows 7 32bit SP1
I have svchost.exe running at 237,736 k which I assume is Windows update Tuesday for the month of March trying to push through. Fan is running hard and machine temp is up. Updates are trying to be found and it's been searching for over an hour and a half. It's never taken that long before.
I killed the process and ran the dism tool to see what's going on. I get the following errors when running dism /online /cleanup-image /scanhealth
CheckSUR file:
~ ~ ~
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2016-03-08 23:50
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: 590
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
~ ~ ~
Last successful update was on 2/10/16
sfc /scannow doesn't detect anything wrong.
Is this log file up above related to Windows updates being searched for but not found? Or could it be the update servers are extremely busy right now?
How do I fix this?
Thanks...
I have svchost.exe running at 237,736 k which I assume is Windows update Tuesday for the month of March trying to push through. Fan is running hard and machine temp is up. Updates are trying to be found and it's been searching for over an hour and a half. It's never taken that long before.
I killed the process and ran the dism tool to see what's going on. I get the following errors when running dism /online /cleanup-image /scanhealth
CheckSUR file:
~ ~ ~
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2016-03-08 23:50
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: 590
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
~ ~ ~
Last successful update was on 2/10/16
sfc /scannow doesn't detect anything wrong.
Is this log file up above related to Windows updates being searched for but not found? Or could it be the update servers are extremely busy right now?
How do I fix this?
Thanks...