[SOLVED] Win7 Windows Update stalled - wuauserv->svchost.exe to 100% of 1 core

S

Syntony

Member
Joined
Jun 20, 2016
Posts
11
Location
London
Windows 7 Windows Update glitched attempting to install latest updates on my laptop (it hung attempting to download the first update), following which it simply loops for ever driving one core to 100% 'checking for updates'.

SFCFix shows SURT corruptions:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-21 23:26:02.789
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: 7
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-06-21 23:31:28.921
----------------------EOF-----------------------

Zipped CBS folder attached.

Windows Update is currently turned off, so assistance with this would be very gratefully received...

Tony
 
Hi and welcome to Sysnative. Sorry for the delay. If you are still in need of assistance, please do the following.

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

Many thanks for the response - I certainly don't mind waiting to get this sorted! As luck would have it I'm on the road at the moment and don't have reliable Internet or an alternative machine, so if you don't mind I'll wait a couple of days till I'm back at home base before I activate the script. I'll post again as soon as I have the results.

Tony
 
OK, back at base now. The script you supplied produced the following SFCFix.txt:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-28 23:20:20.179
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Master\Desktop\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\438bdea041e..b7d5c290482_31bf3856ad364e35_6.1.7601.18915_fd5580292c2f81f8.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a0d9c99ae5f..050cba47354_31bf3856ad364e35_6.1.7601.18915_e458ac8d407c36fd.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f701df9b3f1..a7d9f18ac91_31bf3856ad364e35_6.1.7601.18915_eaef43ad6bba2d6e.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\df162f3ee21..b00835066cd_31bf3856ad364e35_6.1.7601.19091_149edb2b0765ef46.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b7ce65a4f29..82e1ffc2621_31bf3856ad364e35_6.1.7601.18915_365841be2597d1e2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a3455e0a58e..7b72e53f185_31bf3856ad364e35_6.1.7601.19020_cdee4d17051f7293.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\438bdea041e..b7d5c290482_31bf3856ad364e35_6.1.7601.18915_fd5580292c2f81f8.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a0d9c99ae5f..050cba47354_31bf3856ad364e35_6.1.7601.18915_e458ac8d407c36fd.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f701df9b3f1..a7d9f18ac91_31bf3856ad364e35_6.1.7601.18915_eaef43ad6bba2d6e.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\df162f3ee21..b00835066cd_31bf3856ad364e35_6.1.7601.19091_149edb2b0765ef46.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b7ce65a4f29..82e1ffc2621_31bf3856ad364e35_6.1.7601.18915_365841be2597d1e2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a3455e0a58e..7b72e53f185_31bf3856ad364e35_6.1.7601.19020_cdee4d17051f7293.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2016-06-28 23:20:26.143
Script hash: wbgVwDE9ZXET+LRP8sJxsap1tuHB/5OwiUhd/3mcSO0=
----------------------EOF-----------------------

Thanks, Tony
 
Thanks. Please do the following so we can see the remaining corruptions.

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.
 
The System Update Readiness Tool (SUR) took over 90 minutes to complete, so the need for sleep intervened...

The CheckSUR.log file generated is attached.

Thanks, Tony
 

Attachments

Excellent.
Code: 
Seconds executed: 5504
 Found 8 errors
 Fixed 8 errors

Please check for Windows Updates and let me know how it goes.
 
I started Windows Update, which ran for quite a long time (about an hour?), but then failed Error: 80080005

I ran SFC /scannow to check for system file inconsistencies, but it didn't find any problems

Thanks, Tony
 
OK, please do the following.

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:

04 - Register System Files
05 - Repair WMI
06 - Repair Windows Firewall
10 - Remove Policies Set By Infection
14 - Remove Temp Files
15 - Repair Proxy Settings
17 - Repair Windows Updates



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.
 
OK. Now we want to check for Windows Updates again. Keep in mind that it will take much longer than normal the first time because of the fixes we just did. The Windows Update cache has to be completely rebuilt. I've had it take up to 12 hours before. All depends on the hardware you have and the internet connection speed you have. Some finish in an hour. If it takes a long time, I usually tell people to change the power settings on the computer so it doesn't go to sleep and let it run overnight. 9 times out of 10 this works.

Yours may be quicker though so let's find out.
 
Thanks, Brian. Windows Update is now running. I've had to rebuild the Windows Update cache once before, and I'd suspect that the 12 hours won't be too far out!

Tony
 
OK, the Windows Update run to repopulate the Windows Update cache did complete eventually - I wasn't around to see, but the time-stamp on DataStore.edb indicated that it ran for about 18 hours... Windows Update also found 2 'Optional' updates (one of which was Windows 10 upgrade, the other to fix slow Windows Update problems, amongst others), and 13 Important updates.

I then made the mistake of trying 'search for updates' again, to check that it really was working - a mistake because it ran for another 18 or so hours! At least it did complete and found the same updates available.

I took a look at the CBS.log file and it does still show some 'unable to open package' errors during the Windows Update 'search for updates' rerun.

Tony
 
The "unable to open package" errors are normal. Go ahead and select to install the important updates as well as the optional Windows Update slow fix one. Let me know how it goes.
 
Thanks Brian,

When I started the updates, it was pretty clear that nothing was going to happen very fast, so I decided to run the KB3161608 fix (slow Windows Update etc.) as a standalone update instead, since it gives more information on where it's got to. It's currently indicating 'Searching for updates on this computer...', so it looks like it may well be another 18 hour run. When that's done I'll install the 'Important updates' in the normal way, so I'll get to see how effective the fix is.

This could take some time!

Tony
 
From the time-stamp on DataStore.edb the stand-alone update for the KB3161608 fix was ready to install in a little less than 8 hours...(!) On rebooting following the fix install, Windows Update posted an alert for the outstanding updates, plus one new one (virus definition update) within a couple of minutes, which seemed like good news.

Installing the 14 updates (which included some big ones) took less than an hour including 2 reboots (four of the updates failed error 800F0902 - Installer is already busy - first time through and had to be re-run).

Windows Update 'Check for updates...' now completes in 90 seconds rather than 18 hours (a 740-fold improvement I calculate), and the KB3161608 fix also seems to speed up some other processes (such as Windows Defender 'Quick Scan' by a factor of around 5).

Best of all, though, is that Windows Update is apparently now back in a fully working state, so many many thanks for all the assistance in achieving this!

Tony
 
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