WSUS: how to repair the SUSDB database (reset WID and content)

If your WSUS console shows unexpected errors and won’t open (or hangs), you can reset WSUS by removing the SUSDB database (WID) and the content directory (C:\WSUS), then running post-install with Wsusutil.exe. This procedure returns WSUS to a clean state.

⚠️ Warning: you will lose previous configuration/syncs. Back up if you need to preserve anything.

Typical symptom

“The WSUS administration console has encountered an unexpected error. This might be due to a transient error; try restarting the administration console. If the error persists…”

This often happens after years without maintenance, SUSDB corruption, or inconsistent content.

Requirements

Administrator rights on the WSUS server.
PowerShell access.
HeidiSQL (or another client) if you want to drop the DB via GUI (optional).
Runtime: can take a while if C:\WSUS is large.

Step 1 — Stop services (IIS + WSUS)

Stop-Service -Name W3SVC, WSUSService -Force

Step 2 — Remove the SUSDB database (WID)

Remove the Windows Internal Database (WID) files:

Remove-Item -Path "C:\Windows\WID\Data\SUSDB.mdf","C:\Windows\WID\Data\SUSDB_log.ldf" -Force -ErrorAction SilentlyContinue

More aggressive option (removes entire db folder; use with care):
Remove-Item -Path "C:\Windows\WID\Data\SUSDB*" -Force -ErrorAction SilentlyContinue

GUI option: drop the DB with HeidiSQL (optional)

Connect to WID via named pipe:

Type: Microsoft SQL Server (named pipe)
Host: \\.\pipe\MICROSOFT##WID\tsql\query
Authentication: Windows (integrated)
Query (to force offline and drop):

ALTER DATABASE SUSDB SET OFFLINE WITH ROLLBACK IMMEDIATE;
DROP DATABASE SUSDB;

CLI alternative:

sqlcmd -S np:\\.\pipe\MICROSOFT##WID\tsql\query -E -Q "ALTER DATABASE SUSDB SET OFFLINE WITH ROLLBACK IMMEDIATE; DROP DATABASE SUSDB;"

Step 3 — Clean WSUS content

Remove downloaded content to avoid inconsistencies:

Remove-Item -Path "C:\WSUS\*" -Recurse -Force -ErrorAction SilentlyContinue

Recreate the folder if needed:

New-Item -ItemType Directory -Path "C:\WSUS" -Force | Out-Null

Step 4 — Start services

Start-Service -Name W3SVC, WSUSService

Step 5 — WSUS post-install

Run post-install pointing to the new CONTENT_DIR:

Set-Location "C:\Program Files\Update Services\Tools"
.\Wsusutil.exe postinstall CONTENT_DIR="C:\WSUS"

If the Configuration Wizard doesn’t appear, reboot the server and open it manually.

Quick verification

Open the WSUS Console and complete the wizard (languages, products, classifications, sync source).
Run an initial sync and check Event Viewer (Application) and WSUS logs.
(Optional) Run a content reset if needed:
```
.\Wsusutil.exe reset
```

Recommended cleanup and maintenance

Schedule Invoke-WsusServerCleanup (PowerShell) periodically to purge obsolete revisions.
Monitor the size of C:\WSUS and move content to a volume with enough space if it grows quickly.
Document products/classifications you actually need to minimize space and sync time.

Common issues (and fixes)

Can’t connect to WID via named pipe → ensure the Windows Internal Database service is running and you use Windows authentication.
Errors when deleting files → stop W3SVC and WSUSService properly; use -Force and check permissions.
Console still fails → check WSUS roles/features, reinstall if a component is missing, and verify .NET and IIS.
Endless sync → reduce products/classifications and let the first sync finish (it can take a long time).

Conclusion

Resetting SUSDB and content with Wsusutil.exe postinstall returns WSUS to a clean state when the console fails persistently. After the wizard and a first sync, you should be back to normal operation.

Guilgo Blog