Windows update agent 7.6 taking all of my CPU resources

[HK2015]

I installed new clean windows 7 ultimate a few days. Everything was ok. Installed well. Activated well. Getting windows update well. After service pack 1 was installed successfully, a new version of windows update agent 7.6 was installed and then the whole problem started.

Every time I start my computer, it is running in the background eating all of my cpu resources. CPU usage always goes up 100%. So I can barely use other programs. So I changed the update setting to only to "check updates but not install or download". But the problem remains the same. Still using 100% CPU cycles. (100% CPU usage constantly, all the time, every second and minute). Although it uses 100% resources, it downloads and installs update extremely slowly. I still have nearly 200 update to install.

When I stop the windoows update service using "services" program, cpu usage dropped down to 0-20%. If I put windows update setting to "never check windoows update" and disable windows update service completely then the problem is solved on next boot. But this is not the solution.

I know this is a common issue in window XP and it was fixed in the windows updates for XP I think. I am suprised to see this problem in windows 7 ultimate. I searched for the solution online but no solution was found for windows 7. I did find several discussions and solutions for windows XP. But not for windows 7.

 

[NoelDP]

This is often caused by corruption of some of the update's files.

Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Please also post the C:\Windows\windowsudpate.log file

 

[HK2015]

Thank you for your reply.
I uploaded zip for my first old 3 CBS files to my first post.
And zip for remaining latest 3 CBS files here.
But somehow zip from my first post was removed.
So I edited this second post and uploaded the zip for latest 3 cbs files here.

 

[NoelDP]

There don't appear to be any results from a CheckSUR/SURT scan - and no results of an SFC /SCANNOW either.
There are no files attached to your first post that I can see.

Please post the requested data after running the requested tools, and also post the windowsupdate.log file as requested.

 

[HK2015]

I followed the instructions to run sfc/scannow.
But when I run cmd sfc command, it said I must be an administrator running a console section.
My account is the only account in this computer and it is the administrator account.

 

[NoelDP]

You must still use the instructions and run as Admin.

 

[HK2015]

1) I managed to run sfc/scannnow with admin rights.
I simply located the cmd file in system32 folder and right click then chose "run as administrator".
Result of the scan: corruptions detected and unable to repair. Reports can be viewed in CBS files.

2) System update readiness tool was successfull installed.

So I attached the following files with this reply:
-CBS folder
-Windows update log

 

[NoelDP]

CheckSUR is clear.
Here's the summary of the SFC scan results...

 Line 159111: 2015-05-12 20:34:28, Info                  CSI    0000062f [SR] Repairing 4 components
 Line 159112: 2015-05-12 20:34:28, Info                  CSI    00000630 [SR] Beginning Verify and Repair transaction
 Line 159115: 2015-05-12 20:34:28, Info                  CSI    00000632 [SR] Cannot repair member file [l:34{17}]"windeploy.exe.mui" of Microsoft-Windows-Setup-Component.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159118: 2015-05-12 20:34:28, Info                  CSI    00000634 [SR] Cannot repair member file [l:32{16}]"WinLGDep.dll.mui" of Microsoft-Windows-Setup-Component.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159121: 2015-05-12 20:34:28, Info                  CSI    00000636 [SR] Cannot repair member file [l:26{13}]"audit.exe.mui" of Microsoft-Windows-Setup-Component.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159124: 2015-05-12 20:34:28, Info                  CSI    00000638 [SR] Cannot repair member file [l:26{13}]"setup.exe.mui" of Microsoft-Windows-Setup-Component.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159127: 2015-05-12 20:34:28, Info                  CSI    0000063a [SR] Cannot repair member file [l:32{16}]"W32UIRes.dll.mui" of Microsoft-Windows-Setup-Component.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159130: 2015-05-12 20:34:28, Info                  CSI    0000063c [SR] Cannot repair member file [l:30{15}]"oobeldr.exe.mui" of Microsoft-Windows-Setup-Component.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159133: 2015-05-12 20:34:29, Info                  CSI    0000063e [SR] Cannot repair member file [l:24{12}]"spwizimg.dll" of Microsoft-Windows-Setup-Navigation-Wizard-Framework, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159136: 2015-05-12 20:34:29, Info                  CSI    00000640 [SR] Cannot repair member file [l:24{12}]"W32UIRes.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 159139: 2015-05-12 20:34:30, Info                  CSI    00000642 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol later

 

[HK2015]

Thank you.
I'll be looking forward to it.

 

[NoelDP]

I've uploaded a file - hk2aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\hk2aa
hit the enter key - if you get a 'Not Found' error try
DIR D:\hk2aa
or
DIR E:\hk2aa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\hk2aa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply