Windows 10: Windows 7 SP1 Windows Update stuck checking for updates

Ok, it shows 242 important updates now!

Should I now change to download and install automatically, also a the services, should it be without "delayed"?

Ok, so I returned the settings to automatically, it's downloading now, we'll see if it all gets installed successfully...

 

Two of the important updates are unselected for donwload, .NET Framework and this one:


Should I leave it that way?

 

You got lucky, from what I've seen. I did a clean install of 7 sp1 just to test how Windows update worked, or didn't work. After several reboots and retries, I left mine running on check for updates for 3 days and nada. It would not update, just a continuous checking for updates. It's a known wide spread problem that in most cases requires manual intervention to resolve.

 

Yes, I had a similar experience doing an OEM factory reset to Win7 SP1 on my laptop.

The key to getting it to check for updates in a prompt fashion was to install KB3125574 (the Convenience Rollup) and then do a Disk Clean-up and tick the Windows Update Clean-up. This last point is important as it removes all obsolete updates (this in itself speeds up the check-for-updates process - there's less to check).

On my machine before installing KB3125574 SYSTEMINFO reported: 267 Hotfix(s) Installed.
After KB3125574 it was: 268 Hotfix(s) Installed.
After Windows Update Clean-up it was: 122 Hotfix(s) Installed.

NB: Windows Update Clean-up requires a restart to complete the process. First it says 'Windows is configuring updates' and then there's a time consuming 'Cleaning up...' screen before the restart is complete.

For me that reduced 'checking for updates' from 'hours' down to 1 minute 20 seconds.

 

Windows update will do that if those updates need to be installed separately from the rest. Let it do all the others, reboot, and run Windows update again. Odds are this time they will be checked for install the second time around.

 

Now I think one of the updates is causing a problem... I got a Nvlddmkm.sys bluescreen a few minutes ago. This is the same error I had before reinstalling... But hey, at least I have all the latest updates! *Smile

 

You could try can uninstalling one or both to see if your BSOD goes away. Then set them to hide in Windows update so they don't install again.

 

I have not yet tried any of this on a fresh install, but MANY threads at sevenforums.com and at other fora seem to confirm that these 3 patches will get WU up and running, so that all of the many other, important patches can be installed in minutes, rather than hours or days:

3125574 (convenience roll-up)
3020369
3172605

Each computer is unique and -- as of a few months ago -- other individual patches (such as 3138612, 3145739 and 3102810) had been mentioned. However, several of those have been superseded, and -- at least for me and many others -- they did not fix the WU issue.

On an existing Win7 install (not a new one), I think 3125574 can be skipped. 3020369 and 3172605 ought to be sufficient.

YMMV, of course...

HTH,

MM

 

No, 3125574 is a convenience roll-up for Win7 SP1 systems, it's not SP1.*Wink

MM

 

In services.msc (the "console), Windows Update should be reset to "Automatic (delayed start)".

In the Windows Update applet, it's up to you, but many advanced users prefer to have some control over their updates.
So, they configure Windows Update ONLY for IMPORTANT updates and the setting is set to "notify, but let me choose...".

Other users, who may be less "hands-on" can configure Windows Update for automatic installation or for automatic download. It's your choice.

As a general rule of thumb when there are a LOT of patches to install, it's best not to try to get them all installed in one batch.
Starting with IMPORTANT patches only (not RECOMMENDED and not OPTIONAL), one would generally install them in bunches, in this sequence:

• Security patches for Windows
• Security patches for Office, Silverlight, and other MS programs
• Important non-security patches for Windows, Office and other programs
• .NET Framework patches last

If some of the available patches in your list are not "ticked" by default, it could mean that you first need to install one or more prerequisite patches. Anything that is not "ticked" by default is likely NOT the highest priority. You can come back to those later.

It's best NOT to use the computer for other things while you are installing updates and to have infinite patience...
Sometimes, it can take a while. But it's best not to interrupt the process. And it's VERY VERY important not to turn off the computer or its power while it's updating....

TBH, if you install 3125574, it might shorten the process for you, as it includes many of the individual updates in one "rollup".

Continue the process, rebooting when prompted, until a manual update check says that there are no more available updates...

HTH,

MM

 

ONe or both what??

 

Those last two updates you mentioned as being installed separately. If your lucky it was one of those that caused the BSOD.

 

I have not seen ANY trouble reports with 3020369 or 3172605 at sevenforums or other places.
I seriously doubt either of those is the issue.

On a refurbished machine, to some extent, all bets are off.
But BSOD is usually the result of hardware issues, driver conflicts or (in some cases, rarely) a rootkit.

I would look elsewhere for the cause of the BSOD. For example, I would be sure that the system has all the current device drivers....
In "Device Manager", for example, do any of the installed devices have a Yellow Triangle on them?

OK, aside from the fact that this entire thread probably belongs at sevenforums.com, not here at tenforums, this is morphing into something far more complicated than the usual "how do I get Win 7 to update" problem. *Sad

So, I'll defer to others more facile, especially when it comes to BSOD.*Smile
Troubleshooting that issue will take the discussion down a different pathway, using appropriate tools such as WhoCrashed or BlueScreenView, etc.....

Cheers!
MM

 

I never claimed that the above mentioned updates are the cause of the problem, however, others might be. I don't know.

 

It was just a hunch, a guess, that one of those updates may have caused it. Since, they were the last ones installed, they would be fairly easy to uninstall again as a test, that's all.