Fixing Common WSUS Errors on Windows Server 2022/2025 (Plus: Is WSUS Still Supported?)

— WSUS still ships with and works on Server 2022 and 2025, and Microsoft has continued servicing it, but it’s a fair moment to think about whether WSUS is still the right long-term fit for your environment rather than assuming it’ll be supported indefinitely. If you’re maintaining WSUS today, here are the most common errors and fixes.

“The WSUS content directory is corrupt” / content download failures

Usually caused by the content store getting into an inconsistent state relative to the WSUS database. Run the built-in reset tool from an elevated command prompt:

wsusutil.exe reset

This forces WSUS to re-verify every update’s content against the database and re-download anything missing or mismatched — it can take a long time on a large content store, so expect this to run for hours on a mature WSUS install with years of accumulated updates.

Clients not reporting / stuck at “Not Yet Reported”

1. On the client, check the Windows Update client’s connection to WSUS:

Get-WindowsUpdateLog

(This compiles the readable log from ETW traces — check the output file for connection errors to your WSUS server’s URL.)

1. Confirm the client’s GPO-assigned WSUS server URL is correct and reachable:

gpresult /r

Look for the Windows Update policy settings under Computer Configuration.

1. Force a fresh check-in:

wuauclt /resetauthorization /detectnow

(On current Windows versions wuauclt has limited functionality compared to older releases — if this doesn’t trigger a visible change, use the Settings app’s “Check for updates” instead, or trigger detection via the UsoClient utility.)

WSUS console won’t open / “Could not access SQL Server”

If WSUS is using Windows Internal Database (WID) rather than full SQL Server (the default for most WSUS installs), confirm the WID service is actually running:

Get-Service -Name MSSQL$MICROSOFT##WID

If it’s stopped, start it and retry the console. If WSUS is pointed at a separate SQL Server instance instead, confirm that instance is reachable and the WSUS service account has the permissions it needs on the SUSDB database.

Disk filling up on the WSUS server

WSUS content stores grow indefinitely by default unless you’re actively declining superseded and expired updates. Run Server Cleanup Wizard (in the WSUS console, under Options) regularly, or automate it with the Invoke-WsusServerCleanup PowerShell cmdlet, to decline superseded updates and reclaim space from content that’s no longer needed.

If you’re weighing whether to keep using WSUS at all

Given the deprecation announcement, if you’re standing up update management fresh rather than maintaining an existing WSUS deployment, it’s worth evaluating Windows Autopatch (for Intune-managed, cloud-first environments) or Azure Update Manager (for a lighter-weight, Azure Arc-compatible option covering both cloud and on-prem servers) before investing further in WSUS infrastructure — neither requires abandoning WSUS on day one, but both are the direction Microsoft is actively investing in.