Win 7 Windows Update 80246002 Unable to run updates

Anonymous
2014-08-27T22:00:30+00:00

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.

Windows for home | Previous Windows versions | Windows update

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

171 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-09-02T19:10:50+00:00

    Hi Susan,

    Thanks for responding. I just checked two of my machines and Win Update has started working again without making any DNS changes (ISP = COX residential, but not using their DNS as primary).  I'm waiting for a call-back from an OEM vendor to see if his updates are working again (COX business class).

    I have one Win 7 64-bit machine that has KB2982791 installed, but not KB2993651. Is it OK to install it without first uninstalling KB2982791?  I know MS "highly recommends" uninstalling, but I ran into some problems doing so on another machine (boot and IE problems which I was able to resolve). MS doesn't seem to state the ramifications of doing so. Any thoughts?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-02T18:45:49+00:00

    It's not a patch.  I have installed all updates released through August on every single computer under my control including some remote and in colos.  Not a single one is repro-ing this issue.  If it WAS a patch, I'd be able to repro this SOMEWHERE in all of my machines I control.  I can't repro this.

    And ... if it was patch related we'd be getting another patch.  There's no update being released.

    I follow updates and moderate the patchmanagement.org listserve.  I know patches.  This is not a patch related issue.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-02T18:39:34+00:00

    My thought is,

    its a bad, patch....If updating worked before the patch, and stopped after...its a bad patch.....

    The fact that Microsoft is fixing it today, IT's a bad patch.......

    Also I use Verizon FIOS and their DNS servers, so issue has affected more than just Time Warner users...

    Hopefully, Since Microsoft has issued soo many bad patches this year alone, that they can get their act together!!!!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-09-02T18:39:11+00:00

    I have listened to several support incidents since Friday and a DNS change has been successful for each one.

    I would like to identify folks who have tried to resolve the 0x80246002 using an alternate DNS setting and have failed.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-09-02T18:26:09+00:00

    It's not a bad patch.  Clearly when folks are able to get around this issue by changing DNS settings, this is not a patch issue.

    I'm wondering how much is this connected to Time Warner and possibly we are more interconnected on the Internet then we know. 

    As I said above *any* functional DNS servers that your ISP provides should work to get you to Microsoft update.  If every impacted poster here said they were using one specific ISP I could go AH HA there's the root cause and point to the ISP as the source of the problem.  But clearly we don't have one ISP at play here.

    Bottom line if it doesn't magically resolve itself (as mohieddineayes indicates above) - which in turn points to a ISP root cause - then move your DNS to an alternative provider such as Google DNS or OpenDNS.

    Again, and personally, I prefer OpenDNS due to the additional web filtering ability it provides.  I can also state that here at the office and at home where I've always pointed my dns to opendns' IP addresses, I've had zero failures of Microsoft update.

    So to answer your question, the Internet has gone bonkers is what I would say the root cause is.

    Was this answer helpful?

    0 comments