New Windows Update Agent 7.6.7600.320 causing error 80246002 during search for updates

Anonymous

I am using Windows 7 64-bit with Service Pack 1. Windows Update had been working very well until the Windows Update Agent was automatically updated to 7.6.7600.320 sometime in August 2014. Now when Windows Update attempts to search for updates, it reports that "Windows could not search for updates" and indicates that error code 80246002 was received.

[UPDATE] Since posting this query, I think that I have resolved my problem by following the instructions described on the page "System Update Readiness Tool for Windows 7 for x64 based Systems (KB947821) [May 2014]". I downloaded the file (Windows6.1-KB947821-v33-x64.msu) and then let it install itself. It describes itself as "Hotfix for Windows (KB947821)". The installation took a long time, with much disk activity. When it finally finished, I rebooted my machine, and attempted a Windows Update. It appeared to work properly; it even found an important update which I then installed successfully. So apparently for my problem the Hotfix for Windows (KB947821) provided the solution.

[UPDATE 2] After seeing the posts about changing the DNS to solve the problem, I thought I would add the following information in case it is relevant:

I am using the 64-bit version of Internet Explorer 11, and confirmed that it is operating in 64-bit mode by inspecting the browser's user agent. You can review your browser's user agent by visiting the site http://user-agent.me/
My Internet protocol properties are set to "Obtain DNS server address automatically". This works with my wireless router, and I have never been tempted to change it.

[UPDATE 3] After thinking that I was safe, having done multiple successful searches for updates, the 80246002 problem returned on my machine! I rebooted my wireless router and my machine but it did not help. So, I went ahead and tried the DNS trick: I changed the preferred DNS server to 8.8.8.8 and the alternate DNS server to 8.8.4.4, and then rebooted. Now Windows Update search is successful! I am humbled, and grateful!

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

Answer accepted by question author

Anonymous

I finally fixed the update problem with an Acer Aspire 5315 Laptop.

I installed KB2993651 for win 7 32 bit.

I then got update error 80244019

I then looked that up & installed KB 971058 -

it went to 100% CPU but less than 100% after 5 minutes.

It then was able to get updates.

It downloaded 187 updates to 100% completion.

It started installing 187 updates & got to 30 % then rebooted & was still going at 32% of updates when I left my friends place.

I phoned her & it seems ok.

I'll have to check next time I'm there that it's all done.

Moral of the story - don't give up - keep trying.

cheers

Bobby

0 comments

Answer accepted by question author

Anonymous

In my case I got the window update error code 80246002 after I uninstalled KB2982791 as per https://technet.microsoft.com/library/security/MS14-045 and then tried checking for updates. Nothing I did would clear the error (ipconfig /flushdns, renaming the SoftwareDistribution folder, a few MS Fix its, etc...). Since KB2993651 was the replacement update that I was trying to download and install, I decided to manually download the update from the windows update catalog (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB2993651). After downloading and installing KB2993651, I rebooted the PC and then I was able to check for Windows Updates again without getting the 80246002 error code.

0 comments

Answer accepted by question author

Anonymous

For anyone else who is experiencing issues updating a freshly installed windows 7, i'll share with you my fix. I RE-reformatted windows 7 after making sure to delete both partitions, giving this a clean slate(to eliminate other possible errors). Then begin updating as usual, just around 20(?) updates in is when update agent 7.6.7600.320 is supposed to download. Obviously...don't hit install/update. Download chrome and seek out KB3135445 ( https://www.microsoft.com/en-us/download/details.aspx?id=50797 ). Follow install directions, after it's done go back over to windows update and click check for updates. Give it anywhere from 5-10 minutes and it should say you have around 243 ish updates! Hope this helps.

0 comments

144 additional answers

Anonymous

2015-12-30T16:41:55+00:00

What works for me is to set to never check for updates, apply. Then I set for updates and it works.
Was this answer helpful?

0 comments No comments
Anonymous

2015-12-30T12:54:06+00:00
There are no many forums mentioning this topic, but no-one had come up with a solution that worked for me doing a re-install of Windows 7 on an old laptop. I have finally managed to get it up to date, so here is how I did it.
1. Essential! Set Windows Update to Never Check for Updates.
2. Used "Windows Update Downloader" to get the updates up to March 2015 (when the downloader support stopped) and installed the relevant ones using a script.
3. Got a list of all updates in 2015 from KB894199.
4. Downloaded and installed KB3112343, which appears to be the latest update to the Windows Update Client. This installs V7.6.7601.19077, but did not solve my problem as "Checking for Updates" still ran forever.
5. Downloaded all the Windows 7 security updates since March 2015 using the Microsoft Update Catalog and installed them using a script.
6. After all this, Windows Update "Check for Updates" ran in less than 30 minutes and found 35 important updates and lots of optional updates. This includes some Security Updates that I would have expected to be in the list from the Windows Update Downloader, so that list is not complete; may be the originator was finding it too time consuming to keep up to date.
7. Let Windows Update install the important updates, which it did successfully.
It looks so simple when you write it down, but it has taken me many hours over a couple of weeks to get to this stage. I suspect the Windows Update Client is written without regard to the amount of memory it requires, and that it is slowed down by continual memory cache activities. Somehow the amount of memory required must increase as the number of uninstalled updates increases, to the point where it runs for many hours on a poor little machine with only 2GB RAM. It may be that it is fit for purpose on a machine that has been kept up to date, but it seems to not be fit for purpose on a re-install.
Was this answer helpful?

0 comments No comments