Windows Server 2016 — WinSxS Growth Exhausts C: and Breaks Patch Installation — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Patch installation fails due to low disk space as component store growth consumes C:. Critical updates cannot stage.

Environment & Reproduction

Common on long-lived servers without periodic cleanup or log rotation.

Get-PSDrive C
dism /online /cleanup-image /analyzecomponentstore

Root Cause Analysis

Superseded components and stale update artifacts accumulate beyond available free space thresholds.

Quick Triage

Measure largest directories and identify immediate reclaim opportunities.

Get-ChildItem C: -Directory | ForEach-Object { $_.FullName, (Get-ChildItem $_.FullName -Recurse -Force -ErrorAction SilentlyContinue | Measure-Object Length -Sum).Sum }

Step-by-Step Diagnosis

Confirm WinSxS reclaimable package state and pending cleanup tasks.

dism /online /cleanup-image /analyzecomponentstore
Get-ScheduledTask -TaskName StartComponentCleanup

Solution — Primary Fix

Run component cleanup and clear obsolete update cache before retrying update.

dism /online /cleanup-image /startcomponentcleanup
cleanmgr /sageset:1
cleanmgr /sagerun:1

Solution — Alternative Approaches

Temporarily extend system volume and move non-system logs to data drive.

Get-Volume
Move-Item C:Logs* D:Logs -Force

Verification & Acceptance Criteria

Sufficient free space exists and update package stages successfully.

Get-PSDrive C
Get-HotFix | Select -First 5

Rollback Plan

Restore moved data and previous cleanup policy if application behavior changes.

Move-Item D:Logs* C:Logs -Force

Prevention & Hardening

Schedule monthly component cleanup and disk capacity alerts for system volumes.

schtasks /Query /TN "MicrosoftWindowsServicingStartComponentCleanup"

Related Errors & Cross-Refs

Related: 0x80070070 disk full, rollback on reboot, SoftwareDistribution bloat.

Related tutorial: View the step-by-step tutorial for Windows Server 2016.

View all Windows Server 2016 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Windows Server storage and servicing best practices from Microsoft Learn.