New
#31
Your situation and resolution attempts are not unlike the variety of things I had tried (over and over...). I thought I would share details on what the one additional consideration was that resolved in entirety for me. I have not read about this specifically anywhere within these forums or others elsewhere.
I was trying to install KB3102810 which had been identified as potential resolution to the high CPU problems with svchost.exe and wuauserv service being used by Windows Update. Attempted to install but similar to problem with the Windows Update process in use, it just showed a "searching for updates..." popup and then hung.
It did not occur to me until umpteen hours and various other fix attempts later, that maybe there had been a conflict !! Further investigation revealed that even after a fresh system restart, CPU use was high and Windows Update was already active in background when looking at Resource Monitor. I went into Windows Update - Change Settings and changed it to NEVER automatically update and then rebooted...and confirmed that process was NOT active. I reattempted the install of KB3102810 and it resulted in an entirely different set of installation prompts this time around. After it finished and requested a reboot, I tried Windows Update again. CPU use was lower as promised and after a short anxiety filled minute or two, it reported back with 217 updates available for downloading !!
Hope this helps...I feel that everyone's individual settings in Windows Update probably explains some of the inconsistency re success rates where some people had conflicts with active processes and others did not ! Anyhow, happy to have it behind me now : )
I'm having the same problem, managed to download Update for Windows (KB3083324). Checking for any other updates as I type this and its still just taking forever.
Any advice?
Found this thread searching for a resolution to my windows update just searching for updates forever. I found the solution to the problem and the reason why so many people are having issue is because microsoft changed the name of windows update agent to windows update client, so all of the microsoft support articles reference a old WU as being the most up to date.
Here is the latest installer as of June 2016, that worked for me. It found the updates after about 15-20 minutes of searching and then allowed me to update my fresh install.
Latest Windows Update Client - Windows Update Agent
Hope that helps anyone who ran into the same issues as me.