[SOLVED] Windows 7 x64 Update endless loop

L

lightning

Member
Joined
May 17, 2016
Posts
10
Hi! Once started my Windows Update service seems to be running forever (well, I usually stop it after a few minutes) consuming one logical CPU and up to 1 GB of RAM. It also used to create huge (several GB) CBS logs but I've turned them off in the registry (I've turned them back for this report).

Based on this forum I've downloaded the System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821): it detected 13 Missing Winning Component Key errors (see attachment: CBS.zip/CheckSUR.log).

Could you please help?

SFCFix result:
Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-05-17 21:29:32.707
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     0
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          13
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-05-17 21:30:02.772
----------------------EOF-----------------------

 

Attachments

Hi and welcome to Sysnative. Please start with the following.

Code: 
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.18912_none_121e94c25bb5b52f  
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.18912_none_c947d475d6b16956  
(f) CSI Missing Winning Component Key 0x00000000 x86_wpf-reachframework_31bf3856ad364e35_6.1.7601.18842_none_020f13ad8715cbaa  
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-msxml30_31bf3856ad364e35_6.1.7601.18782_none_e6468305adb05155  
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18912_none_8a8eeb0ba044fe8c  
(f) CSI Missing Winning Component Key 0x00000000 amd64_presentationcore_31bf3856ad364e35_6.1.7601.18842_none_0a349640a6ae05f8  
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-msxml30_31bf3856ad364e35_6.1.7601.18431_none_e67b8ca5ad88b4d4  
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.18201_none_95dc85beb07c0dc5  
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18912_none_046e806d736c9e06  
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.18912_none_e52b8cd0ad8ceae3  
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7601.18923_none_1241e8d3a58fba5f  
(f) CSI Missing Winning Component Key 0x00000000 x86_wpf-windowsbase_31bf3856ad364e35_6.1.7601.18842_none_5951f561a6226ac5  
(f) CSI Missing Winning Component Key 0x00000000 amd64_wpf-penimc_31bf3856ad364e35_6.1.7601.18842_none_09b496e91b679065

Remove Update Manually
 1. Click on the Start
Start%20Orb.jpg
button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, press enter
wusa /uninstall /KB:3057154

4. Let me know if it says it was successful or if there are any errors.
 
Thanks. Please do the following.

Retrieve Components/Software Hives
Note: The Software have has confidential and sensitive information in it so please send me a PM with a link to that particular hive so it's not in the public form.
  • Please download the Freeware RegBak from here: Acelogix Software - Download products
     You will find it at the bottom of the page that the link brings you to.
  • Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
  • Click the New Backup button. Accept the defaults and simply click Start.
  • When it says Finished successfully, click the Close button.
  • This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
  • This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, two of which are named COMPONENTS and SOFTWARE.
  • Copy these two files to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
  • Now right click on these files on your desktop and select Send to > Compressed (zipped) folder.
  • Then please upload the zip file(s) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
  • You can close any open windows you have as well as the RegBack program now.
 
Thanks. I'd like to try something. Please do the following. I'd like to see the results in the log.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

Result:
Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2016-05-22 01:04:47.327
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at SFCScript.txt [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-rpc-local_31bf3856ad364e35_none_470716a172349439\6.1.


Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-rpc-local_31bf3856ad364e35_none_470716a172349439\6.1.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-rpc-local_31bf3856ad364e35_none_470716a172349439\6.1.
RegistryScript:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-05-22 01:04:47.390
Script hash: cczhxDC0LeghDT0VqpARHd+Z/mYZdkxm3S9/azp88Lk=
----------------------EOF-----------------------
 
Good. Now let's do the following again.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Excellent. Let's see if this gets the rest.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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

Step#2 - System Update Readiness Tool (SUR)
 1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Items for your next post
1. SFCFix.txt
2. CheckSUR.log
 

Attachments

All remaining errors are gone. Thanks!

Btw. what was the reason behind these errors? Simply a few missing default entries in the registry?
 

Attachments

Actually the issue appears to be that an update didn't properly remove remnants in the registry so we had to manually remove them.

Are you having any other issues?
 
(The official answer from the Microsoft support was to reinstall my op. sys.... just because they were unable to remove an update and to take responsibility for the mistake.)

Unfortunately the original symptom is still present: the update (wuauserv) service still consumes one full CPU thread for undefined time...
CBS.log is much smaller, both sfc /scannow and checksur /scannow reports no errors.
I've reset (again) Windows\SoftwareDistribution and Windows\System32\catroot2, but CBS.log is still full of the following errors:
Code: 
Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
[...]
Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]

I've also run the Windows Update troubleshooter (https://support.microsoft.com/en-us/kb/971058), it reported error 0x80080005...

I've also read that someone has had similar issue after changing (?) the access rights of System Volume Information (http://answers.microsoft.com/en-us/...-065144a/f88b7a31-7698-4192-8035-212797cc89ae). Well I have added some extra permissions to this folder (I prefer to check easily the current size of the System Restore points), but I did this a few years ago, and System still has Full control permission (so I've kept my current settings).
 
OK, here's what I would like you to do.

Step#1 - Run Windows Repairs
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 Windows Repair (All-in-One) Portable to your desktop.
2. Once the file is downloaded, right-click on the file on your desktop and choose Extract All...


Extract.JPG

3. Keep the defaults and click the Extract button.
4. A folder named tweaking.com_windows_repair_aio will be extracted to the desktop. Once the extraction is complete the folder will open.
5. Inside this folder, there is a folder named Tweaking.com - Windows Repair. Open this folder as well.
Capture.JPG



6. Double-click on Repair_Windows.exe to open. Note: Please make sure all of your programs are closed and anything you were working on is saved as we will be rebooting.
7. When the program opens, click the Reboot to Safe Mode button at the bottom of the screen. Answer Yes to allow.
8. Once rebooted into Safe Mode, open the program again. When the program opens, click the Repairs tab and click the Open Repairs button.
9. A backup of your registry will be made. After a few moments you will have many options from which you can choose.
10. Please click the Unselect All button and then click to enable only the following ones:

03 - Reset Service Permissions
04 - Register System Files
05 - Repair WMI
10 - Remove Policies Set By Infection
14 - Remove Temp Files
15 - Repair Proxy Settings
17 - Repair Windows Updates
21 - Repair MSI (Windows Installer)


11. Ensure the Restart check box is selected and click the Start Repairs button in the lower right of the screen. This may take some time to run so be patient.
StartRepairsWithReboot.JPG

12. Once the fixes are complete you will be prompted to restart your machine. Answer Yes.

Step#2 - Check for Updates
Now check for Windows Updates. Because of the fixes we did in Step#1, it will take extra long the first time. If possible I would like you to start it at night before you go to bed and let it run all night. Let me know how many updates appear in the list that need to be installed.

Thanks.
 
It did not help... Once DataStore.edb is rebuilt the Windows Update (wuauserv) service is stuck again: no network or disk I/O, one full CPU thread for 30 minutes... and only then did show up the list of updates: 15 important and 3 optional updates in total, all of them published after May 1st, 2016, and one more optional from January.
A few minutes later the Windows Update process is back on stressing the CPU again...
 
Can you please go ahead and install all critical/important and optional updates? Once installed, check for Windows Updates again to see if there are any more and the continue to install/check for updates until there are no more left.

Thanks.
 
After waiting for the update service for ~30 minutes to stop stressing the CPU, finally it has started the download, and I was able to install the updates. CBS.log has grown to 500+ MB in the meanwhile.

Right now, when I restart the update service it does not step into an aforementioned seemingly endless loop, and CBS.log grows only by 200KB.
However if there was no update service specific fix delivered through Windows Update in May, I don't see why wouldn't this endless loop occur again next time.

Thank You for your help!
 
That's what I suspected. If your updates are current you don't see the issue when checking for updates. There are many complaints of this currently going on and getting worse. As long as you keep current on updates you should only experience this once a month when you install updates. See the following for more info.

The Convenience Rollup Makes a Big Difference, But Windows 7 Updating is Still Broken - Thurrott.com
Win7 Windows Update once again taking forever @ AskWoody
Updates taking a long time to install in Windows Server 28 R2 | Ask the Core Team
 
I've always kept my Windows up-to-date, but simply don't have 30 minutes/day for checking for updates (even if there are no updates to install). However it's much better now after your Missing Winning Component Key fixes.
Thank 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