Following a clean install, Windows Update remains at "Checking For Updates" forever...

Anonymous

I've reloaded hundreds of Windows computers over the years and I like to think that I am reasonably proficient at that process. I have just encountered an issue that required a lot of time and effort to resolve and I am posting this to try and save someone else the same ordeal.

My customer had a late model, name-brand Windows 7/64 SP1 computer with a disk drive that was failing. I changed out the disk drive with a replacement and went through the recovery process, using the manufacturer-provided Recovery Media. That media is supposed to be identical to the image loaded on the drive from the factory - Windows 7/64 with SP1.

Following the reload, I followed my normal procedure and launched Windows Update. Windows Update remained at "Checking for Updates" for hours, without ever displaying any updates to install. I restarted the PC and tried again, with exactly the same result. The Software Distribution folder would get built and there were plenty of entries in WindowsUpdate.log, but eventually disk activity would cease but CPU activity would remain over 50%. And Windows Update just showed "Checking for Updates" forever.

I decided the reload must have been bad and so I repeated it from scratch again with exactly the same result. At that point I decided the image on the manufacturer's Recovery Media must be defective and so I reloaded from my MS Partner Program Windows 7/64 SP1 DVD. I had the same exact symptoms and result again. I thought that maybe I was not waiting long enough, so I left it running overnight. The next morning, it was still at "Checking for Updates".

I tried additional reloads using SURT and that also remained at "Checking for Updates" without accomplishing anything. I tried using the Windows Update Troubleshooter - with no luck. Ditto for manually resetting Windows Update and various combinations of these techniques. I verified that Windows was activated and that date/time were correctly set. Nothing made any difference.

I then started meticulously documenting everything as I went along and I think I've found a solution:

After the reload, I checked the Windows Update components in C:\Windows\System32. The components are wuapi.dll, wuapp.exe, wuaclt.exe and wuaeng.dll and all are version 7.5.7601.17514 dated 11/20/2010. Once you launched Windows update or run SURT, these are all updated directly to version 7.6.7600.320. At that point, I get the symptoms described above and there doesn't appear to be any way to recover.

When Windows Update is launched, it first updates itself automatically and without the user having any option. It appears that upgrading the WU components from7.5.7601.17514 directly to 7.6.7600.320 causes the issue. I suspect that it works fine for computers that are updated incrementally.

Once WU version 7.6.7600.320 is loaded, there is no easy recovery that I could find.

CURRENT PROCEDURE:

Download https://support.microsoft.com/en-us/kb/3020369 and https://support.microsoft.com/en-us/kb/3172605 in advance.
Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.
Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.
When the installation prompts for updates, choose "Ask Me Later".
Apply KB3020369 and then KB3172605 in that order.
Restore the Internet connection, configure update settings to your preference and launch Windows Update as normal.

Credit to Canadian Tech, Volume Z and other contributors for developing this current procedure.

ORIGINAL PROCEDURE FROM JANUARY 19 2016 HAS BEEN DEPRECATED BY THE NEW PROCEDURE ABOVE:

Download KB3083710 and KB3102810 in advance.
Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.
Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.
Manually install KB3083710 and restart - WU components will now be version 7.6.7601.19016 dated 9/25/2015.
Manually install KB3102810 and restart - WU components will now be version 7.6.7601.19046 dated 10/20/2015.
Restore the Internet connection and launch Windows Update as normal.
After a few minutes, you should have plenty of updates to download and install.

Ken Morley

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

580 answers

Anonymous

2016-11-14T17:59:11+00:00

Interesting that you mention Windows Defender. The one laptop that I tried out Windows 10 has spent many updates in the SCOD mode for hours on end. That is the Spinning Circle of Death and it often requires pulling the battery and waiting a minute to get the laptop back because your power down button no longer works. . My recent troubles I found it failed to do another of it's forced updates and even though I don't use Windows Defender it is caused by bad files in Windows Defender. I already use Malware and Norton Internet security and the drive is clean. Placing the drive in another computer and have it scanned as an idle drive still shows no troubles. At this point I found that Windows Defender can't be downloaded or fixed separately. It is a full part of the windows 10 software so it requires you back up everything and then download a new install of Windows 10 and it will clean your hard drive and you can only hope all your back up stuff works with a new reload of Windows 10. In other words it is another reason I tell everyone to not go to Windows 10.
Was this answer helpful?

0 comments No comments
Anonymous

2016-11-14T15:17:37+00:00

Hi @ Rajdeep218 ,

Nothing wrong with those updates, as I did install them and they did not hurt Windows 7 at all.
Was this answer helpful?

0 comments No comments
Anonymous

2016-11-14T15:14:59+00:00

Hi @ ShaneFletcher ,

I have Windows Update set to Check for Updates, but do not Download.

I installed those updates, with no adverse problems, whatsoever. That's why I did not understand your post. Besides, if you set it for Never check for Updates, you won't receive any Windows Defender Updates, if you use Windows Defender.

Also, if you use Norton or McAfee, those Anti-Virus programs, take up CPU Cycles themselves. Not sure about what the others do.
Was this answer helpful?

0 comments No comments
Anonymous

2016-11-14T14:25:48+00:00

Ken , Thanks so much for posting the solution to the Update stuck forever problem . I used it and all is again well in Update Land. Ray
Was this answer helpful?

0 comments No comments
Anonymous

2016-11-14T12:09:23+00:00

@thecreator

I was referring to Win10 itself not any actual Malware, as MS keeps trying to push/force the (spy machine) OS onto preferred Win7 users with their hidden updates that have nothing to do with security but merely forcing users to upgrade. These new updates have changed and we no longer have control on what we can/cant download hence why I was asking in my original post, this was due to me making a big mistake by allowing WU to run again instead of leaving it to 'NEVER' check for updates. ( As clearly mentioned by CT on 16th July 2016 in this discussion).

My machine was running perfectly until curiosity got the best of me and I started the WU, a critical update was installed onto my machine in the background whilst WU updated itself and by this time my machine's CPU and MEMORY usage had gone up up to 50% plus hence slowing my machine down, it has always been at around 13% or less. I haven't even installed the other three important updates yet because of this, as i don't want to further my problems and was seeking further advice from VZ on what to do.

I apologise for the misunderstanding as i probably should have worded my original post a bit better, i don't want Win 10 on any of my machines so just need to clarify if I should leave my other machines as they are and never check for updates again to keep Win10 at bay.

Thank you.
Was this answer helpful?

0 comments No comments