Skip to main content

Resolving the Stuck on Checking for Updates issue in Windows 7

Lately I've been finding Windows Updates under Windows 7 to be a real pain.  One of the more common issue is where Windows gets stuck on checking for updates.  This can go on indefinitely.

The following steps often resolve the issue.  I say often because in some rare cases the issue can persist...

- Open an admin command prompt

- Enter "net stop wuauserv"

- Run KB3138612.msu

- Restart PC

- Open an admin command prompt

- Enter "net stop wuauserv"

- Run KB3102810.msu

- Enter "net stop wuauserv"

- Run KB3135445.msu

- Run WindowsUpdateDiagnostic.diagcab

- Run WindowsUpdateDiagnostic.diagcab again (must see everything fixed)

- Run Windows Update and check for updates

One last thing: always make sure you have the latest version of the Windows Update Client.

Comments

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

APC PowerChute Network Shutdown - Authentication Phrase

​Was installing  APC PowerChute Network Shutdown (PCNS) on a customer’s server and couldn’t find a record of the Authentication Passphrase that I set ages back on their Smart UPSes Network Management 2 Card. So I went to reset it on the card and start anew… it took a lot of digging to find it on their particular release of firmware: Go into the UPS tab, then into “shutdown” inside the “Configuration” category: You may then need to change the passphrase being used on other servers. To do this, open up PCNS in your browser and click into the area shown below:

McAfee does my head in

I’ve said it before and I’ll say it again: to all intents and purposes installing McAfee Anti-virus software is pretty much as bad as getting a virus.  There, I said it.  Again. I’ve lost count of how many problems I’ve had with customer PCs over the years where the root of the problem was McAfee in one or another of its hideous incarnations.  But here’s one that’s fresh in my head because I’ve only just sorted it out… A customer had a PC that wouldn’t connect to the iTunes Store in iTunes.  He could do everything else with iTunes, just not connect to the store.  Actually, now I think of it he probably wouldn’t have been able to use the internet radio stations in iTunes either.  He could access the internet and send/receive emails just fine.  iTunes just refused to play ball.  When I ran the Diagnostics in iTunes I got an error –3221. Well what could cause this?  Probably a firewall I thought.  The customer had McAfee Security Center with VirusScan and Personal Firewall.  They also