Objective
Handle a nearly full Windows Server system disk without deleting WinSxS or logs at random by measuring usage, identifying supported cleanup targets, checking VSS, moving durable data, and restoring safe free-space headroom.
Prerequisites
- Documented protected workloads, repositories, retention and expected RPO/RTO.
- A restore target or isolated test location that cannot overwrite production data.
- Administrative access appropriate to the system being changed or diagnosed.
- A clearly identified scope: affected users, systems, addresses, services and the time of the observed problem.
- A maintenance or test window when the procedure can affect production traffic or availability.
- A copy of the current configuration or other recovery material before any irreversible action.
Step-by-step procedure
Establish the baseline and scope
Before changing anything, reproduce the issue or document the requested change on a representative system. Record the affected users or services, exact time, current configuration, recent changes and a known-good comparison point. This baseline is the reference used to decide whether each later step improves the situation.
- The scope and current state are documented well enough to reproduce or verify the procedure.
Usage
Work through this operational element in a controlled sequence: usage. Record the current state, verify dependencies, perform the smallest necessary action, and validate its effect before continuing. If the result differs from the expected state, stop and reassess rather than stacking additional changes.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Supported cleanup targets
Work through this operational element in a controlled sequence: supported cleanup targets. Record the current state, verify dependencies, perform the smallest necessary action, and validate its effect before continuing. If the result differs from the expected state, stop and reassess rather than stacking additional changes.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
VSS
Work through this operational element in a controlled sequence: VSS. Record the current state, verify dependencies, perform the smallest necessary action, and validate its effect before continuing. If the result differs from the expected state, stop and reassess rather than stacking additional changes.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Moving durable data
Work through this operational element in a controlled sequence: moving durable data. Record the current state, verify dependencies, perform the smallest necessary action, and validate its effect before continuing. If the result differs from the expected state, stop and reassess rather than stacking additional changes.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Restoring safe free-space headroom
Work through this operational element in a controlled sequence: restoring safe free-space headroom. Record the current state, verify dependencies, perform the smallest necessary action, and validate its effect before continuing. If the result differs from the expected state, stop and reassess rather than stacking additional changes.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Validate the complete service
Repeat the original user, system or application workflow from the real source and verify the complete result, not only one command or one local check. Confirm that logs and monitoring show the expected behavior and that no temporary debug, bypass, test account, rule or maintenance setting remains enabled.
- The end-to-end service works or the remaining failure is isolated to a clearly identified component.
Technical commands from the original procedure
These technical blocks are preserved byte-for-byte from the historical procedure and kept in their original order. Review names, addresses, paths and parameters before use.
Get-Volume | Select DriveLetter,FileSystemLabel,Size,SizeRemaining,HealthStatusGet-PSDrive -PSProvider FileSystem | Select Name,Used,FreeGet-ChildItem C: -File -Force -ErrorAction SilentlyContinue | Sort Length -Descending | Select -First 20 FullName,LengthGet-ChildItem C:WindowsTemp -Force -ErrorAction SilentlyContinue | Measure-Object -Property Length -SumDISM /Online /Cleanup-Image /AnalyzeComponentStoreDISM /Online /Cleanup-Image /StartComponentCleanupcleanmgr /d C: /LOWDISKGet-Service wuauserv,bits | Select Name,Status,StartTypeGet-ChildItem C:WindowsSoftwareDistribution -Force -ErrorAction SilentlyContinue | Measure-Object -Property Length -Sumvssadmin list shadowstoragevssadmin list shadowsGet-Partition -DriveLetter C | Get-VolumeGet-Disk | Select Number,FriendlyName,Size,PartitionStyleValidation
The procedure is validated when:
- The original symptom or change request has been tested end to end.
- The effective configuration matches the intended design and no unexplained error remains in the relevant logs.
- Temporary troubleshooting controls have been removed and monitoring remains normal.
- The result, evidence and any follow-up action are documented.
Rollback
- Restore the configuration, policy, binding, route, credential assignment or service state recorded in the baseline when the change does not meet its success criteria.
- Remove temporary rules, test objects and diagnostic settings that were introduced only for the procedure.
- After rollback, repeat the minimum health checks to confirm that the previous service level has been restored.
Troubleshooting / common errors
- Separate source snapshot failures, transport failures, repository failures and application-consistency failures.
- If a repair requires deleting a chain, create or verify another recoverable copy first.
- If the result changes between tests, compare source, destination, identity, time and policy context before changing additional settings.
- If a command succeeds but the application still fails, continue at the next protocol or application layer instead of widening access.
- If the expected evidence is missing, verify that logging, auditing and the test path actually cover the failing component.
- If the change does not improve the measured symptom, restore the previous state and reassess the working hypothesis.