Unable to install security updates via WSUS on Windows 2008 client servers

Question

When I try install to install updates on Windows 2008 client servers I get the error : Code 80244019  Windows Update encountered an unknown error
After running the WSUS Client Diagnostic Tool I get the result : GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002 The system cannot find the file specified.
On a Windows 2003 server the WSUS Client Diagnostic Tool shows no error message. So I guess the problem seems to be specificly related to Windows 2008 servers.
The client server has been integrated into a WSUS console version 3.2.7600.226 runnning on a Windows 2003 Enterprise Edition SP2.
Thanks in advance for the help in resolving this issue.

Answer 1

When I try install to install updates on Windows 2008 client servers I get the error : Code 80244019  Windows Update encountered an unknown error
The 0x80244019 error is an HTTP 404 error and when encountered trying to "install updates", which really occurs when trying to
download the update files so that the updates can be installed, is almost always a function of the desired file having been manually deleted from the WSUS server. The file that should be there for the needed update, isn't, but it used to be.
If all of the clients are getting this error on all updates, then that's a function of the content store on the WSUS server being missing, in the wrong place, or configured with the wrong ACLs.
After running the WSUS Client Diagnostic Tool I get the result : GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002
This result is inconclusive, and not really relevant. The CDT is 32-bit only and can't be used on 64-bit systems. Plus, we already know the client is talking to the WSUS server -- you've reported the error code -- so the Client Diagnostic Tool will
tell us nothing of use at this point (even if it did work on 64-bit systems).
On a Windows 2003 server the WSUS Client Diagnostic Tool shows no error message.
Cool. It works on a 32-bit system.
So I guess the problem seems to be specificly related to Windows 2008 servers.
No... BUT... allow me to make an example of this for just a moment, and forgive me for that.
This is a great example of arriving at the wrong conclusion, caused by not considering ALL of the differences, as well as the scope and capability of the diagnostics performed. The error is not because one is '2003' and the other '2008; the error is because
one is 'x86' and the other is (obviously) 'x64'. And, in either case, diagnosing the client was wasted effort because the client is already working. (It got a real HTTP error message from the WSUS server.)
Now, we need to get some real diagnostic information to find out why you're getting this error code. :-)
Please post the actual entries from the WindowsUpdate.log where this error code appears, plus a hundred lines prior, and let's get some context around the error code, and the exact update that's involved in this issue.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.