How to Move the WSUS Content Folder to a Different Drive

Windows Server Update Services, or WSUS, can consume a significant amount of disk space over time. This becomes especially noticeable in environments that store Microsoft update content locally instead of downloading updates directly from Microsoft during client installation.

In many environments, the default WSUS installation path on the C: drive eventually becomes a problem because the system volume was never sized for long-term update storage. This guide walks through the Microsoft-supported method for moving the WSUS content folder to a different drive path safely and efficiently.

Why Move the WSUS Content Folder?

• Free up space on the system drive.
• Improve storage performance by using dedicated disks.
• Simplify storage management and backup operations.
• Prepare for future WSUS growth and update expansion.
• Reduce the risk of failed updates caused by low disk space.

Prerequisites

• Administrator access to the WSUS server.
• A new NTFS-formatted destination drive or partition.
• Adequate free space on the target drive.
• A maintenance window if this is a production WSUS environment.
• A recent backup or snapshot of the server.

Step 1: Verify the Current WSUS Content Location

Open PowerShell as Administrator and run the following command:

Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Update Services\Server\Setup | Select-Object ContentDir

The default WSUS content location is typically:

C:\WSUS\WsusContent

Step 2: Stop WSUS and IIS Services

Before moving the content, stop the WSUS and IIS services to prevent file locks and database synchronization issues.

Stop-Service WsusService
Stop-Service W3SVC

Alternatively, you can stop IIS completely using:

iisreset /stop

Step 3: Create the New WSUS Folder

Create the destination directory on the new drive. For example:

New-Item -Path D:\WSUS -ItemType Directory

Ensure the NETWORK SERVICE account has appropriate permissions to the new folder before moving content.

Step 4: Move the WSUS Content Using wsusutil

Microsoft recommends using the built-in wsusutil utility rather than manually moving files. This ensures the WSUS configuration database is updated correctly.

cd "C:\Program Files\Update Services\Tools"
.\wsusutil.exe movecontent D:\WSUS D:\WSUS\move.log

This process may take time depending on the size of the existing WSUS repository.

Step 5: Restart Services

iisreset /start
Start-Service WsusService

Step 6: Verify the New Location

Verify that WSUS is now pointing to the new content directory:

Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Update Services\Server\Setup | Select-Object ContentDir

Open the WSUS console and confirm there are no synchronization or content-related errors.

Troubleshooting Tips

• Do not manually modify the registry unless absolutely necessary.
• Avoid enabling NTFS compression or deduplication on the WSUS content directory.
• Ensure antivirus exclusions are configured appropriately for WSUS folders.
• If the C: drive is critically full, pre-stage files with Robocopy before running wsusutil.
• Review the move.log file for errors after the migration completes.

Optional: Pre-Stage the Files with Robocopy

If the system drive is already low on space, you can pre-copy the files before running wsusutil:

robocopy C:\WSUS D:\WSUS /MIR /COPYALL /R:2 /W:2

After the copy completes, run the wsusutil movecontent command again to finalize the migration.

Conclusion

Moving the WSUS content folder to a different drive is a straightforward but important maintenance task for Windows administrators. Using the supported wsusutil method ensures the migration is performed safely while minimizing the risk of corruption or synchronization issues.

With proper planning, verification, and service control, the process can usually be completed with minimal downtime while reducing pressure on the Windows system drive.