Win 7 Windows Update 80246002 Unable to run updates

Actually, I think the portion of my reply that you quoted may be taken out of context without the second bullet point in the original reply's content. I would have to see the update history on either or both of the problem machines in order to make a judgement call on that. As noted in my second bullet point, the only machine that I had trouble with this morning was one that was already set to 8.8.8.8 / 8.8.4.4 and I found that by first installing the optional update by itself, the problem with installing the important update was subsequently resolved.

TBH, I feel that if you have corrected the error the point is moot. I do sincerely appreciate you following up with your own experience as I don't believe that any one solution offered thus far is a one-size-fits-all solution. What seems to work for one computer's configuration does not necessarily work for another but I feel that the community's contributions are collectively helping others in similar situations.

I just wanted to let you know that I was using OpenDNS when I first started getting the 80264002 error, and I had tried switching back to my ISP DNS (Charter) to resolve the problem but that did not work either.

Thank you Krisjan! I changed the DNS servers to what you said and it is working fine. Thanks again!!

For some reason the 2 computers that I am having the issue with are not responding to the DNS change which is very disappointing. However I am able to update my Microsoft Security Essentials manually so it just proves that the updates that are most important are still possible to get. In the mean time I have declared to just try to be patient and understand that once again Microsoft wants to be a pain in the butt and attempt to sucker people into paying as much as possible in order to fix an era they have made but would like to claim is much more than what it really is. Hopefully by the middle of next week this issue will be fixed!

... 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.