I noticed when doing a manual Windows Updates using Control Panel it finds the updates fast enough but after selecting updates I want to install and asking to install them takes forever to Download updates and no progress indicated, but if I click the start icon after some time it shows the updates are ready to install if I Shut Down the PC, indicated by the yellow Bang. No indication of what updates are ready to install either.
If I let the Windows update run on downloading, it will eventually download and install the selected updates but still no progress indicated, but takes hours. I see this behavior on some (4) my W7 PC's (7).
Its like the Windows Update screen does not refresh.
Any insight to this behavior or how to solve it?
Fully updated Windows 7 64bit prior to this months (Aug 2016) patch Tuesday.
Note: Home network, Fios with no other issues. Its wide spread on several computers and does it on any of them when I travel with those devices also, it is a windows update gui issue. Happens on Normal month to month updates.
This has nothing to do with "checking" for updates as answered in this question I answered this question myself but this is an entirely different issue and have found no solution so far.
Note:
This issue does not happen anymore since MS started rolling out servicing stack updates. for Windows Update issues after a Clean install of W7 see my post over here>>>>>Windows 7 SP1 Windows Update stuck checking for updates
Best Answer
Dice Roll. . .
I like all the methods listed here on this MS KB as potential solutions to this problem. In particular Method 10 thru Method 13 stick out to me the most that sound like solutions I've used in the past to resolve correlated problems even if not exactly the same.
I'll only quote the methods below I would not skip for sure if I were troubleshooting this issue but I wouldn't limit myself to just these or just this KB for that matter but these may be good starting points for potential solutions.
I also agree that seeing any applicable detail from the
%windir%\WindowsUpdate.log
would be helpful in troubleshooting this issue.Lastly, I'd start troubleshooting and working this problem from one of the machines and ensure it's connected to a rather speedy Internet connection so in other words if you're traveling and connected to public network or a mobile wifi, just wait to ensure those factors don't play a role in the issue just in case.