Windows Update is not updated

吉村 誠 0 Reputation points
2025-02-04T07:59:50.42+00:00

Issue

The 24H2 update is not being applied to a device under WSUS management.

Device Information

  • OS: Windows 11 23H2 (Currently Applied)
  • Installed Updates:
    • KB5034467
    • KB5012170
    • KB5026039
    • KB5027397
    • KB5035853
    • KB5035967

Background

  • Attempted to update the device to 24H2 via WSUS.
  • WSUS indicated that 24H2 was installed on the device.
  • The update status for 24H2 on WSUS showed "Installed" and "Not Applicable."
  • Due to issues with 24H2, the device was downgraded to 23H2.
  • The WSUS console became corrupted, requiring a rebuild.
  • After rebuilding WSUS, the device still appeared as having 24H2 applied.
  • Mismatch identified between the update status on the device and WSUS.

Investigation

  • Renamed "SoftwareDistribution" and "catroot2" directories and attempted an update → Issue not resolved.
  • Deleted the device from WSUS and re-registered it → Issue not resolved.
  • Executed "Windows11InstallationAssistant.exe" on the device.
    • The system prompted "Check compatibility using PC Health Check App."
    • Confirmed that 24H2 is NOT installed on the device.

Findings

  • WSUS shows 24H2 as installed, but the device is still on 23H2.
  • Confirmed that a manual update to 24H2 is possible.

Request for Guidance

  1. Why does WSUS indicate that 24H2 is applied when it is not installed on the device?
  2. What steps should be taken to resolve this issue?
  3. It is evident that the SQL database in WSUS is corrupted. How can the data be corrected?

I would appreciate insights from those with relevant expertise.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,571 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Adam J. Marshall 9,686 Reputation points MVP
    2025-02-06T01:01:15.3566667+00:00

    First, reporting happens at the client, not WSUS. So run the client side script after deleting the computer from the WSUS MMC Console. Even if you think you've done this before, please do it with my script.

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

    If after that, the computer still doesn't show that it needs 24H2, run winvir and post a screenshot.


  2. Adam J. Marshall 9,686 Reputation points MVP
    2025-02-06T01:32:29.8333333+00:00

    what's winver say on the client system? (Start > winver)


Your answer

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