Fresh Install Win7SP1 Update just hangs tried everything...

I have had the same issue as in the last 2 days as well. Ive never had this before, but found your post by researching the same issue. It happens after I update to SP1, from a clean Win7Pro x32 install, using a M$ OEM disk. Have tried too many things to list, but there is something mystical about this issue. Just letting you know that you are not alone.

yep totally confused by this!

In order to try and solve this, I have a bare metal install on old machine, (Non activated) I have also done a fresh install on a VM and activated it. The problem occurs after the Windows Update Agent 7.6.7600.320 is installed from then on update just hangs, so no updates ever get applied or a response from windows update from that point on. Seems I am not the only one!

Hopefully someone will have some time to checkout the log files I posted.

Similar situation here. Bare metal retail Win7x32 install on a recently bought laptop. All is well until just after the SP1 update, when Windows Update says I need Update V7.6.7600.320. After that, svchost goes cpu-bound and 1 gig, and "checking for updates" never ends (at least it hasn't after a full day).
I installed KB3050265, but no change.

On a few systems with the same problem I found that if you leave it for roughly an hour until the CPU and HDD thrashing slows down and then do a restart you should find that WU has updated itself in some cases without informing you and after that it if you run it again it is still quite slow but it does tend to fetch the update list eventually... I found this to happen on 4 different systems recently. I cant guarantee this will work but it has for the laptops I have repairing.

SurferX said:

Windows updated to Windows Update Agent 7.6.7600.320 (the only update),

Manually Install KB3083324

Windows Update Client for Windows 7 and Windows Server 2008 R2: September 2015

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


If you start from scratch, you can install KB3083324 instead of 7.6.7600.320 (May 2014).

They say a watched pot never boils...

Ok I left the two machine alone overnight, 11hours... It seems the bare metal (non activated) install has come back saying I have 147 updates available. I have not yet selected them, as I am amazed after spending the last few days on this.

I am posting the logs, but reviewing them, it seems that I rebooted the machine around midnight and started the update process and it seems like the results came back nearly seven hours later... BTW on this machine the only think I have installed is security essentials not other hotfixes since 7.6.7600.320.

Could some one take a look at the logs to see if there is clue why it takes so long? The Install on the VM which I have activated and is the one I WANT TO KEEP, is still hanging after 11 hours I will post those logs in a moment.

NoelDP said:

There are no actual errors in the logs I've seen - the one you quote is classed as 'Info' and is a normal part of an update install.

Try this - Windows Update error 8024000B - Windows Help

I tried this BTW on Win 7 Pro 64bit at least the file that this KB refers to doesn't seem to exist.

Little update,

The main reason I went and did a bare metal install, was to see if the VM was the cause of the windows update problems.

So far the baremetal machine has got past the point where it now gives a list of updates to download, they are currently downloading... So maybe there is a difference.

The VM install is identical (except it is activated) so far it still hangs looking for updates, one thing I noticed that I did different, and seems to have made a difference is I installed MSE and did a reboot before I started the the update process off, the memory footpring of svchost process that runs when doing the update has increased to ~1.2G instead of less the <.5gigs and also the option for
Microsoft updates is now available and checked. So I have now installed MSE on the VM and rebooted and started the updated process again, maybe success in 12hours...