The Patch Manager Task History would not record any information with regard to the WSUS Server downloading updates from Microsoft, that I'm aware of.
Can you screencap what you're seeing in Task History and post it here. Perhaps if I see it it will trigger something that I'm not remembering mentally.
This is a CLIENT-SIDE error. It's saying that the WUAgent cannot download the file for that update from the WSUS Server because it does not exist on the WSUS server -or- the access permissions on the content store are incorrect.
Now that we know that it is the client that's recording the HTTP 404 error, we also know a couple of other factoids. We know that the WSUS server did successfully download the file for this update at some point. If it had not, the client would have never been able to see this update as available and attempt to download the file. So the question is: Which is the culprit.. permissions or a missing file.
First step is to inspect the filesystem on the WSUS server and determine the actual state of the file for KB2705619 related to Windows 7 x64 systems.
Concurrent with that, run the FREE Diagnostic Tool for the WSUS Agent and verify whether the content store is legitimately accessible.
If the file is physically missing, then run the utility wsusutil reset from %ProgramFiles%\Update Services\Tools, which will reconcile the content store with the list of approved updates, and re-queue downloads for any missing files.
If the file is not missing, then we're back to the accessibility of the content store.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.