Solved Fresh Install Win7SP1 Update just hangs tried everything...

[SurferX]

Hi, I found this forum after spending the last two days trying to get windows update to work on a fresh install.

Originally I wanted to put Win7 SP1 64bit on a VM (KVM). Everthing installs fine, windows update hangs looking for updates, even if I wait 24hours, leaving svchost running at 100% cpu on a core.

I tried many things including Window Update Trouble Shooter (KB971058), System Readiness Tool KB947821, VM settings, permissions, DNS settings... Until I gave up.

So I thought I would try a different tack, I have now installed Windows SP1 on Spare HD on the laptop directly i.e. no VM. I have NOT activated Windows as do not wish to keep this installation, i.e. once I have resolved the problem I want to use the VM, at that point I will activate it.

So I have now done a fresh install, I have windows update set to automatic, but with Important updates selected only (not recommended updates), done several reboots. Windows updated to Windows Update Agent 7.6.7600.320 (the only update), I have set my DNS to 8.8.8.8 and 8.8.4.4 just in case my ISP was the cause of some problem.

I left the machine overnight, Windows Update still hangs...

I ran SURT, SFC Scan (showed no errors) I have posted the logs if anyone can figure this out?

I did notice these in the CBS file
2015-09-10 10:34:47, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

I also notice these errors:
Failed to get session package state for package: Package_1_for_KB2656356~31bf3856ad364e35~amd64~~6.1.1.1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

 

[Apache312]

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.

 

[SurferX]

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.

 

[cmthomson]

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.

 

[Andyrids]

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.

 

[UsernameIssues]

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).

 

[NoelDP]

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

 

[SurferX]

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.

 

[SurferX]

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.

 

[SurferX]

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...

 

[NoelDP]

MS have been having throttling problems on the servers since Windows 8 was released.
It may be impacting on the updates servers you're using

 

[SurferX]

MS have been having throttling problems on the servers since Windows 8 was released.
It may be impacting on the updates servers you're using

Update

The Windows Update finaly returned after 20+ hours of checking, on my VM install of Windows 7. I wonder if I am having some network issues on my own end, which have componded the already very extended times it is taking to run Windows Update From a fresh install. Though I can't be sure, of that as the network seems fine pretty much all the time I want to use it(I am at home) I will post the logs tommorow, if someone is able to identify anything usefull, that mind help others who are following this thread.

 

[SurferX]

Unfortunately the WindowsUpdate log rolled over, so I can't post that.

I thought I would sumarise my findings:

1. Windows Activation is not necessary
2. KB3083324 or kb3065987 was NOT necessary though it might make some difference if you have and old machine with less than 2GB, the SVCHOST needed at least 1.2GB
3. I had installed Microsoft Security Essentials (which had the effect of making the option for
Microsoft updates available and checked) this DID affect the memory footprint of the svchost process.
4. I have perfectly serviceable broadband, but I have noticed occasionally poor response times, this may compound any problems on the MS servers on the other end.

Bare metal Machine took 7hours
VM took 20+ hours


Hope that helps others

 

[NoelDP]

Thanks for the data!

 

[Layback Bear]

Just for information.

What I have done that works for me.
When your system is in the download stage and not working, restart the computer and start the download again. I think what this does is shift the download search to another M/S server that isn't as busy.
DO NOT do this if your system is in the Install Updates stage.

Some times I also have to use this method to get MSE Updates downloaded.

I have no proof the above is true. It just works for me.

 

[cmthomson]

"Manually Install KB3083324"
This worked for me. Start with a generic Win7 SP1 DVD (ten bucks on *bay), install this update before running Windows Update, then be patient (several hours) while the 200+ current updates download and install.

 

[robebcan]

I have exactly the same problem. I did a clean install of Win7 x64 Premium on a brand new SSD. I selected "Check for Updates" and it would be running until Christmas if I let it. The same thing happens if I look for "Installed Updates" on the computer. Interestingly, I downloaded the Microsoft Update Readiness Tool, and that took FOREVER to download and on trying to install it, it hangs up on the "searching for updates on this computer".
My internet access is working just fine. I just now loaded MSE and tried checking for updates again. Hang up. I tried switching Auto updates to Never, reboot, and then Auto then check for updates. Hang up again.

Any ideas ?

 

[waTeim]

Yep, I had this problem last year and again the past couple of days. Installing the following is the fix. I additionally updated to IE11 prior to the linked-to update but it's (IE 11) probably not necessary. I can confirm that following the install of this patch, the "searching for updates" behavior of windows update which previously took 100% of the CPU for 1 day and didn't accomplish anything, instead executed using 9% of the CPU for 15 minutes and returned a list of 228 updates.

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