Don;
If anything security may be enhanced slightly with a public DNS's ability to transcribe common errors in typed URLs and by minimizing cache poisoning.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Don;
If anything security may be enhanced slightly with a public DNS's ability to transcribe common errors in typed URLs and by minimizing cache poisoning.
Does this affect security at all?
Thanks,
Don
I tried the suggestion to change the DNS servers to 8.8.8.8 & 8.8.4.4 and it fixed the issue.
If you are not technically inclined, (myself included) ..call your ISP and have them change the DNS in your router for you from the office. It takes seconds and resolves the issue beautifully!
... 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.
I don't follow your logic there. One or more updates could have caused some machines' DNS settings to point in the wrong direction, who knows? I think the answer is still somewhere in Microsoft's realm. The fact that it's effecting so diverse a number of ISP's lays the blame squarely at Microsoft's doorstep I would say. It's still their updates that are causing havoc.
Change your DNS servers to 8.8.8.8 and 8.8.4.4 and it will fix the problem. A reboot may be needed.
I must say the support here is totally useless. Microsoft knows this issue and knows the temporary fix as well.
This did the trick!
Thank you so very much. You have saved what was left of my sanity!