Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

What actually causes wuauserv high CPU use updating Windows


  • Please log in to reply
40 replies to this topic

#1 uberbleeper

uberbleeper

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:42 AM

Posted 18 July 2016 - 05:22 PM

I've read posts all over the internet about (mostly Vista & Win7) high CPU use - searching updates & it hanging forever.

Never read any attempt at explaining actual cause of high CPU use for svchost & wuauserv service.

  I read the post on manually d/l Vista kernel updates & installing 1st, then running update - not tried it yet.  Before I do that, have couple of questions.

  But, the update hanging problem only affects my 32 bit CPU, 32 bit OS Vista laptop - not my Vista x-64, Quad core machine.

 

I tried everything, including all the MS update Fixit (2 diff ones) & System Update Readiness tools., ran SFC a few times, manual resetting of update components, renaming Software Distribution & Catroot2 folders, re-registering dll's, stopping / starting services - BITS, Cryptoserv, Windows Update;  reinstalling Windows Update Agent (already had latest ver) - no joy.

FYI,  the WindowsUpdateAgent-7.6-x86.exe (in 32 bit OS), didn't change any dates on update files in System 32.  Unless it just "checked if they existed," & skipped them, didn't appear to change anything.

 

 

 I'm curious why  the 32 bit Vista, 2 core machine - needs 50 - 60% CPU - for 12, 18, 24 hrs & still never finishes. 

But my Quad core, Vista x64 box, barely uses any CPU & finishes finding updates in a tiny fraction of the time.  Spiking a few sec. to 13% on one core, then way less most the time is normal on it.  Often drops to 0 CPU for several sec.  It might use 2 - 6% and is not constant, like the dual core laptop is.   If MS limiting BW on Vista, W7 updates is the problem, a quad core wouldn't finish searching a lot faster that a dual core.   I don't think it takes much resources just to search?

 

My quad core's got more CPU power, but not where the dual core should use 50 - 60% CPU for 18 to 24 hrs straight & still never finish, where the quad core barely uses any..

 

One recent update attempt on the laptop, control panel UI said no updates found (there were some) - Event Viewer said 31 updates detected, but none installed.  No errors on failed installations - anywhere I found.  This lead me to suspect corrupted update downloader or installer dll files.

 

?? Not sure if I should BU & delete the 8 or so WU dll files in system 32, then re-run the update agent installer?

 

Thanks.

 

 



BC AdBot (Login to Remove)

 


#2 lmacri

lmacri

  • Members
  • 407 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Canada
  • Local time:09:42 AM

Posted 18 July 2016 - 09:39 PM

Hi uberbleeper:

During these "Checking for updates..." hangs on my 32-bit Vista machine I see constant consumption of ~ 50% of my CPU by the Windows Update service (wuauserv) running under the svchost.exe process (i.e., complete saturation of one of my dual cores).  Sysinternal's Process Explorer shows that all this CPU is consumed by a thread for the Windows Update Agent (wuaueng.dll).  Post # 6 of Kayla's thread Processes in Task Manager During Updates in the VistaForums has instructions on how to confirm this on your own machine(s).

 

Attached File  WU PE svchost wuauserv 14 Apr 2016.png   60KB   1 downloads

 

The problem seems to be more prevalent on affected machines with slower CPUs and limited amounts of RAM.  A single core CPU will show 100% saturation while a dual core CPU will show 50% saturation.  Here's a screenshot of  the CPU consumption for my February 2016 Patch Tuesday update.  The initial "Checking for updates..." phase took just under 3 hours that month, with the svchost.exe process constantly consuming ~50% of my CPU (saturation of one of my dual cores). Once "Checking for updates..." finished around the 40 min mark, download and installation of 13 important updates completed between the 40 and 10 min marks. The dark grey band at the 5 min mark was the system restart to finish the installation.

 

Attached File  Windows Update A svchost Edited 10 Feb 2016.png   29.2KB   3 downloads

As noted in Kayla's thread, the Windows Update Agent (WUA) at C:\Windows\system32\wuaueng.dll on my 32-bit Vista system is currently v7.6.7600.256 and hasn't been updated since June 2012. I suspect there will be no permanent fix for this problem unless Microsoft releases an update for the WUA for Vista before extended support ends on 11-Apr-2017.

Fortunately, the temporary workaround posted at http://wu.krelay.de/en/ to pre-install missing Windows kernel-mode driver (Win32K.sys) updates before running Windows Updates does seem to solve these "Checking for update..." hangs for most Vista users.  Try the step-by-step instructions posted 16-Jun-2016 in m#l's thread Updates not working, it has been searching for updates for hours and post back if you run into any problems.  I was fully patched as of June 2016 so I only had to pre-install this month's KB3168965 (MS16-090: Description of the security update for Windows kernel-mode drivers: July 12, 2016).  The initial "Checking for updates..." phase for my July 2016 Patch Tuesday updates completed in ~ 20 min (compared to 5 or 6 hours for April and May) and my entire Windows Update session, including download and installation of seven important updates, finished in under one hour.

------------
32-bit Vista Home Premium SP2 * Firefox v47.0.1 * NIS v22.7.0.76 * MBAM Premium v2.2.1

HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS


Edited by lmacri, 18 July 2016 - 09:46 PM.


#3 uberbleeper

uberbleeper
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:42 AM

Posted 18 July 2016 - 11:38 PM

Thanks Imacri.  Unfortunately, I've read that... & much, much more than I ever wanted to on update problems.

I know which service / DLL is using the high CPU.   I was curious about why.  Why would it take such large resources just to search a very small part of MS database?

What would the CPU be doing for 12 to 24 hrs at 50 - 60% capacity?   Maybe another MS change - another update? - broke the update agent?  There's no reason it'd  need those CPU resources for hours on end.

 

The length of time doesn't bother me as much as constant excessive CPU use for a day.  I've checked read / write bytes on wuauserv & wuaueng.dll while the CPU is high - there's generally little being written & there's very little bandwidth being used.

No  complicated calculations or extensive graphics.    Maybe for a bit, if it started d/l'g large files.

 

I copied  entries from windowsupdate log - from a week or so ago.  Log (& event viewer) reported 32 updates found.  Never showed them in control panel & didn't install.  Next time I opened update UI, it didn't remember them.

 

So this isn't just a matter of "letting it run."  Something else is broken / off, but I've pretty  much replaced, fixed or reinstalled everything - unless a little known setting is wrong.

The log remarks are kind of cryptic on what happened.  Maybe someone has seen it before & can interpret.   I'll post tmrw - I'm beat.



#4 lmacri

lmacri

  • Members
  • 407 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Canada
  • Local time:09:42 AM

Posted 19 July 2016 - 07:35 AM

I know which service / DLL is using the high CPU.   I was curious about why.  Why would it take such large resources just to search a very small part of MS database?

What would the CPU be doing for 12 to 24 hrs at 50 - 60% capacity?   Maybe another MS change - another update? - broke the update agent?  There's no reason it'd  need those CPU resources for hours on end.

 

Hi uberbleeper:

 

That's a very good question, and I've never seen a definitive answer as to "why" the Vista Windows Update Agent (wuaueng.dll) is currently having problems searching for updates.  My "Checking for updates..." hangs started during my Aug 2015 Patch Tuesday updates, which is the first Patch Tuesday after the official release of Windows 10 on 29-Jul-2015, but I have no proof that there's a connection.

 

From Woody Leonhard's Woody on Windows InfoWorld blog in his 22-Jun-2016 entry Microsoft releases KB 3161647, KB 3161608 to fix slow Windows 7 update scans:

 

"But what really got my goat: Those hours-long waits generally involved the computer just sitting there. There was little activity over the internet, almost no activity on the PC, while "check for updates" kept checking and checking and checking. Millions of people were sitting, hour upon hour, waiting for Microsoft's servers in the sky to get their act together."

 

That concurs with what I observed in my own Windows Update log - see my post # 162 in ScousaJAY's VistaForum thread windows update just seems to hang while checking. I can see Protocol Talker synchronizing the list of updates with the local database on the client computer (+++ PT: Synchronizing extended update info +++) and a dozen or so entries where DtaStor handles the database transactions to add URLs for new updates posted since the last Windows Update (e.g., http:// download.windowsupdate.com/c/msdownload/update/software/updt/2016/03/windows6.0-kb3147071...). Then there's a huge gap of several hours (no warnings, no errors) before the next timestamp shows that Agent (the Windows Update Agent) has finished searching for available updates.  There's little read/write activity on my hard drive during this time gap - just the Windows Update Agent chewing up CPU and my cooling fan running in overdrive.  As that post notes, Win XP had a similar problem three years ago after Win 8.1 was released and Microsoft eventually released a patch - likely because Win XP had (and still has) a large marketshare worldwide.

 

From Dalai's workaround at http://wu.krelay.de/en/ mentioned in my previous post:

 

"The term "solution" might be a little bit exaggerated, since the following HowTo only tries to make sure that the Update Agent doesn't need to check all updates, so the check for new updates is done faster. Futhermore, it's only a temporary solution; most likely the issue will appear again with the next Patchday."

 

I'd still suggest that users try the step-by-step instructions posted 16-Jun-2016 in m#l's thread Updates not working, it has been searching for updates for hours and see if Dalai's workaround helps. Most Vista users should find that their "Checking for updates..." hang drops from several hours to under 30 min.

 

EDIT:

 

I should also note that Microsoft released a patch in June 2016 for the Win 7 Windows Update Agent (WUA) that appears to be a permanent fix for Win 7.  The Win 7 June 2016 update rollup KB3161608 includes hotfix KB3161647 (Windows Update Client for Windows 7 and Windows Server 2008 R2: June 2016) that adds "An optimization that addresses long scan time for updates". According to Woody Leonhard's blog entry Microsoft releases KB 3161647, KB 3161608 to fix slow  Windows 7 update scans, "there's no analogous patch for Vista customers." :(

------------
32-bit Vista Home Premium SP2 * Firefox v47.0.1 * NIS v22.7.0.76 * MBAM Premium v2.2.1

HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS


Edited by lmacri, 19 July 2016 - 11:55 AM.


#5 Willy22

Willy22

  • Members
  • 945 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Planet Earth
  • Local time:03:42 PM

Posted 19 July 2016 - 09:45 AM

- You''re not the only one who is asking this question.

- SYSNATIVE thinks that a file called "Win32k.sys" is causing the problems in Win 7. But I don''t know if this applies to Vista.

https://www.sysnative.com/forums/windows-update/20476-guide-windows-7-very-slow-scan-times-when-checking-updates.html



#6 lmacri

lmacri

  • Members
  • 407 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Canada
  • Local time:09:42 AM

Posted 19 July 2016 - 11:36 AM

- You''re not the only one who is asking this question.

- SYSNATIVE thinks that a file called "Win32k.sys" is causing the problems in Win 7. But I don''t know if this applies to Vista.

https://www.sysnative.com/forums/windows-update/20476-guide-windows-7-very-slow-scan-times-when-checking-updates.html

 

Hi Willy22:

 

The general consensus is that the problem Windows Update component is the Windows Update Agent (wuaueng.dll).  The workaround posted on Dalia's webpage at http://wu.krelay.de/en/ to pre-install monthly Windows kernel-mode driver (Win32K.sys) updates only "tricks" the Windows Update Agent into searching for updates faster.

 

Like the OP uberbleeper, I ran all the usual diagnostic tests [e.g., chkdsk /r, sfc /scannow, System Update Readiness Tool (MS CheckSUR), etc.] and even had a malware removal specialist in the Malwarebytes Malware Removal Help forum check my system for a malware or PUP infection (FRST, ESET Online, AdwCleaner, JRT, RKill, etc.), and none of these diagnostics found a problem with my 32-bit Vista computer.  I wasted even more time answering "cut and paste" questions from a Microsoft MVP who was convinced that this is not a Microsoft problem - see my thread August 2015 Windows Update for Vista Requires One Hour to Run to Completion in the Microsoft Answers forum.  Even that Microsoft MVP eventually came around to the conclusion that Dalai's workaround is a viable (but temporary) workaround for this problem.

 

As I noted in post # 2, the Windows Update Agent (WUA) at C:\Windows\system32\wuaueng.dll for Vista is currently v7.6.7600.256 and hasn't been updated since June 2012.  Microsoft is clearly aware of this problem but I would be pleasantly surprised if they provide a permanent fix by patching the WUA for Vista before extended support ends on 11-Apr-2017.

------------
32-bit Vista Home Premium SP2 * Firefox v47.0.1 * NIS v22.7.0.76 * MBAM Premium v2.2.1

HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS


Edited by lmacri, 19 July 2016 - 12:16 PM.


#7 uberbleeper

uberbleeper
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:42 AM

Posted 19 July 2016 - 08:51 PM

Thanks gals & guys.  While that info is helpful (maybe more for others starting troubleshooting this), my case has a twist.

Time to update is one issue, but my laptop is finding them - just not displaying them to install.  This is different than what most people are describing & complaining of.

 

And I could have a corrupt file / reg entry, etc., as well as any MS's update server tricks or a Vista broken update "Agent".

 

One recent update check on the dual core laptop, the windowsupdate.log & event viewer showed 32 updates found.

It never reported them in the control panel > update UI.  And didn't remember them on next reboot, the way it has.

 

 It looks like it never finishes or finds anything, because the progress bar never stops & no updates displayed.  So after a day or so, I turn it off. 

It HAS been detecting them - just not displaying them.  (a wink is as good as a nod to a blind horse)

I actually found Windowsupdate.log & Event Viewer both detected updates several times, since the last time any were shown in the Control Panel, then installed (on 4/6/2016).

Some obviously repeats from the time before - never got installed.   Here are some of the dates:

 

### Windowsupdate.log shows updates detected on several days (below), since the last date (4/06/2016) any were  shown in Control panel & actually installed.  Since then, NONE that windowsupdate.log & Event Viewer report "detected" have shown up in control panel.

After the last date that 32 updates were detected (6/26/2016), is when all the repair work on Windows Update related files & folders was done, multiple MS fixit tools run & Windows Update Agent reinstalled (not sure if successful, but no errors AFAIK).

2016-04-19    16:18:18:434    1588    98c    Report    REPORT EVENT: {A0573763-A280-45F2-A4AB-4774817A45FB}    2016-04-19 16:18:05:455-0500    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 14 update

2016-04-23    12:49:01:574    1588    138c    Report    REPORT EVENT: {B876298A-98A8-48C2-9896-90FE4A735EEC}    2016-04-23 12:47:59:486-0500    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 16 updates.

2016-05-20    10:49:23:258    1532    f10    Report    REPORT EVENT: {B7D1C873-2EBB-4B8F-9247-1DF3558FAA70}    2016-05-20 10:48:55:133-0500    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 27 updates.

2016-06-26    13:32:23:645    1636    14ec    AU      # 32 updates detected
2016-06-26    13:32:23:692    1636    10b8    Report    REPORT EVENT: {3E032448-87EB-4E5D-A38D-D83D12A9707D}    2016-06-25 22:54:54:904-0500    1    148    101    {00000000-0000-0000-0000-000000000000}    0    8024a005    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x8024a005.
2016-06-26    13:32:24:253    1636    10b8    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
2016-06-26    13:32:24:253    1636    10b8    Report    WER Report sent: 7.6.7600.256 0x8024a005 00000000-0000-0000-0000-000000000000 Scan 101 Unmanaged
2016-06-26    13:32:24:253    1636    10b8    Report    CWERReporter finishing event handling. (00000000)
2016-06-26    13:32:24:253    1636    10b8    Report    REPORT EVENT: {6C369333-5D06-47E0-AAB8-06935FC457CA}    2016-06-26 13:32:06:656-0500    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 32 updates.

 

I don't know exactly what the err 0x8024a005 on 2016-06026 is.  Very little on the web & no helpful description on MS list of errors.

Attached is part of the Windowsupdate.log - showing various errors & comments after it detected updates.  None of which may mean much. 

 

There seem to be some of the errors before  probs started (after 4/6/2016), just not as many errs as recently.  I've looked them up (many, many... pages, articles, posts).  All said to do what I've already done.

 

The only few  things I didn't do yet were:

1) - Run the MicrosoftEasyFix50202.msi tool in aggressive mode (GRrrrrr);

2) - didn't do step 4b @ https://support.microsoft.com/en-us/kb/971058 - below
 

4. b. Reset the BITS service and the Windows Update service to the default security descriptor. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.

sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

 

 

3) ??I'm not sure if it matters if the path is at C:\ , or C:\Windows\System 32 - before running those commands?

 

4) Didn't try reinstalling Win Update Agent in Safe Mode or clean boot.  Not positive if I stopped wuauserv, BITS before reinstalling it.  I figured the installer would if needed, but some say to do it.

 

5) I'm also considering BU, then delete the 8? windows update DLL files in System 32, then reinstalling the Update Agent.  If any are corrupted & went undetected, the Update Agent installer will be forced to reinstall them.

Attached Files



#8 lmacri

lmacri

  • Members
  • 407 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Canada
  • Local time:09:42 AM

Posted 19 July 2016 - 10:04 PM

Thanks gals & guys.  While that info is helpful (maybe more for others starting troubleshooting this), my case has a twist.

Time to update is one issue, but my laptop is finding them - just not displaying them to install.  This is different than what most people are describing & complaining of.

 

... I don't know exactly what the err 0x8024a005 on 2016-06026 is.  Very little on the web & no helpful description on MS list of errors.

 

Hi uberbleeper:

 

The "Checking for updates..." hangs are the most common symptom but some users have reported problems such as "Downloading updates..." getting stuck a 0%, or downloaded updates that never install correctly and keep getting re-offered on subsequent Windows Updates.  See msvista2001's thread vista stuck on "checking for updates" in the MS Answers forum, who reported seeing a Windows Update error 0x8024402C every time they ran the MS FixIT Tool.

 

I'd still suggest that you go ahead and try the step-by-step instructions posted 16-Jun-2016 in m#l's thread Updates not working, it has been searching for updates for hours.  All five of the Windows kernel-mode driver (Win32K.sys) updates listed on Dalai's webpage at http://wu.krelay.de/en/ are important (recommended) security updates for Vista that would normally be installed by an automatic Windows Update so there's little risk if you install them manually by following those instructions.  If installing your missing Win32K.sys updates doesn't help, or you just aren't convinced that this is an appropriate approach to solving your problem, then you'll have to wait for someone else with expertise in interpreting Windows Updates logs to jump in and lend a hand.

------------
32-bit Vista Home Premium SP2 * Firefox v47.0.1 * NIS v22.7.0.76 * MBAM Premium v2.2.1

HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS


Edited by lmacri, 19 July 2016 - 10:09 PM.


#9 uberbleeper

uberbleeper
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:42 AM

Posted 20 July 2016 - 03:05 PM

Thanks.  I may be forced to resort to installing kernel updates 1st, but there's a distinct difference in my case.  I don't have most of the errors listed in that article. 

My main problem is Vista on the laptop not displaying updates once it finds them.  It's possible some  installed update agent DLL files are corrupt, but obviously weren't replaced when I 1st ran the installer.  Or bad settings, corrupted / misssing reg data.  At least I can compare the 2 computers.

 

I have some of the same errors in my desktop's windowsupdate.log as on my laptop.  They seem to self resolve - because it finishes reporting then installing them.  Sometimes the logs show updates are detected w/in seconds after several Warning or Error msgs (in both computers, per the logs).

Both my computers updated normally on 4/6/2016.

Both would've probably had the same available updates - incl. kernel mode updates & same ones were installed, as I choose. 

 

After the 4/6/2016 update, only the laptop fails to display detected updates in control panel "select updates" screen.(on multiple days, per logs).  Once, the log reported "user declined installing updates at shutdown."  Never saw it.

 

While my desktop continues to normally detect, d/l & display all available updates for installing.  The laptop is detecting the same KB updates, just not displaying them in Control Panel UI.

 

AFAIK, this is different from complaints in most all articles - maybe 200 I've scanned.  On the entire web, I found a couple people said their logs showed updates detected as normal, but the select updates to install screen was blank.

The only solution I saw mentioned for this was more fix it or readiness tools, run SFC, reinstalling update agent (maybe in safe mode, if possible); resetting WU components / re-register DLLs, reset a few other things.  :deadhorse:

 

I'm guessing something went hay wire on the laptop, somewhere.


Edited by uberbleeper, 20 July 2016 - 03:18 PM.


#10 uberbleeper

uberbleeper
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:42 AM

Posted 25 July 2016 - 02:00 PM

Thanks Imacri & others for replies.

Well, I made a bunch of change & even found missing reg entries in my laptop (that won't update) vs. desktop that has no problem.  I recreated them.

But none of it make any difference, so far.

 

Anyway, for now I can't spend more time trying to fix this problem in VISTA.  Win 7 at least has a new Update Agent version, which seems to solve only some users' problem.

Same w/ various other "fixes."  Some say some step or method solved the problem, but more say doing everything they could find didn't help. Seems odd - if some Vista / W7 users can solve the "High CPU / Long Updates" problem, why not most?  Assuming they can read & follow directions?

 

So, I D/L'd the core updates from wu.krelay.de/en/.

I believe one of Imacri's posts ? mentioned installing them one by one, from oldest to newest, rebooting after each?  Is that currently the recommended best practice?

If it really doesn't matter, for Vista - are there  some tested scripts floating around to batch install them?

Krelay's site gives instructions to use command line: 

start /wait "" "%SystemRoot%\system32\wusa.exe" "C:\full\path\to\Update.msu" /quiet /norestart

Which works.  Only ran (the oldest) one so far, using that.  Removed "/quiet" to see if errors or directions displayed.  It finished & asked to reboot.

Doing it manually -by  D/L'g files listed in Krelay - NOT rebooting after each  may not be the best idea.  But, Update Agent or WSUS offline generally only reboot once, after all are installed?

Why the difference - needing to reboot after each, using method suggested on Krelay site?

 

I don't have a ton from krelay's site, but > 5.  I've seen posts in the past - in general - on batch installing D/L'd updates.  Many scripts offered, but I'm not sure that's best.

For one thing,  MS Update Agent, probably detects which ones need installing 1st, 2nd....  Though I've never had the updater install a few, ask me to reboot, then install a few more.

 

Many people complain it's their laptop w/ this problem.  Maybe just as many older desktops but users didn't mention the type / age of PC.

Thought occurred many of these would be wireless - if that affects the situation?  I read one post, where a guy couldn't get updates on his home connection (assume it worked for all else).  Said he connected to his neighbor's unprotected connection & then had no problems completing automatic updates??  He concluded it was "his connection."  Not enough speed or ISP throttling D/L's (at times) or traffic to / from MS servers.

 



#11 lmacri

lmacri

  • Members
  • 407 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Canada
  • Local time:09:42 AM

Posted 25 July 2016 - 04:02 PM

Hi uberbleeper:

 

Did you have difficulties following the step-by-step instructions posted 16-Jun-2016 in m#l's thread Updates not working, it has been searching for updates for hours in the MS Answers forum?

 

If you had followed those instructions by the saving the standalone update packages (.msu files) to your desktop and double-clicking to run, the installation wizard for the Windows Update Standalone Installer (C:\Windows\System32\wusu.exe) would automatically prompt you to restart your computer at the end of each installation to complete the configuration changes in your Windows registry.

 

Those instructions also recommend that you install any missing Windows kernel-mode driver (Win32K.sys) updates listed at http://wu.krelay.de/en/ in chronological order (i.e., from lowest to highest KB number) to ensure that Win32K.sys (and other files bundled in those .msu installers) are updated in incremental steps [e.g., from v6.0.6002.19462 (KB3078601) to v6.0.6002.19664 (KB3168965)].

 

You would only need to install a maximum of 5 of the Windows kernel-mode driver (Win32K.sys) updates listed on Dalai's webpage at http://wu.krelay.de/en/ this month if you have a Vista computer.  The current list for July 2016 is KB3078601 (rel. 18-Aug-2015), KB3109094 (rel. 07-Dec-2015), KB3145739 (rel. 12-Apr-2016), KB3164033 (rel. 14-Jun-2016), and KB3168965 (rel. 12-Jul-2016).  Depending on the last time you managed to successfully run Windows Update, only one or two of those updates might have been missing from your system.

 

I've never tried installing these .msu installers from an elevated command prompt, using the WSUS Offline Update tool, or installing these Win32K.sys updates out of order so I can't offer any other helpful advice since you've chosen to follow a different methodology than what I've recommended.  Hopefully the manual tweaks you made to your Windows registry haven't already corrupted your OS.

------------
32-bit Vista Home Premium SP2 * Firefox v47.0.1 * NIS v22.7.0.76 * MBAM Premium v2.2.1

HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS


Edited by lmacri, 25 July 2016 - 04:05 PM.


#12 uberbleeper

uberbleeper
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:42 AM

Posted 25 July 2016 - 06:21 PM

I appreciate that.  You didn't say if there's an opinion about the need to reboot after installing each manually downloaded update, when. Windows automatic update may install 20 - 30 updates & only reboot once?

I got 'em installed.  I'll be quite surprised & pleased if it actually stops the high CPU & long scan times.

 

Appeared to me - most of the time it's not scanning anything.  Some computer engineering types claimed they monitored what the active files (like wuaueng.dll) were doing while no network activity & nothing being written to log files - for hours.  I believe they said the files were in a loop most of the time - making millions or billions of calls to another couple of files.  No actual activity between MS servers & the computer for hrs.  That's pretty much what I saw.  Just overheating the CPU & mobo.

 

Maybe MS or the NSA is using our machines for their botnet.  They download problems or iterations to run - using our equipment, then send the results back - if we let it complete.  Then they allow the downloads.  :ph34r:

 

So far, I haven't created problems by editing the registry for nearly 20 yrs.  But I always back it up.  I never change anything that I don't have expert instruction or can plainly see a problem.

There've been several times when the factory uninstaller, or even the developer's supplied "complete uninstall tools" failed to remove enough, so their own driver upgrades will install correctly.

 

Not even following devs' or resident gurus' ridiculously detailed lists of pre-installation steps to insure successful installs.

 

Every time install problems persisted after following all recommended methods - then some (safe mode, clean boot, dangerous mode; delete this & that - didn't matter) there were still a few registry keys - buried deeply, or files no one ever mentioned.  Once I found & removed them, they installed perfectly w/ no hesitation.

 

Quite possible the problem of 1000's of users  having updating problems that may wear out their fans, CPUs, mobos - is due to MS changing something they shouldn't.  Or not deleting something they should've.  Or other MS changes totally jacked the auto update process & they're not willing to do anything about it.  If they're having to give free Win 10 upgrades to everyone, that doesn't look good.

Hardware & software mfgs often aren't willing to issue patches or driver updates when a new OS comes out.  Sometimes when the hardware / software isn't very old.  They sell more products that way.  It's a good system.



#13 uberbleeper

uberbleeper
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:08:42 AM

Posted 13 August 2016 - 01:14 AM

Update:  The workaround mentioned at

 

I did use the proposed "solution" (not fix) of D/L the kernel-mode driver updates listed at http://wu.krelay.de/en/ .  After installing the updates (from the list) I was missing, it changed updating time on my dual core laptop, from never finishing to finding ~ 30 updates in 15 min. total.  I selected 20- something patches & it finished D/L'g in ~ 15 min or less.  In August, installing the one available Kernel-mode update 1st reduced update scanning time to 28 min. 

 

Wish I'd found the original post on this workaround - 1st out of 100 searches I did on multiple engines.  If it came up in my searches, I never noticed it.  If you try this, find out which of the patches listed (by month) at http://wu.krelay.de/en/ - likely based on your last successful update time.

 

Some obvious questions about why this method works. 

Imacri wrote:

 

The workaround posted on Dalia's webpage at http://wu.krelay.de/en/ to pre-install monthly Windows kernel-mode driver (Win32K.sys) updates only "tricks" the Windows Update Agent into searching for updates faster.

 

And that's what the Krelay.de site mentions.  That this method works for so many is the important part.  I don't know why it works, but  I'm pretty sure it has nothing to do w/ there being 1 or 2 less patches out of 30+ available for updater to find last month.

Think about it - why would reducing the number of patches it must detect by 1 make any real difference in scan time?

1st, I thought about something being broken that the Windows kernel-mode driver (Win32K.sys) updates fixed, allowing update to complete more normally.

 

But many have said (& I saw) the same problem happen the next month.  Possibly implying, if patching Windows kernel-mode drivers was the fix in the previous month, something causes the same problem,  every month.  Not likely.

Perhaps there's an intentional / unintentional bug in Microsoft's update servers, where on your computer 1st connecting, if they don't see the latest Win32K.sys patch(es) installed, it causes massive delay.

Could be literally any reason - intentional  or not.  And after Snowden, all bets are off as to what COULD be intentional or possible.   But wuaueng.dll constantly using => 50% of CPU for hours (or a day) on dual core machines is a real bug that  MS knows about - being this widespread. 

 

I've read knowledgeable people that dug into the issue of wuaueng.dll (& the whole update process).  One technical post (can't find) said they actually checked what wuaueng.dll & maybe other update components were doing during long periods of no network activity.  The processes were stuck in loop(s), making millions of requests (explaining high CPU).  I don't remember reading any guesses what eventually ended the loop (for some users) &  finish updating.  Maybe when MS servers get good & ready to allow transmitting data?

https://www.askwoody.com/2016/the-windows-update-takes-forever-problem/comment-page-2/

 

I don't know if it's intentional by MS - as many have said.  But it's odd they don't care.  Maybe they decided to try & prevent another XP situation, where people hung onto old OSes (bad for bottom line).

 

Today, after installing the one new Windows kernel-mode driver patch for Aug 2016 for Vista x86, rebooted & then checked updates, I saw something new from past months.  Before WindowsUpdate.log showed any found updates, TrustedInstaller.exe (installs the updates) was the process using high CPU - for a long time, NOT wuaueng.dll.  Before any updates were found.  I checked WindowsUpdate.log multiple times. 

 

The service for it (Windows Modules Installer) was set to Manual start.   When it finally detected updates & I installed, TrustedInstaller was still using quite high CPU the whole time.  And continued to use ~ 50+% CPU for ~20 min after reboot & configuring updates were long over.   Adding insult to injury.  Eventually, it went to stopped status on its own.

But for hours of checking updates  in Vista 64 bit, TrustedInstaller hasn't been called & is still stopped.

 

This update debacle isn't the only reason -  just one of the final straws, why I plan on switching to Linux before Vista's support ends.  It may not be perfect, but at least 1000's of skilled users can look inside & find  a problem.  Even write patches, if a Linux distro team won't / can't.  Windows is just too insecure / too desirable a target.  It's anything but "set it & forget it."  I'm also not interested in moving any farther into Big Brother Bill's Orwellian world.

 



#14 JohnC_21

JohnC_21

  • Members
  • 22,587 posts
  • ONLINE
  •  
  • Gender:Male
  • Local time:10:42 AM

Posted 13 August 2016 - 08:14 AM

Perhaps there's an intentional / unintentional bug in Microsoft's update servers, where on your computer 1st connecting, if they don't see the latest Win32K.sys patch(es) installed, it causes massive delay.

 

You hit the nail on the head with this one. No problems with updating Windows 8 or 10.

 

This update debacle isn't the only reason -  just one of the final straws, why I plan on switching to Linux before Vista's support ends. 

 

 

Wise choice. As you already know Vista support ends in April 2017. I have a dual boot computer running Ubuntu and XP. Never had a problem updating Ubuntu and malware is a non-issue.For people switching from Windows linux Mint is a good choice, the version of Mint depending on what your CPU and RAM specs are. That being said Ubuntu has been rock solid for me. 



#15 six-h

six-h

  • Members
  • 96 posts
  • OFFLINE
  •  
  • Local time:02:42 PM

Posted 05 September 2016 - 12:46 PM

I don't give a monkey's Why wuauserv causes high CPU use, I just want to be able to update my PC, it just searches endlessly for some sign of updates and never finds them!

I am only permitted to use less than 50% of my own CPU, and am also deprived of almost half of my RAM, periodic visits to "Services" to "Stop" wuauserv have become part of the inevitable performance in order to use my own machine! Grrr!

That said, it is a risk to me and the wider world, ...but what do Microsoft Almighty care?

:cowboy: 's






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users