Recreating the SUSDB and WSUS Content Folder in WSUS (Windows Server)

by

Maintaining your WSUS (Windows Server Update Services) can sometimes feel overwhelming, especially if the SUSDB is cluttered with old or unnecessary updates, or the Content folder has become bloated due to accidental settings changes. At times like these, starting fresh with a clean database and content repository can be the most efficient solution.

Here’s your step-by-step guide:

Why You Might Want a Clean Rebuild

  • Your SUSDB is outdated and accumulates unneeded updates.
  • Content folder has grown massively, perhaps after unchecking “download update files… only when updates are approved.”
  • A rebuild can often be faster and more reliable than trying to repair a messy WSUS setup.
    Microsoft Learn

Step-by-Step Rebuild Instructions

1. Stop WSUS and IIS Services

Run PowerShell as Administrator and stop both services:

Stop-Service WSUSService, W3SVC
Get-Service WSUSService, W3SVC  # Verify both are stopped

Microsoft Learn

2. Connect to SUSDB via SQL Server Management Studio (SSMS)

  • Determine your SUSDB type:
    • If installed on Windows Internal Database (WID): Use connection \\.\pipe\MICROSOFT##WID\tsql\query.
    • If on a full SQL Server instance: Connect using ServerName\InstanceName.
      Microsoft Learn
  • For WID, you may need SQL Management Studio Express, matched to the correct version/SP level of WID.
    Microsoft Learn

3. Backup and Delete SUSDB

1. Backup the SUSDB
Open SQL Server Management Studio (SSMS).
Connect to your WSUS SQL instance:
WID: \\.\pipe\MICROSOFT##WID\tsql\query
Full SQL: ServerName\InstanceName
In Object Explorer, expand Databases → SUSDB.
Right-click SUSDB → Tasks → Back Up….
In the Back Up Database dialog:
Select Full Backup.
Set destination to a secure path, e.g., D:\SQL\Backup\SUSDB_Full.bak.
Under Options, check Verify backup when finished.
Click OK to execute.
✅ Your .bak file is now ready for recovery if needed.

2. Detach the SUSDB
After the backup:
In Object Explorer, right-click SUSDB.
Choose Tasks → Detach….
In the Detach Database dialog:
Check Drop Connections if other processes are connected.
Click OK.
👉 SUSDB will disappear from the Databases list in SSMS.

3. Rename the SUSDB Files
Now, locate the physical database files:
By default, WID/SQL stores them in:

C:\Windows\WID\Data\
or

C:\Program Files\Microsoft SQL Server\MSSQL<version>.MSSQLSERVER\MSSQL\Data\
Look for:
SUSDB.mdf (data file)
SUSDB_log.ldf (log file)
Rename them to archive versions, for example:

SUSDB_OLD.mdf SUSDB_log_OLD.ldf
This prevents conflicts when you recreate a fresh SUSDB.

4. (Optional) Re-Attach Later
If you ever need the old SUSDB back:
In SSMS, right-click Databases → Attach….
Click Add… and browse to the renamed SUSDB_OLD.mdf.
The log file (SUSDB_log_OLD.ldf) will auto-associate, or you can point to it manually.
Click OK to restore the old database.

✅ With this workflow, you have:
A .bak file backup for restore.
A detached and renamed copy of the old SUSDB.
A clean slate for WSUS to generate a fresh database during post-install.

4. Recreate (or Replace) the Content Folder

  • Locate your content directory path from the registry key: HKLM\Software\Microsoft\Update Services\Server\Setup\ContentDir
  • Rename or delete the old folder: REN <Path>\WSUS WSUS_old Or: DEL <Path>\WSUS /A /Q
  • Recreate the directory: MKDIR <Path>\WSUS This ensures proper default permissions are applied.
    Microsoft Learn
  • (Optional) If you’re only rebuilding content (not SUSDB), you can force download of approved updates using: cd "C:\Program Files\Update Services\Tools" .\WsusUtil.exe reset

Microsoft Learn

5. Restart WSUS and IIS

Start-Service WSUSService, W3SVC
Get-Service WSUSService, W3SVC  # Confirm both services are running

Microsoft Learn

6. Run WSUS Post-Install

Navigate to:

cd "C:\Program Files\Update Services\Tools"

Then run:

  • For WID setups: .\Wsusutil.exe postinstall CONTENT_DIR="<drive>:\WSUS"
  • For SQL Server setups: .\Wsusutil.exe postinstall SQL_INSTANCE_NAME="Server\Instance" CONTENT_DIR="<drive>:\WSUS"

Microsoft Learn

This command reinstalls the SUSDB, recreates the WSUS website (typically on port 8530), and points to the new content directory. Logs will be created in your Temp folder and WsusUtilUseCustomWebSite.log to track progress.
Microsoft Learn

7. Run the Configuration Wizard

The first time you open the WSUS console after this process, the WSUS Configuration Wizard will launch automatically. You can set your update selections, upstream server, SSL preferences, proxy, and more.
Microsoft Learn

Summary Table

StepAction
1Stop WSUS and IIS
2Connect to WID or SQL via SSMS
3Backup & delete SUSDB
4Rename/delete and recreate Content folder
5Restart services
6Run wsusutil.exe postinstall
7Run WSUS Configuration Wizard

Final Thoughts

Rebuilding the SUSDB and content folder can breathe new life into a sluggish or cluttered WSUS server. This process is especially helpful when you are:

  • Removing years of accumulated update debris
  • Recovering from misconfiguration
  • Migrating WSUS to a fresh-scale state

Caution: If you use SSL or custom IIS bindings, you may need additional post-configuration steps.

Leave a Comment