[SOLVED] Windows 7 x64 SP1 - W. Update service consumes 50% CPU, Update check never completes

K

kleena

Member
Joined
Jun 16, 2016
Posts
7
Hello,
since several weeks I've been having this problems. No updates have been downloaded sice, the Windows Update service takes a lot of CPU and when I start the "Check for updates", it doesn't seem to ever complete.
The usual "reregister Update components" batch file didn't help. DISM.exe /Online /Cleanup-image /Restorehealth ends with Error 87, "Restorehealth not recognized in this context".

The "Fixit" tool from a KB article ends with several things fixed, but "Error 0x800b0100 not fixed".

The tool "SFXFix.exe" by niemiro ended with 12 unfixed corruptions.

I will try to upload the logs right now.

If anyone has suggestions, please let me know, I'll be very grateful.

Thank you & cheers!

KK

Update: Since I do not see whether/where the SFXFix tool auto-uploaded my logs, I took whatever has todays date (there were some rather large CAB files with old dates too) and I'm posting it as attachment now.
View attachment CBS.rar
 
System Update Readiness Tool (SURT)

Download the latest version of the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

Windows Update Package Replacement

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 two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) using the MSU file downloaded earlier.
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log
View attachment Packs.zip
 
Hello,
thank you for your help. This is che CheckSUR.log I obtained after replacing the requested files and running the tool (which normally, too, searches for updates till the battery goes out, but finished rather quickly for one run just after the replacements).
Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-06-20 22:18

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x80070026     servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum         Line 1: XÍ
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat        

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest Zero Length    0x00000000     winsxs\Manifests\amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30.manifest      amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30     
(f)    CSI Manifest Zero Length    0x00000000     winsxs\Manifests\x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa.manifest      x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa     

Summary:
Seconds executed: 1803
 Found 4 errors
  CSI Manifest Zero Length Total count: 2
  CBS MUM Corrupt Total count: 1
  CBS Catalog Corrupt Total count: 1

Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30.manifest
    winsxs\manifests\x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa.manifest
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat
Thanks & cheers,
KK
 
Hmm... It doesn't appear that SURT actually replaced the files. :confused:

Could you verify that the .manifest files were placed in C:\Windows\Temp\CheckSur\Winsxs\Manifests, and the .cat and .mum files in C:\Windows\Temp\CheckSur\Servicing\Packages?
 
Hi!

I tried the same again, in the temp path there were no files before I copied in mine.
Upon starting, the SURT showed this prompt:
Code: 
---------------------------
Windows Update Standalone Installer
---------------------------
Do you want to install the following Windows software update?

                

    Hotfix for Windows (KB947821)


---------------------------
Yes   No   
---------------------------

then took a long tome to initialize th einstallation, then installed and said "...update was istalled...".
This is the log I have now:
Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-06-22 09:54

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x80070026    servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum        Line 1: XF
(f)    CBS Catalog Corrupt    0x800B0100    servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat        

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Manifest Zero Length    0x00000000    winsxs\Manifests\amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30.manifest    amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30    
(fix)    CSI Manifest Zero Length    CSI File Replaced    File: amd64_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_1a80fa6617c73a30.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab
(f)    CSI Manifest Zero Length    0x00000000    winsxs\Manifests\x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa.manifest    x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa    
(fix)    CSI Manifest Zero Length    CSI File Replaced    File: x86_microsoft-windows-wpd-legacywmdmcesp_31bf3856ad364e35_6.1.7601.18872_none_be625ee25f69c8fa.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab

Summary:
Seconds executed: 3262
 Found 4 errors
 Fixed 2 errors
  CSI Manifest Zero Length Total count: 2
  Fixed: CSI Manifest Zero Length.  Total count: 2
  CBS MUM Corrupt Total count: 1
  CBS Catalog Corrupt Total count: 1

Unavailable repair files:
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat

Did anything change?

Thanks & cheers,
KK
 
It did replace the manifest files, but not the catalog.

Let's perform the replacement with SFCFix, and then check with SURT again to verify.

SFCFix Script

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. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
View attachment SFCFix.zip

After SFCFix has completed, run SURT again.

When SURT has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
Upon seeing the script's log, it seems like I have not folowed your previous instructions properly - sorry!
I went with the script now and these ae the resulting logs:

SFCFix
Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-24 10:36:24.499
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\vk\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum

Successfully copied file C:\Users\vk\AppData\Local\niemiro\Archive\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat.
Successfully copied file C:\Users\vk\AppData\Local\niemiro\Archive\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum.

Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_for_KB3069762~31bf3856ad364e35~amd64~~6.1.1.0.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-06-24 10:36:27.375
Script hash: YKoa9YgbvZDC0Tr1lZIS4xpdKGNmSbQ19rTBh1jltKs=
----------------------EOF-----------------------

and CheckSUR.log
Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-06-24 10:58

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 4785
 No errors detected

Now there seem to be no errors left. Should I try to do a normal check for updates now, or it it still too early?

Thank you!
 
Looks good!

Do check for updates and attempt to install any that are offered.

If the installation fails or the check for updates doesn't complete, please zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.
If CBS.zip is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link.
 
Hello,
sorry for my late reply.
I have the check for updates running for about two days now (I have decided to let it run extra long after I saw another computer finally find them after a night and a day long checking session).

The check is still "running". By now, an icon has appeared in the notification area, saying that "New updates are available". When I click that icon, another window with the check progress bar shows.

Before the check, I tried the checkit script mentioned earlier. It reported two problems (service registration etc.) fixed.
I am attaching a packed CBS.log. Can you maybe find a hint of some problems still pertaining?

Thank you again!

Log coming here: View attachment CBS.rar
 
That seems to have worked - thank you!
KB3020369 showed some quirks while installing, the Standalone Installer would, in some situations, again never finish checking "updates on this computer".
Finally starting the installation after a clean restart did the magic.
KB3161647 the installed with no problem, after which I could find and install updates.

At some point a update recheck reported error #80244019, that one disappeared after a restart and I could install the last update batch.

Thank you again, I hope this topic can be finished now! :)
 
Glad to hear it!

I'll mark the thread solved. If you encounter any problems, please post back and I will continue to assist you.
 
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