Troubleshooting WSUS Client Reporting Issues: Not Yet Reported or Not Reported in Over 24 Hours

 If an endpoint is not reporting to WSUS or hasn’t updated its status in over 24 hours, follow these steps to diagnose and resolve the issue:

Step 0: Verify Prerequisites

Before troubleshooting, ensure the endpoint meets the prerequisites for WSUS. Use JetPatch Endpoint Readiness to analyze and pinpoint missing configurations.

Step 2: Check Group Policy and Registry Settings

For Domain-Joined Endpoints

1. Open Command Prompt as administrator.

2. Run:

   gpresult /h GPReport.html

3. Open GPReport.html and navigate to:

   Computer Configuration > Administrative Templates > Windows Components > Windows Update
   

4. Verify that the policy Specify intranet Microsoft update service location is set to:

   http://<WSUS_Server>:8530

5. Force a Group Policy Update (if necessary):

   gpupdate /force

For Non-Domain/Non-Policy Endpoints

1. Open Registry Editor (regedit) as administrator.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
   

3. Verify or update the values for:
   • WUServer
   • WUStatusServer
   • Ensure these match the WSUS server URL.

After either gp update or regex change, run the following powershell command as admin

$updateSession = new-object -com "Microsoft.Update.Session";$updates=$updateSession.CreateupdateSearcher().Search($criteria).Updates;

Step 3: Perform Basic Connectivity Tests

On the Endpoint

1. Test Network Connectivity:

Open PowerShell as administrator and run (8531 test only needed if using WSUS SSL):

Test-NetConnection -ComputerName <WSUS_Server_Hostname_or_IP> -Port 8530 

Test-NetConnection -ComputerName <WSUS_Server_Hostname_or_IP> -Port 8531

1. Test WSUS Access via Browser:

   • Open a browser and access:
     • http://<WSUS_Server_Hostname_or_IP>:8530
     • https://<WSUS_Server_Hostname_or_IP>:8531
   • If inaccessible, investigate server-side or network-related issues.

Step 4: Check Windows Update Service

1. Open services.msc on the endpoint.
2. Locate the Windows Update Service and ensure:
   • The service is running.
   • The Startup Type is set to Automatic.
3. If the service is not running, start it and recheck.

Step 5: Analyze Windows Update Logs

Manually Check for Updates

1. Open Settings on the endpoint.
2. Go to Update & Security > Windows Update.
3. Click Check for updates.
   • If an error occurs, consult Microsoft’s Troubleshooting Guide.

Generate and Review Windows Update Logs

1. Open PowerShell as administrator and run:

   Get-WindowsUpdateLog

2. Open the generated log (saved on the desktop) and look for error codes such as:

   • 0x80244010: Communication issues with WSUS server.
   • 0x80072EE2: Timeout or network issues.

   • Consult Microsoft’s Troubleshooting Guide.

Step 6: Reset Windows Update Agent Using JetPatch Scripts

1. Use JetPatch’s Reset WUA Authorization script (PowerShell or Batch) to reset the Windows Update Agent.
2. If needed, run the Advanced WUA RESET script to fully reset all Windows Update settings.

Monitor Endpoint After Reset

1. Use Endpoint Readiness to verify WSUS communication after the reset.
2. Focus on the WUA Communication column to confirm updates.

Step 7: Leverage JetPatch for Multi-Endpoint Checks

Run Built-In Tasks

1. Open Endpoints > Management in JetPatch.
2. Filter by the relevant Windows endpoint group(s).
3. Select all rows, then click Action > Run Task.
4. Search for Check for potential Windows Update Agent issues and run the task.
5. Review results under Endpoints > Activities