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.
Exactly the same issue. Microsoft, release a fix for this. A lot of people are having problems as I've asked around. Some of them have formatted and clean installed Windows 7, the first update is this broken update agent and from there on it's totally broken.
I have searched about this issue. The problem first manifested itself some time in June, some people just seem to have got this Update later. Enough negative feedback to really consider a fix I think.
Good morning, first poster, unfortunatelly never have an issue with windows, my hard drive died and I made a nice clean install of windows 7 home premium, yesterday at night I tried to run the windows update, started to get this error, I have followed every single solution presented in the Microsoft sites, tried a LOT of hotfix/I Fix it.
I download four updates that Windows update said that failed install, but when I try to manually install them system says they are already installed.
Don't make me format yet again my system, I have a slow internet connection and a full install means two lost days due to all the updates that I then need to re-download.
I am just adding this this thread, since Microsoft seems to have totally messed up wua .. current
Windows Update Agent 7.6.7600.320 is broken, this needs to be fixed now, lot of people are going to be hanging out in the wind on this one
of note, this is from a fresh install, only sp1 is installed on win7x64 .. this patches installed without permission on my end
windows update agent 7.6.7600.320
definition update for windows defender
update for windows kb958488
kb2685811
kb2505454
this is as far as the update process got after sp1 was installed, since I see wua767600.320 is not showing up in Microsoft search for this update...
this is the log entry that is causing the issue directly, not sure if there is anything upstream that is messing things up
-08-28 03:40:45:108 336 bb8 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab are not trusted: Error 0x80070002
2014-08-28 03:40:45:170 336 bb8 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80246002
2014-08-28 03:40:45:170 336 bb8 Setup FATAL: SelfUpdate check failed, err = 0x80246002
2014-08-28 03:40:45:170 336 bb8 Agent * WARNING: Skipping scan, self-update check returned 0x80246002
2014-08-28 03:40:45:170 336 bb8 Agent * WARNING: Exit code = 0x80246002
After deinstall KB2760601 (Sharepoint) here Windows Update works again
Bruce, we haven't even got as far as installing the latest update 651 yet. All I did was uninstall the original (flawed) update 791, AS STRONGLY RECOMMENDED by Microsoft themselves.
My suspicion is that it's something in backing out that old update, that is causing any subsequent action to fail. Whether it is run individually, or as part of the new update. Until MS can figure out what that is, we don't have a viable fix.
