Issue Summary: WSUS Client Status Reporting Issue

Prabhuswamy S 0 Reputation points
2026-06-03T11:52:16.7566667+00:00

We are facing an issue with our WSUS environment.

Client systems are successfully detecting, downloading, and installing Windows updates from the WSUS server. However, in the WSUS console, several client computers are showing the following messages:

  • "This computer has not reported status yet"
  • "This computer has not reported status for XX days"

We have already performed the following troubleshooting steps:

  1. Reset the WSUS client ID.
  2. Deleted and re-added the client in the WSUS console.
  3. Ran GPUpdate and Windows Update detection/report commands.
  4. Restarted Windows Update services.
  5. Performed IIS reset on the WSUS server.
  6. Executed the WSUS Cleanup Wizard.
  7. Verified that the clients are receiving and installing updates successfully.
  8. Tested the same procedure on multiple client systems, but the issue persists.

Environment Details:

  • WSUS Server OS: [Windows Server Version]
  • Client OS: [Windows 10/11 Version]
  • WSUS Version: [Version]
  • Number of affected systems: [Count]

Kindly assist us in identifying the root cause and provide a resolution for the WSUS client status reporting issue.We are facing an issue with our WSUS environment.

Client systems are successfully detecting, downloading, and installing Windows updates from the WSUS server. However, in the WSUS console, several client computers are showing the following messages:

  • "This computer has not reported status yet"
  • "This computer has not reported status for XX days"

We have already performed the following troubleshooting steps:

  1. Reset the WSUS client ID.
  2. Deleted and re-added the client in the WSUS console.
  3. Ran GPUpdate and Windows Update detection/report commands.
  4. Restarted Windows Update services.
  5. Performed IIS reset on the WSUS server.
  6. Executed the WSUS Cleanup Wizard.
  7. Verified that the clients are receiving and installing updates successfully.
  8. Tested the same procedure on multiple client systems, but the issue persists.

Environment Details:

  • WSUS Server OS: [Windows Server Version]
  • Client OS: [Windows 10/11 Version]
  • WSUS Version: [Version]
  • Number of affected systems: [Count]

Kindly assist us in identifying the root cause and provide a resolution for the WSUS client status reporting issue.

Windows for business | Windows Server | User experience | Other
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. scan80269 0 Reputation points
    2026-08-22T19:37:17.0266667+00:00

    I have encountered this exact issue, ever since my WSUS server running Windows Server 2025 installed the July 2026 Cumulative update.

    The clients that persistently show "This computer has not reported status in XX or more days" within the WSUS console all have Intel 4th-7th generation Core CPUs. Clients that have Intel 8th-14th generation Core CPUs do not exhibit this issue, and their statuses are all properly updated within the WSUS console.

    Last month, I uninstalled the Windows Server 2025 July 2026 Cumulative update, and the status of all clients went back to normal. Thus I can confidently say that a change to Windows Server 2025 OS starting with the July 2026 Cumulative update directly correlates with clients based on Intel 4th-7th gen Core CPUs failing to update their status within the WSUS console.

    Please note that all clients have been able to download and install monthly updates properly from my WSUS server. The issue is only with client status not being updated as observed in the WSUS console.

    Summary:

    • Windows Server 2025 with June 2026 (or older) update: all client status normal (Intel 4th-14th gen Core CPUs)
    • Windows Server 2025 with July/Aug 2026 update: client status normal (Intel 8th-14th gen Core CPUs)
    • Windows Server 2025 with July/Aug 2026 update: client status NOT updated (Intel 4th-7th gen Core CPUs)

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Adam J. Marshall 11,031 Reputation points MVP
    2026-06-05T18:46:17.8733333+00:00

    I know you've run through a bunch of stuff... that some of them are on my blog linked below. I know people hate doing this, but PLEASE follow the steps in my blog post from top to bottom.

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

    DO NOT SKIP STEPS. 99.999% of the time, these steps fix the issues you are experiencing. Go from top to bottom.

    Was this answer helpful?

    0 comments
  3. HLBui 11,095 Reputation points Independent Advisor
    2026-06-04T09:59:48.92+00:00

    Hi Prabhuswamy S

    Everything looks fine on the client side, yet the console acts like those machines are ghosts. The good news is, this usually isn’t a broken WSUS setup but rather a reporting hiccup between the Windows Update Agent and the WSUS server. When clients install updates but don’t report status, it’s often due to stale reporting data or Device Guard/Defender policies interfering with the status submission.

    Here’s what you may check next:

    • Make sure the WSUS server’s IIS Application Pool (WSUSPool) isn’t recycling too aggressively set the idle timeout to 0 and memory limit to something reasonable.
    • Run wuauclt /reportnow or usoclient StartInteractiveScan on a few clients, then watch the WSUS logs for incoming reports.
    • Verify that port 8530/8531 traffic isn’t being filtered by any endpoint protection or proxy.
    • If you’re using Server 2022 or later, confirm that Enhanced Security for WSUS isn’t blocking anonymous metadata submissions.
    • Lastly, check the WSUS database for orphaned client entries sometimes a cleanup or reindex fixes the “not reported” issue.

    This behavior isn’t unusual in mixed Windows 10/11 environments, especially after cumulative updates. Once the reporting syncs up, those messages should clear automatically within a day or two

    Was this answer helpful?

    0 comments

  4. AI answer

    2026-06-03T11:52:41.9866667+00:00

    The described behavior indicates that WSUS clients can scan and install updates, but their status reports are not being correctly stored or surfaced in the WSUS database/console. Based on the provided information, focus should be on WSUS-side configuration, database health, and client reporting rather than basic client-side connectivity (which is already working).

    Proceed with the following checks and remediation steps:

    1. Verify WSUS configuration vs. Windows Update
    • Confirm that clients are actually configured to use WSUS for reporting, not just for scanning.
    • Check the registry on an affected client:
      • HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
      • Ensure UseWUServer is set to 1 so that the client uses WSUS and reports there.
    • If WSUS is misconfigured (for example, updates are not approved or policies are inconsistent), clients may scan and install but not show usable status in the console. The article on bad WSUS setups shows that incorrect WSUS configuration can cause scans to succeed but no actionable status to appear because nothing is approved or properly targeted.
    1. Confirm that updates are approved and targeted correctly
    • In WSUS, verify that updates for the affected clients’ OS versions are approved for the correct computer groups.
    • If the WSUS server is not approving updates or targeting them correctly, the console may show no status or stale status even though clients can scan.
    • The Windows Update troubleshooting guidance notes that when WSUS does not provide proper deployment criteria, the client will scan but not receive install/download instructions, and the console will not show expected status.
    1. Check for duplicate SUSClientID issues
    • Even though the SUSClientID reset was already performed, ensure that there are no remaining duplicate IDs in the environment.
    • The WSUS client agent troubleshooting guidance describes a scenario where only one of several clients appears in the console at a time due to duplicated SUSclientID values (for example, from imaging).
    • On a sample affected client:
      1. Stop the Windows Update service: sc stop wuauserv.
      2. Delete the SUSclientID registry value under:
        • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
      3. Start the Windows Update service: sc start wuauserv.
      4. Run wuauclt /resetauthorization /detectnow.
      5. Run wuauclt /reportnow.
    • Repeat on a few affected clients and then check whether they appear correctly and maintain status in the console.
    1. Check WSUS database event table size and health
    • If clients can reach WSUS but status is not updating, the WSUS database may be overloaded or blocked.
    • The WSUS event table tbEventInstance can grow beyond 1 million rows, causing timeouts and blocking client reporting. Symptoms include:
      • Clients failing to upload events with errors like WARNING: Failed to upload events to the server with hr = 80244008 in Windowsupdate.log.
      • SQL timeout errors in WSUS logs (SoftwareDistribution.log) referencing Timeout expired and ConnectionRead (WrapperRead()).
    • Check the size of tbEventInstance on the WSUS database (SUSDB):
      1. Connect to the WSUS SQL instance.
      2. Select the SUSDB database.
      3. Run: 
             select count(*) from tbEventInstance
      4. If using WMSDE or the built-in WSUS SQL instance, the same can be done with osql: 
             "%programfiles%\Update Services\tools\osql\osql.exe" -S %COMPUTERNAME%\WSUS -E -dSUSDB -Q"SELECT COUNT(*) FROM dbo.tbEventInstance"
    • If the count exceeds 1 million rows, automatic deletion of old events is slow and can block new status reports. In that case, reduce the table size (for example, by purging old events per Microsoft guidance) so that client reporting is no longer blocked.
    1. Differentiate WSUS vs. Windows Update issues
    • Since updates install successfully, the Windows Update engine on the clients is likely healthy.
    • To confirm that the issue is strictly WSUS-related:
      • Manually download and install a test update from the Microsoft Update Catalog on an affected client.
      • If manual installation succeeds, this aligns with guidance that the problem is likely WSUS configuration or communication, not the WU service itself.
    1. Validate scheduling and policy for reporting
    • Ensure Group Policy settings for Automatic Updates are configured so that clients regularly scan and report to WSUS.
    • WSUS uses approvals and deadlines plus Group Policy scan/install schedules to control when clients install and report. If policies are misconfigured or disabled, clients may not send regular status reports even though they can install updates when manually triggered.
    1. If the issue persists
    • Collect logs from affected clients (WindowsUpdate.log) and WSUS server logs (SoftwareDistribution.log) around the time clients are expected to report.
    • If SQL timeouts or WSUS database issues are visible, prioritize database cleanup and performance tuning.
    • If no database issues are found and SUSClientID duplication is ruled out, follow the WSUS client agent troubleshooting article end-to-end for deeper diagnostics.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.