Solved Continuous search for updates.

[Grego86]

I have a emachines 250-1162 notebook with Windows 7 Starter that I'm reviving with a new hard drive. I've reinstalled Windows 7 and a few small updates then SP1. Now I can't get the computer to find anymore updates. It never finishes is what I mean. For hours it will just keep searching and searching. I have ran the sfc /scannow command with no flaws, Microsoft fix it just keeps looping never finishes running and SURT just keeps searching for updates as well. I've double checked and made sure I had the correct time and date set. I've had experience in the past that caused computer to not update. Another thing to add dunno if its any coincidence but I always have to start the Windows Time service. Its even set to start automatically but never does and after I start it I can't sync time with any of the server addresses.

 

[UsernameIssues]

Set the laptop not to sleep.
Manually start the search for updates.
Leave the laptop alone for 24 hours.

 

[Jacee]

I have a emachines 250-1162 notebook with Windows 7 Starter that I'm reviving with a new hard drive.

You're going to have get your key/license 'validated' by MS because of the new hard drive. Hopefully you still have the original key number!

 

[Grego86]

I do have Microsoft validated. I let SURT run over night and it found a hotfix KB947821 but was unable to install it. I'm going to try booting in safe mode and see if it will work then.

 

[UsernameIssues]

Then it is time to post the files requested here...
http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html
...and hope that NoelDP can sort the problem.

 

[Grego86]

I've got it fixed. I had to download the .Net framework repair tool and that solved my issues. Thanks everyone for the help.

 

[UsernameIssues]

Thanks for sharing the solution. It sure seems odd that .NET needed repairing on a fresh install.

 

[NoelDP]

It wouldn't/couldn't, unless a .NET update got screwed along the way - if the original .NET 3.5 install was broken, there's be many other symptoms.

 

[waTeim]

Whoa, 3.5 you say? In the current environment, 3.5 is never installed, WU goes immediately for .Net 4 after installing SP1. Is that a possible problem?

 

[NoelDP]

.NET 3.5 is part of Windows 7, and always installed by default (which is why you get updates for it)
Windows Update should be offering .NET 4.5.2 by now as an update - which is a separate beast.

 

[waTeim]

But the thing is, that's not what happens. Old windows 7 pro (.Net 2.0) -> SP1 via update -> .Net 4.0 updates. Neither .Net 3.5 nor .Net 4.5 mentioned --> windows update searches forever.

 

[UsernameIssues]

How long have you left it searching for updates?

 

[waTeim]

Hmm probably the longest time I've had the patience for is about 10 hours, and I know what you're going to say, and no, I will not be leaving it on for 24 hours.... too much heat, unless someone can at least conjecture why that would be necessary.

After all why does it require such a long time? That's long enough to analyze the entire OS multiple times unless it's spending most of the time doing nothing but busy-wait the CPU to death. Admittedly it kind of looks like that's what it's doing.

if there were only a way to apply all relevant updates manually and avoid windows update entirely.

 

[UsernameIssues]

I'm not sure why some people have to wait so long lately.

If you figure it out, you could make lots of people happy

Some people think that some of the update servers are just too busy in some locations. I could not confirm that theory using Wireshark to see the traffic... because the Virtual Machine that I was testing with got its list of 200+ updates within 20 minutes.

 

[waTeim]

I don't think it's slow windows servers because the vast amount of time is spent without network IO, but when there is network IO (especially when using update WU .256 instead of .320) it's at > 25 Mbits/sec.

 

[UsernameIssues]

I have a few W7pro64bit VMs. I only keep one fully patched. The rest only have SP1 installed. These VMs return to their frozen (not patched) state when I exit them. A few months ago, I started seeing threads about long Windows Update scan times after a fresh build. I tested the scan time within one of my VMs, but gave up after 4 hours due to the heat being generated by the laptop (which I was also using at the time). Since then, I have seen some long scan times, but not in the last few weeks. Since the VMs are frozen, the change in scan times has to be external.

I have seen people (with tin foil hats) theorize that the busy servers randomly tell Windows 7 clients to scan everything again and again. Let's hope that they were joking.

 

[waTeim]

This similar to the setup i have except translated in time. There are (KVM) VMs installed from a Windows 7 Pro DVD, (not SP1), however SP1 can be applied in a straightforward way via either WU or ISO, but as soon as .NET 4 updates are applied and any windows update version .320 or later cause this problem.

 

[waTeim]

The final solution for me (I've also updated the original thread), was in fact let it run -- 15 hours in my case just to detect all of the updates, about 30 more minutes to download, and as I type this, it has installed 38 of 211 (10 minutes).

 

[waTeim]

As I've noted in the related threads. This is the solution to the problem.

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