Installed Failed Client download via WSUS Server

Hi,

If you are encountering issues with Windows Update on your clients and receiving error code 0x80d02002, there are several steps you can take to troubleshoot and resolve the problem. Here are some suggestions:

1. Check Disk Space:

• Verify that there is enough free disk space on both the WSUS server and the client machines. Insufficient disk space can cause update installation failures.

2. Reset Windows Update Components:

• Since you mentioned you've already tried resetting Windows Update Components, make sure you followed the correct steps. You can use the following commands in an elevated Command Prompt:

bashCopy code
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

3. Review WindowsUpdate.log:

• Examine the WindowsUpdate.log on the affected client machine for more detailed error messages. This log can be found in the C:\Windows directory.

4. Review Event Viewer:

• Check the Event Viewer on both the WSUS server and the client machines for any relevant error messages related to Windows Update or the installation process.

5. Consider Using Windows Update Troubleshooter:

• Run the built-in Windows Update Troubleshooter on the affected client machines. This tool can often identify and fix common update-related issues.

Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

Have you run a wsusutil reset on the WSUS Server to re-confirm that all files are downloaded properly to the WSUS server and not corrupted? - There is no progress bar or way to tell if wsusutil is still working, so once you start it, leave it for 24 hours before testing.

Then of course, while you likely did something similar, try running the client side script

https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/

It does more than what the above script that XinGuo posted.