Windows Update Hangs

Just a thought VZ, should I install these KB now..my updates went in..will these help future months?

I am not learned enough to understand all th KB things nor did I know to do so..I did search for answers and there was no easy to understand.."having issues with July 2016 updates..installKB. Etc.  ". That I could find or I am just too apprehensive to keep installing things..so I went the patience route ..but your suggestion I am sure will help others...is there a forum that will help me decide to upgrade from W7 that I love to W10?

But it works..see my other post..set it and let it run one right or for the day..they will go in..not happy either but patience works...maybe time to upgrade to w10

KB3102810 is outdated. The new 3102810 is KB3161647, included in KB3172605.

KB3172605 32-bit

KB3172605 64-bit

Make sure to have its prerequisite, KB3020369, installed.

Regards, VZ

Mr. Canadian Tech,

your answers are completely preposterous. You are not seriously suggesting this, are you? Do you realize what a billion machines, computing *nothing* for 12 hours every month, amount to? Will you do the math of wasted energy, or should I do that for you as well? This whole matter is ripe for some environmental organisation's attention.

As I'm writing this, of course I'm looking at Windows Update going nowhere and burning CPU.

And Microsoft should truly be ashamed of themselves for this. There is no reason *whatsoever* for the check to take longer than a second, so much it would take today's CPU power and internet connections to download a list of updates and compare it with a local state. That is, if implemented *properly*. Being a software developer, and looking at this fiasko, I feel ashamed. Why doesn't Microsoft?

It's been this way a long time, too. Versions of Windows Update, crunching something for hours, getting nothing done. This is no lone case. Internet is filled with these reports. And yet, most people simply don't notice the CPU burn because most of them don't have usage indicators visible at all times. I, for example, do (in tray area).

If the service has to wait for something, then I would expect you don't do it in a hot loop when you know well that this waiting often takes 12 hours!

If it actually takes this much to compute the task, then the whole update system must be so misdesigned that I wouldn't believe such a programmer getting work at Microsoft. But I do have some distant memory that in certain instances (rare), Windows Update actually checked the state fast.

Of course, when checking is done fast, "downloading" then moves nowhere for hours, burning CPU just the same. This is the last clue, as 'downloading' certanly has 0 reason to burn CPU. But it does, nevertheless.

I searched on the question sites and found this question. The accepted answer suggested this:

https://support.microsoft.com/en-us/kb/3102810

Of course, when I tried installing it, it said it's already installed. Windows Update seems to constantly return to this 'bugged' state, even though it was already fixed. Or maybe someone *wants* us to be frustrated with Windows 7. Can you guess why? *Cough* 10 *cough*...

Of course, the chance of getting an explanation from Microsoft on what exactly is this thing computing for hours, is next to 0. My best guess would be that it's utilizing client computers as a computing cloud for Microsoft. Maybe Azure really runs on our machines, eh?

Joke aside, Microsoft, would you *please* fix this already?