Win 7 Windows Update 80246002 Unable to run updates

... Microsoft knows this issue and knows the temporary fix as well.

• If changing your DNS to Google's public DNS (8.8.8.8 / 8.8.4.4) resolves the problem then GREAT! However, at that point you can stop blaming Microsoft or Windows Updates for your trouble because the problem comes solely from your own ISP (Internet Service Provider) that is supplying the original DNS service. Microsoft has nothing to do with your ISP's DNS service's shortcomings.

That appears to be incorrect. Many people have now said that only certain machines on their network have this problem. For example, all the machines on my network use the same router and DNS settings from the router. Two didn't work. Adjusting the local DNS on those machines allowed the update check to work properly. The problem is definitely local to each of those machines and not with the ISP.

What is everyone's ISP in this thread suffering from this issue?  I wonder if there's some ISP commonality going on?

Unfortunately, that doesn't seem to be the case, which makes this "solution" beyond baffling.

It's good that people are adding backup DNS though (better not to rely on just one, even if it's Google), since DNS outages can and do happen. Charter Communications had a rather massive one about a week ago. Those who had backup DNS weren't affected.

Making the DNS changes worked for me, but if I change them back then the problem still exists.

My ISP is Mornington Communications.

I have not yet tried to change the DNS number on my Windows 7 Desktop PC.   I am using Verizon FIOS as my Internet Service Provider.

I guess JEEPED is saying the PROBLEM IS my Internet Service Provider.  ??? 

In other words, what ever is causing the 80246002 error code is not MS's fault?

I will wait until tomorrow to attempt to change the DNS number on my Desk Top PC. 

I am glad at least two folks have provided 'work a rounds' for what ever is causing the 'problem'.

Also, thanks to the person who requested the step-by-step instructions on HOW to change the DSN number.

... Microsoft knows this issue and knows the temporary fix as well.

Don't get me wrong but let's get our facts straight. I am not here defending Microsoft or Windows update as they both have made mistakes in the past. As a matter of fact, at least some of the problem with the current rash of 80246002 errors seems to have to do with an earlier update that is being reversed and overwritten with a subsequent one. However, if it quacks, waddles and looks like a duck then let's call it a duck and not a goose. 

• If changing your DNS to Google's public DNS (8.8.8.8 / 8.8.4.4) resolves the problem then GREAT! However, at that point you can stop blaming Microsoft or Windows Updates for your trouble because the problem comes solely from your own ISP (Internet Service Provider) that is supplying the original DNS service. Microsoft has nothing to do with your ISP's DNS service's shortcomings.
• In my personal experience, I have been using Google's public DNS service on a couple of machines for several months and even wrote a local Wiki article on the perils of relying on your ISP's greedy DNS service. Regardless, I experienced the 80246002 error this morning on a Windows 7 laptop using Google's public DNS and was subsequently able to resolve it.

I don't know for sure if these are two unrelated issues or if they have somehow become clouded together. If bashing Microsoft and Windows Update for your own ISP's lack of providing credible Internet services makes you feel better then I suppose that you should continue in that. I just want to set the record straight so others can achieve a proper perspective and receive full benefit from this thread.

If anyone needs instructions on how to change the default DNS server(s) on their computer or hardware router, they might find my local Wiki article of use.

Bing is Slow or Doesn't Load with Time-Warner