Windows 7 Checking For Updates stuck forever

Anonymous
2011-05-31T17:23:58+00:00

original title: Windows 7 Checking For Updates stuck forever - I know this is answered, but the solutions don't work for me. Please see details!

I have installed a legit Windows 7 OS on my laptop. Its not an upgrade, it was a blank hard drive. WIndows 7 installed flawlessly, picked up all my drivers. The only problem is I am having problems with Windows 7 updates. When I choose Windows 7 update, it says "Checking for updates" and stays like that - forever. Even the next day. I did heavy heavy research, found out others are having the same problem. I tried all the fixes I could find, which are listed below:

  1. No Anti-virus programs installed yet - brand new Windows 7 ultimate installation
  2. There is no spyware - its a brand new clean install
  3. Firewall shut off
  4. Temp files, cookies, history cleared
  5. background intelligent transfer service set to automatic in services.msc
  6. software distribution folder renamed
  7. tried shutting off automatic updates and doing it manually
  8. Added windowsupdate to trust zone
  9. ran MicrosoftFixit50202 in normal and advanced mode

Even with my internet SHUT OFF (turned off modem) it still checks for updates and doesn't fail with "No internet connection available".

Please, please help. Anyone.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2011-06-08T21:01:42+00:00

Problem solved.

It was my internet connection!! I logged onto my neighbors via wireless unsecured (ssh... don't tell lol), and within 30 seconds, 77 updates came through!

It has to be something in my network.

Thanks for helping though!!

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments

261 additional answers

Sort by: Oldest
  1. Anonymous
    2016-08-04T02:06:48+00:00

    Dave, you are correct.  I had a Windows 7 machine that I hadn't used in months and could not get updated to Windows 10 in time for the expiration.  The update process was stalled (corrupted?).  Anyway, turning off Windows update (set to never install updates), restarting the machine, downloading and manually installing KB3172605 (latest for July, 2016), restarting the machine, and turning  windows update back on allowed me to at least get the machine to resume updating Windows 7.  The key is turning off windows updates while you manually install KB172605 as nothing works right when "Trustedinstaller.exe" is cranking in an endless and futile manner in the background.  Now that it is updating normally again, I'll just stick (or am stuck) with Windows 7 on this machine.  What a chore!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-08-05T22:57:37+00:00

    It's not that your computer is running slow or anything, it's just that there are too many updates and the PC is trying to install all the ones that are required for your PC to have all of its power with it! I've done this multiple times and it always works. If you installed a brand new copy of Windows 7 OS, go to Windows update and leave it there for 10-13 hours, since it's a brand new copy, it has to find a total of 200-300 updates if it's brand new! Once you see that it's  found the update so download them And it shouldn't take longer than 1-3 hours. Once the updates are done, your PC is up and running and all the drivers and updates should let your PC reach its maximum power! Hope this helped!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-08-05T23:09:07+00:00

    The June 2016 Update Client, included in KB3172605, is designed to address this issue.

    Regards, VZ

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-08-05T23:49:44+00:00

    "included in KB3172605, is designed to address this issue".....

    ...as I have discovered.  Thanks VZ and Dave for your help.

    Was this answer helpful?

    0 comments No comments