'Checking For Updates' runs forever on new install

I have a new install of win 7 32bit SP1 and installed the system drivers and when I update it installed the latest version of Windows Update Agent, I set updates (before checking) to NOTIFY ME BEFORE DOWNLOAD AND INSTALL - so I know from my experience of hundreds of installs that it should take minutes to tell me whats available THEN i can download them....THEN i can install them... but it goes into a loop,,,constantly saying its checking for updates, this soaks up my 2Gb RAM and 50% CPU constantly

so i hve tried the microsoft troubleshooter fixit here: https://support.microsoft.com/en-gb/kb/971058

it says its fixed something but cuold not fix issues with installing updates?

i have a 50Mbps LAN connection

heeelpp
thanks

Try installing this update:

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

It's drastically reduced the time to pick up all the updates in all the VM's I've tried. It should pick them up within 10 - 20 minutes.

ive tried loads of things...even reinstalled and reinstalled a different version of win7 sp1 as a test and same result, one person said it worked when he connected to a neighbours network, this is virgin 50Mb on older hub (not new AC hub) - I done a fresh install in May and on Virgin too and it took MINUTES to find what i needed installing

i will give it a bash...been on for 2 days with this now and its annoying the hell out of me, also this version ive got is slipstreamed until June 2015 so should take less than a minute>?

thanks

Many people are reporting slow time for Windows Updates, especially for a clean install.
Kick off WU and let it run overnight and see if that helps.
From what i've read it could take 24 hrs. or more, but it eventually works.

well i got a slipstreamed version that had all updates installed until Jun2015 and left it running from 1am and in the morning it had 55 updates to install

Which version of C:/Windows/system32/wuaueng.dll are you running?
(Right click on file, then Properties, then Details)

This thread is now "Solved".

Maybe snadge finally got the issue fixed, and didn't post back with how it was fixed/solved ?

Oops Sorry David!

Magnet said:

Oops Sorry David!

No apology needed, i just noticed the thread is marked solved.
Only the OP (snadge) or an SF administrator can set a thread to Solved.

SF administrators do not set a thread to solved from what i know, the OP would do that.

So i assume @snadge "Solved" this thread/problem, without explaining how.