Reclaim Space by Temporarily Disabling Windows 11 Reserved Storage

  • Thread Author
Windows 11’s Reserved Storage can feel like a hidden tax on small SSDs: useful for smooth updates, but frustrating when every gigabyte counts — and there are safe, supported ways to temporarily turn it off, reclaim space, and put it back when you’re done.

Background​

Reserved Storage is an OS-managed allocation on the Windows system volume (usually C that Windows uses as a dedicated pool for servicing operations, update staging, temporary system files, and maintenance of optional features and language packs. Microsoft designed the feature to reduce failed updates caused by low disk space, but on devices with constrained storage (64–256 GB), the allocation can be noticeable and painful.
The amount Windows sets aside varies by installation, optional features, and languages, but Microsoft’s baseline target for many systems has traditionally been around 7 GB. In practice, community testing and documentation commonly report reclaimed amounts in the range of roughly 3–7 GB after disabling the reserve. Expect variability — do not count on a single fixed number for every machine.

Why Reserved Storage Exists (and why you usually shouldn’t remove it)​

Reserved Storage isn’t a mysterious hidden partition — it’s a deliberate buffer that protects Windows servicing (monthly cumulative updates, feature upgrades, component servicing). When Windows needs temporary space to unpack or stage updates, the reserved pool guarantees that servicing can proceed even if user space is low.
  • Protects update integrity — reduces the chance of partially applied updates or failed upgrades.
  • Supports optional features and language packs — keeps components available for servicing without cluttering user-visible free space.
  • Acts as a multi‑purpose temporary pool — when updates aren’t staged, the space can hold other platform temporary files.
Because of these protections, disabling Reserved Storage increases the responsibility on users and administrators to ensure adequate free space for servicing operations. For most users, leaving it enabled is the safest choice.

Quick checklist before you touch Reserved Storage​

Before attempting to disable Reserved Storage, follow this short pre-flight checklist to avoid interruptions and errors:
  • Install all pending Windows updates and reboot. If the system is currently downloading or installing updates, the disable command will often fail with an error saying the reserved storage is “in use.”
  • Run Storage Sense or Disk Cleanup to remove obvious temporary files and previous Windows installations — this reduces risk and makes disabling less necessary.
  • Create a System Restore point or a full backup if the device is critical to your work. Disabling the reserve is reversible, but a backup is a sensible fallback.
  • Make sure you have a plan to re-enable Reserved Storage after the maintenance or the update you’re trying to complete. Treat the change as temporary unless you run a managed deployment with clear update window processes.

How to check the current Reserved Storage state and size​

There are two quick methods to check whether Reserved Storage is enabled and how much is allocated.

GUI method​

  • Open Settings → System → Storage → Show more categories → System & reserved. The Reserved storage entry shows the number of gigabytes currently set aside.

Command-line methods (recommended for precision)​

  • Open an elevated PowerShell or Windows Terminal (Admin). Run:
  • PowerShell: Get-WindowsReservedStorageState
  • Command Prompt: dism /Online /Get-ReservedStorageState
Both report whether Reserved Storage is Enabled or Disabled for the running Windows image. These commands are supported and are the most reliable way to confirm the system state.

Supported methods to temporarily disable Reserved Storage​

There are three supported approaches most admins and power users use: PowerShell cmdlets, DISM (Deployment Image Servicing and Management), and the registry (as a last resort). The PowerShell and DISM methods are preferred because they are supported, scriptable, and intended for admin use. The registry edit can work when other methods fail but carries higher risk and should only be used with a backup.

Option A — PowerShell (simplest for interactive use and automation)​

  • Right-click Start and choose “Windows Terminal (Admin)” or “PowerShell (Admin).”
  • Check the state:
  • Get-WindowsReservedStorageState
  • If the state is Enabled, disable it:
  • Set-WindowsReservedStorageState -State Disabled
  • Reboot the PC and recheck the state:
  • Get-WindowsReservedStorageState
PowerShell will return status information quickly. If the change fails and Terminal reports that the storage is currently in use, complete or cancel any pending updates via Settings → Windows Update and try again.

Option B — DISM (useful for imaging or when DISM parameters are preferred)​

  • Open an elevated Command Prompt.
  • Check the state:
  • dism /Online /Get-ReservedStorageState
  • Disable:
  • dism /Online /Set-ReservedStorageState /Stateisabled
  • Reboot and verify:
  • dism /Online /Get-ReservedStorageState
DISM is widely available across builds and is commonly used in scripted deployment scenarios. If DISM returns “unknown option” or Error 87, your build might not support the ReservedStorage parameter; update Windows or use PowerShell on modern Windows 11 builds.

Option C — Registry edit (fallback; use with caution)​

  • Open Regedit as an administrator.
  • Export the current registry (File → Export) as a backup.
  • Navigate to:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ReserveManager
  • Modify or create the 32-bit DWORD named ShippedWithReserves:
  • Set to 0 to disable Reserved Storage.
  • Set to 1 to re-enable Reserved Storage.
  • Exit Registry Editor and restart.
The registry tweak can prevent the reserve from being re-created by imaging/specialize processes, but many systems do not immediately free space after this change — Windows often waits until the next maintenance/service period to flush and reclaim the reserved pool. Use this approach only if PowerShell/DISM don’t persist across your provisioning workflow.

Expected behavior and timing after disabling​

  • You will usually reclaim several gigabytes of free space, but the exact amount varies widely. Real-world reports commonly show between 3 GB and 7 GB reclaimed. Microsoft’s baseline target in many installs is around 7 GB, but optional features and language packs can increase that amount. Do not expect a precise number.
  • The free-space increase may be immediate on some systems, but on others the reserve is only fully released after Windows performs a maintenance/servicing task (Storage Sense cleanups, cumulative update completion, or background housekeeping), which can be scheduled or occur on a weekly cadence. Because of this, it’s normal if you don’t see the full effect until after a reboot and some background tasks finish.
  • If Windows reports that the operation is “not supported when reserved storage is in use,” finish the pending download/install of updates and reboot before attempting the command again.

How to re-enable Reserved Storage (recommended after updates)​

Restoring the reserve is straightforward and strongly recommended after you finish your immediate maintenance or app update tasks.
  • Open Windows Terminal (Admin) or PowerShell (Admin).
  • Run:
  • Set-WindowsReservedStorageState -State Enabled
  • Reboot the PC.
Windows will allocate the reserved space again for future servicing tasks; you should see a reduction in available free space once the reserve is re-created and housekeeping runs. Treat re-enabling as part of your maintenance checklist.

Troubleshooting common errors​

  • Error: “The storage is currently in use” or “This operation is not supported when reserved storage is in use.”
    Fix: Open Settings → Windows Update, finish any downloads or installs, reboot, and retry the DISM/PowerShell command. If updates are stuck, run Windows Update Troubleshooter or perform the pending update actions manually.
  • DISM returns Error 87 or unknown parameter:
    Fix: Your Windows build may not support the ReservedStorage management flags. Update Windows to a modern build (Windows 10 v2004+ or current Windows 11 builds) or use the PowerShell cmdlets if they are present.
  • Reserve reappears after imaging or specialization:
    Fix: Imaging processes or OEM setup passes can reintroduce Reserved Storage. If you need a persistent change for deployed images, apply the registry change (ShippedWithReserves = 0) during the specialize pass of your image, and include the DISM/PowerShell disable command in your task sequence. Ensure you test the entire provisioning workflow.

Safer alternatives to disabling Reserved Storage (recommended for most users)​

If your goal is to reclaim space without removing Windows’ protective buffer, try these less invasive steps first:
  • Use OneDrive Files On‑Demand to keep personal files in the cloud but accessible locally as placeholders; this can free a lot of space on small drives.
  • Run Storage Sense, Disk Cleanup (including cleaning system files), and remove previous Windows installations. These tools frequently recover multiple gigabytes.
  • Uninstall unused optional features and remove unnecessary language packs (Settings → Apps → Optional features and Settings → Time & language → Language). These can reduce the reserved number without disabling the feature entirely.
  • Move large media files (Photos, Videos) to an external drive or use an SSD/HDD secondary drive for bulk storage.

Enterprise guidance and automation best practices​

For IT pros managing fleets, the choice to disable Reserved Storage must be deliberate and automated where chosen.
  • Document the decision and define criteria (e.g., devices with <128 GB storage are allowed to have Reserved Storage disabled during imaging).
  • Automate the workflow using DISM or PowerShell inside unattended task sequences: check state → disable → reboot → verify. Include guards that re-enable the reserve before feature upgrades or schedule feature upgrades only after temporarily restoring the reserve.
  • For devices that will not be kept up-to-date via Windows Update (e.g., locked-down kiosk builds, VDI golden images), disable the reserve only if you have a controlled servicing pipeline or other means to apply updates safely. Consider staging updates from an internal server to avoid servicing failures.
  • When planning feature updates, require a safe free-space threshold — many admins recommend 10–20 GB of free system volume before a feature upgrade; treat any 5 GB figure as a short-term minimum for smaller patches, not a guarantee for feature updates.

Security and stability considerations​

  • The registry edit method (ShippedWithReserves) is powerful but risky: incorrect changes to other keys can destabilize the system. Always export the registry before editing and test changes on a non-production machine.
  • Disabling Reserved Storage increases the chance that a large cumulative or feature update will fail if free space unexpectedly drops. That can lead to complex recovery steps and increased helpdesk tickets. Treat disabling Reserved Storage as a temporary, controlled action — not a permanent optimization — unless you operate in a managed environment with clear servicing rules.
  • Keep in mind that Windows may opportunistically reintroduce or reallocate reserved space after imaging, optional feature installation, or other system changes. Periodically verify the state if you need deterministic free-space behavior.

Step-by-step recipe: safely reclaim space to update an app (concise)​

  • Open Settings → Windows Update. Install and finish any pending updates. Reboot.
  • Run Storage Sense and Disk Cleanup (clean system files). Remove obvious large files or move them externally.
  • Open Windows Terminal (Admin). Check the state: Get-WindowsReservedStorageState.
  • If Enabled, disable: Set-WindowsReservedStorageState -State Disabled. Reboot.
  • Confirm reclaimed space in Settings → System → Storage → System & reserved. Complete the app update or file transfer.
  • Re-enable: Set-WindowsReservedStorageState -State Enabled and reboot. Confirm the reserve is reallocated.

Final recommendations and practical guidance​

  • Treat Reserved Storage as a temporary tool: disable it only when you need to reclaim space for a specific maintenance task. Re-enable as soon as that task is complete.
  • Prefer PowerShell or DISM for supported, auditable changes. Resort to the registry only when necessary and after exporting a backup.
  • For home users with small SSDs, use cloud storage (OneDrive Files On‑Demand) and Storage Sense first — those usually solve the problem without removing Windows’ safety net.
  • For IT teams, automate checks and maintain documentation so devices don’t inadvertently lose the protective benefits of Reserved Storage during critical servicing windows.

Conclusion​

Reserved Storage is a pragmatic engineering response to an old problem — failed updates caused by insufficient temporary space — but on small drives it can be an unwelcome occupant. Windows provides supported, reversible controls (PowerShell, DISM, and a registry fallback) to temporarily disable the reserve when you’re pressed for space, and to restore it afterwards. Use those controls carefully: finish pending updates first, back up the registry, and re-enable the reserve when you’re done. For most users, safer alternatives such as OneDrive Files On‑Demand, Storage Sense, and removing unused optional features will free space without removing the buffer Windows uses to keep updates reliable.

Source: Guiding Tech How to Temporarily Disable Reserved Storage in Windows 11