This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
As suggested by Microsoft, the failed security update MS14-045 requires actions to be take. You recommend manual uninstall of KB 2982791. This I did. The system reboots. I then went to try and use Windows Update so that it finds and installs the replacement, KB 2993651.
Windows Update is now corrupted. It issues error code 80246002. All attempts to run the Troubleshooter to fix it, says it is unable to automatically resolved the problem. It has entries with a red X in the list. When you ask for the detailed report, though, it shows no problems against any of the entries.
now; the first time I ran it, it showed an Error 1 accessing Windows\SoftwareDistribution, access denied.
It's unconscionable that MS should generate even more severe errors when trying to back out from an existing error from a failed update. And simply deleting one KB, now renders the entire Windows Update process unusable.
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.
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.
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.
Thank you for the info on how to change DNS servers. Have done it and it works! That's all that matters. Not all of us are technically minded. Just a step by step instruction and it worked. All things are working as they are supposed to.
