Windows 10 ESU enrolled but security update warning persists

OS build 19045.7807 confirms that the October 2026 Windows 10 22H2 ESU security update KB5126657 is installed, so the persistent warning does not indicate that this monthly security update is missing.^1^

Verify the ESU update state

1. Press Windows key + R, enter winver, and verify:
   • Version: 22H2
   • OS build: 19045.7807
2. Open PowerShell as Administrator and run:

Get-ComputerInfo |
  Select-Object WindowsProductName, WindowsVersion, OsBuildNumber

Get-HotFix -Id KB5126657,KB5128925 |
  Select-Object HotFixID, Description, InstalledOn

Expected result:

• KB5126657 is present and the build is 19045.7807. This is the October 13 operating-system security update and explicitly applies to Windows 10 ESU.^1^
• KB5128925 is the separate October 13 cumulative security update for .NET Framework 3.5, 4.8, and 4.8.1; it does not determine the Windows OS build.^2^

Get-HotFix does not always enumerate every package. If either entry is absent there but appears in Settings → Update & Security → Windows Update → View update history, verify it through DISM:

dism /online /get-packages /format:table | findstr /i "5126657 5128925"

Your reported build and successful installation history already satisfy the most important checks.

Allow Windows Update to refresh its status

A matching Windows 10 22H2 Consumer ESU case reported the same warning despite confirmed enrollment, a current security build, successful DISM/SFC checks, and a rebuilt update cache. The moderator-recommended non-destructive action was to wait two or three days for WaaSAssessment to reevaluate the device.^3^

During that period:

• Leave normal Windows Update and telemetry-related scheduled tasks enabled.
• Keep the PC periodically powered on and connected to the Internet.
• Reopen Windows Update after the reevaluation period.

Do not use usoclient startassessment; the matching Q&A answer states that it does not trigger this assessment.^3^

Since you have already run the troubleshooter, DISM, SFC, restarted, and rebuilt SoftwareDistribution, repeating those operations is unlikely to add useful information.

If the banner remains after several days

Avoid deleting or manually recreating the WaaSAssessment registry data. Although that workaround cleared the banner in one report, its author explicitly identified it as not an officially supported Microsoft remediation.^4^

Instead:

1. Capture screenshots of:
   • winver
   • The ESU enrollment confirmation
   • Windows Update history showing KB5126657
   • The persistent warning
2. Submit the issue through Feedback Hub → Windows Update, or contact Microsoft support as an ESU installation/licensing issue.
3. Continue checking subsequent monthly updates by comparing the installed build and KB with Microsoft’s release article. ESU supplies critical and important security updates, but not new features or general nonsecurity updates.^5^

An in-place repair should be reserved for a later failure to install an offered update—not merely this stale banner while the current ESU cumulative update is demonstrably installed.

References

1. October 13, 2026—KB5126657 (OS Builds 19045.7807 and 19044.7807 ...
2. October 13, 2026-KB5128925 Cumulative Update for .NET Framework 3.5, 4. ...
3. Windows 10 22H2 Consumer ESU: “Missing Important Security and Quality Fixes” persists despite KB5120249 installed and ESU enrollment confirmed - Microsoft Q&A
4. Windows 10 22H2 Consumer ESU: “Missing Important Security and Quality ...
5. Extended Security Updates (ESU) program for Windows 10