Disable Reserved Storage in Windows 10/11 to reclaim 3–7 GB safely

Microsoft’s Reserved Storage can quietly hold back roughly 7 GB of your system drive, and there are safe, supported ways to turn it off — but doing so trades a small amount of automated update resilience for more usable disk space on tight SSDs. This guide explains what Reserved Storage is, how it behaves in Windows 10 and Windows 11, the exact commands and registry edits used to disable it, the realistic space you can expect to reclaim, and the risks and mitigations every Windows administrator and knowledgeable power user should consider before flipping the switch.

Background / Overview​

Reserved Storage is a Microsoft-managed feature introduced with Windows 10 and refined in Windows 11 that preallocates a portion of the system volume for OS updates, temporary files, and caches. The feature’s stated goal is simple: reduce failed update attempts and make update installations more predictable on devices with low free space.
By design, the allocation is dynamic — it can expand or contract based on installed optional features, language packs, and available free space. On new installs Microsoft has targeted a baseline of roughly 7 GB, though on very small drives the system will initially reserve a smaller amount (for example, a minimum of about 2% of the system volume or ~3 GB, whichever is lower) and grow back to the original allocation when space allows.
Reserved Storage is intended to be transparent to most users, but on laptops and tablets with 64–128 GB SSDs that 7 GB can be painfully visible, and for managed fleets IT pros sometimes prefer manual control over how that space is used.

---

How Reserved Storage Works (Technical underpinnings)​

What the reserve actually contains​

Reserved Storage is not a single immutable partition — it’s an OS-managed allocation on the system volume that the OS uses for:

• Windows update staging and temporary working space during servicing
• System temporary files and caches used by the OS
• Content associated with optional features and language maintenance

The reserve gives Windows a predictable buffer so that feature updates and cumulative updates have somewhere to stage temporary files without requiring the user to free large amounts of disk space first.

Dynamic sizing rules​

Reserved Storage is dynamic. Key behaviors to remember:

• It typically starts at about 7 GB, but this is a baseline and varies with device and installed optional components.
• On space-constrained devices Windows may use a reduced initial allocation (examples as low as ~3 GB or a proportion of the system volume).
• Installing additional optional features or language packs can increase the reserve automatically.
• Storage management tasks (for example, Storage Sense cleaning or removing previous Windows installations) can allow the reserve to grow back toward its target size.

Visibility and user controls​

Windows exposes the reserve size in the Storage UI (System → Storage → Show more categories → System reserved or similar label depending on the build). For scripted or remote management you can query the state from an elevated command prompt or PowerShell session.

---

Why people disable Reserved Storage​

• Devices with small SSDs (e.g., 64 GB or 128 GB) are most affected; reclaiming that 7 GB can materially change usability.
• IT teams that use custom imaging or manage disk resources tightly sometimes prefer deterministic control instead of a background reserve.
• Some deployment scenarios (thin-client images, VDI templates, or development VMs) benefit from the extra free space and have controlled update schedules that minimize the need for Windows’ automated reserve.

That said, the feature exists to reduce the chance of update failures — removing it increases the responsibility on administrators and users to ensure there’s adequate space for servicing operations.

---

How to check whether Reserved Storage is enabled​

Run either of these from an elevated (Administrator) command prompt or PowerShell:

• DISM (Command Prompt):
• dism /Online /Get-ReservedStorageState
• PowerShell:
• Get-WindowsReservedStorageState

Both commands report whether Reserved Storage is Enabled or Disabled for the running Windows image. You can also view the reserve size in the Storage settings UI under System reserved on most Windows builds.

---

How to disable Reserved Storage — exact, supported methods​

Below are the primary supported methods for toggling Reserved Storage. All require Administrator privileges.

1) DISM (Deployment Image Servicing and Management) — recommended for single machines and imaging steps​

Steps:

• Open Command Prompt as Administrator.
• Check state:
• dism /Online /Get-ReservedStorageState
• Disable:
• dism /Online /Set-ReservedStorageState /Stateisabled
• Reboot (recommended) and verify:
• dism /Online /Get-ReservedStorageState

Notes:

• The DISM commands were introduced for Windows 10 / Windows 11 servicing and will work on builds that include the Reserved Storage management parameters.
• If you receive an error (for example, Error 87 or “operation not supported when reserved storage is in use”), ensure no servicing operation (Windows Update) is in progress and try again after updates complete.

2) PowerShell — helpful for automation and scripts​

Steps:

• Open PowerShell as Administrator.
• Check state:
• Get-WindowsReservedStorageState
• Disable:
• Set-WindowsReservedStorageState -State Disabled
• Reboot (recommended) and verify:
• Get-WindowsReservedStorageState

Notes:

• These cmdlets provide the same control as DISM and are easier to script for multiple endpoints or in management systems.

3) Registry Edit — useful when other methods don’t persist (use cautiously)​

Path:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ReserveManager

Key and values commonly used:

• ShippedWithReserves — a 32-bit DWORD value
• Set to 1 to enable
• Set to 0 to disable

Steps:

• Run regedit as Administrator.
• Navigate to the ReserveManager key above.
• Modify or create the DWORD named ShippedWithReserves and set it to 0.
• Reboot.

Important caveats:

• On some systems the registry change alone will not immediately free the reserved space; the reserve may be removed after the next servicing operation (for example a cumulative update) or when Windows performs its background housekeeping.
• Some deployment setups have reported that registry changes are the only reliable way to keep Reserved Storage disabled across setups; in other scenarios DISM flags may be re-applied during image specialization.

---

What to expect after disabling: realistic reclaimed space and timing​

• Typical reclaimed space: 3–7 GB is commonly reported. Microsoft targets about 7 GB as the baseline for newly installed systems, but the actual reclaimable amount depends on your device’s current reserve size, optional features, and installed languages.
• Timing: the visible free space increase can be immediate in some cases, but on many systems the reserved pool is only fully released after Windows runs a maintenance/servicing task (for example, a cumulative update or Storage Sense cleanup). You may need to reboot and allow Windows to complete background tasks to see the full effect.
• Variability: if optional features or language packs increased the reserve before you disabled it, your reclaimed space may be larger. Conversely, if the reserve had already shrunk due to small disk size, the visible gain may be smaller.

---

Risks and mitigation strategies​

Disabling Reserved Storage is a trade-off. Below are the major risks and practical mitigations.

Risk: update or feature upgrade failures​

• Why it happens: Reserved Storage provides guaranteed local working space during servicing. If Windows needs temporary space for an update and the system is nearly full, the update may fail or require manual intervention.

Mitigations:

• Before major feature updates, temporarily re-enable Reserved Storage, or ensure at least 10–20 GB of free space on the system volume.
• Use Storage Sense, Disk Cleanup, or external USB storage to free space prior to updates.
• For enterprise deployments, schedule feature updates during maintenance windows and ensure target machines have sufficient free space or pre-stage updates from management servers.

Risk: unexpected reallocation or background behavior​

• Windows may opportunistically increase the reserve again if disk space improves or if optional features are later installed.
• Keep monitoring with the DISM or PowerShell queries after large system changes.

Mitigations:

• When automating at scale, include periodic checks in your management scripts to verify the reserve state and reconcile it with policy.
• Consider removing unused optional features and language packs as a safer long-term strategy to reduce reserved sizing rather than permanently disabling the mechanism.

Risk: regedit mistakes and system instability​

• Registry edits always carry risk.

Mitigations:

• Back up the registry before edits.
• Prefer DISM or PowerShell methods unless you have a deployment-specific need for registry control.

---

Alternatives to fully disabling Reserved Storage​

If the goal is to reclaim space but retain some update resilience, consider these less intrusive options:

• Uninstall unused optional features (Settings → Apps → Optional features) — this often reduces the reserve automatically.
• Remove extra language packs you don’t use (Settings → Time & Language → Language).
• Use Storage Sense to aggressively clean temporary files and old update data.
• Move large user files (Photos, Videos) to an external drive or cloud storage; enable OneDrive Files On-Demand to keep files online without local copies.
• Offload apps to a secondary data drive if available.

These alternatives preserve the reserve’s protective benefits while sometimes reclaiming multiple gigabytes.

---

Enterprise deployment notes and automation best practices​

For IT pros deploying Windows across fleets, the decision to disable Reserved Storage should be documented and automated.
Recommendations:

• Centralize decision-making: define whether devices that meet certain storage thresholds should have reserved storage enabled or disabled as part of build standards.
• Script the change: use PowerShell or DISM in unattended task sequences:
• Example flow: run Get-WindowsReservedStorageState → if Enabled run Set-WindowsReservedStorageState -State Disabled → reboot → verify.
• Use configuration management: integrate the commands into Intune, SCCM/ConfigMgr task sequences, or third-party RMM tools to ensure consistency.
• Validate before feature upgrades: build checks into update pipelines so machines without the reserve have a gating rule (e.g., require a minimum free-space threshold or temporary re-enable step).
• Imaging caveat: some installers or setup passes can reintroduce the reserve; consider applying a registry-based tweak during specialize pass if your imaging process requires it.

---

Quick, safe checklist for reclaiming storage​

• Confirm current state:
• dism /Online /Get-ReservedStorageState
• Backup critical data and create a system restore point (recommended).
• Free space proactively:
• Run Disk Cleanup, Storage Sense, and uninstall unneeded apps language packs.
• Disable Reserved Storage:
• dism /Online /Set-ReservedStorageState /Stateisabled
• or Set-WindowsReservedStorageState -State Disabled
• Reboot and allow Windows to complete background maintenance.
• Verify:
• dism /Online /Get-ReservedStorageState
• Check Storage → System & reserved for the new reserved size.
• For major updates:
• Ensure at least 10–20 GB free, or re-enable the reserve prior to the update.

---

Practical examples and common troubleshooting​

• If DISM reports the option “unknown” or returns Error 87, check that you’re on a Windows build that includes the DISM reserved storage management parameters. Some very old builds do not support them.
• If the command fails because of "This operation is not supported when reserved storage is in use," wait for any Windows Update or servicing operations to complete and retry.
• If you disable via PowerShell/DISM but the reserve reappears after imaging or during OOBE, consider applying the registry keys in the specialize pass or handle as part of your image customization routine.
• If you disable and then experience update issues, re-enable the reserve with the same commands or ensure sufficient free space before attempting the update again.

---

Conclusion​

Reserved Storage is a sensible, Microsoft-supported mechanism that improves update reliability, particularly on disk-constrained devices. For the average user it works quietly in the background and prevents headaches with failed updates. For power users, laptop owners with small SSDs, or IT professionals managing tight images, disabling Reserved Storage is a valid and supported option — but it brings responsibility.
Disabling will often reclaim between 3–7 GB of usable space, though the exact amount and timing vary by device and configuration. The safest approach is to treat disabling as one tool among several: prefer removing optional features and language packs first, use Storage Sense and cloud offload, and if you do disable the reserve, build safeguards into your update process so feature updates never run without enough free space. For administrators, script the check-and-disable flow, include verification, and gate major updates behind free-space checks.
The trade-off is clear: more usable space now, but more effort to guarantee smooth updates later. For environments where storage is a premium and update schedules are controlled, disabling Reserved Storage is a pragmatic, supported tweak. For broad consumer deployments, the defensive value of Reserved Storage often outweighs the potential space gain.

---

Source: WebProNews Disable Windows 11 Reserved Storage to Reclaim 7GB Space

 

[ChatGPT]

Windows 11’s built‑in Reserved Storage quietly ties up several gigabytes on the system drive to make updates and system maintenance more reliable — and if you’re on a cramped 128GB (or smaller) SSD, temporarily turning it off is a legitimate, supported way to reclaim space fast, provided you understand the trade‑offs and re‑enable it before attempting major feature updates. (techcommunity.microsoft.com)

Background / Overview​

Reserved Storage (sometimes called Storage Reserve or Reserved Storage) was introduced to Windows as an engineering fix: updates and servicing tasks historically failed or stalled on systems with little free disk space. The mechanism reserves a portion of the OS volume so Windows always has some guaranteed working space for update staging, temporary installer files, and system caches. That design reduces the chance of interrupted upgrades and the difficult repairs that can follow. (techcommunity.microsoft.com)
On new installs Microsoft targeted roughly a 7GB baseline for the reserve, but the actual amount is dynamic: on very small drives Windows may allocate less initially (reports and documentation show figures as low as ~3GB or a small percentage of the system volume), and the reserve can grow or shrink depending on optional features, language packs, and available free space. That variability explains why different machines reclaim different amounts when the feature is disabled.
Reserved Storage is intended to be transparent for most users: when free space is plentiful it simply acts as a buffer. But on budget laptops with 64GB–256GB storage, the allocation can feel punishing — and that’s why reputable guides and community reports recommend using the supported commands to toggle the feature only as a temporary measure when every gigabyte counts. (thewindowsclub.com)

---

What Reserved Storage actually contains​

Reserved Storage is not a separate partition; it’s an OS‑managed allocation on the system (C volume that Windows uses for:

• Windows update staging and temporary working space during servicing.
• System temporary files and platform caches used by the OS.
• Maintenance data for optional features and language packs.

This pool is multi‑purpose: when updates aren’t being staged it can hold temporary data for apps and the platform, so it doesn’t sit entirely idle. Because of that multi‑use behavior, the precise “free” space regained after disabling the reserve will vary by system and may change over time.

---

How to check if Reserved Storage is enabled​

There are two simple ways to verify the feature’s status and size.

Quick GUI check​

• Open Settings → System → Storage.
• Click Show more categories (if present).
• Select System & reserved (or System and reserved). The Reserved storage entry shows how many gigabytes Windows has allocated.

Command‑line check (recommended for precise state)​

• In an elevated Command Prompt: dism /Online /Get-ReservedStorageState
• In an elevated PowerShell session: Get-WindowsReservedStorageState

Both report whether Reserved Storage is Enabled or Disabled for the running Windows image. These commands are documented by Microsoft and intended for administrators and power users. (techcommunity.microsoft.com)

---

How to safely disable (and re‑enable) Reserved Storage​

Disabling Reserved Storage is supported by Microsoft via DISM and PowerShell. It requires Administrator privileges and should be treated as a temporary, controlled action.

Pre‑flight checklist (do this first)​

• Install all pending Windows updates and reboot. Attempting to change the state while servicing is in progress will often fail with errors like “This operation is not supported when reserved storage is in use.”
• Run Storage Sense or Disk Cleanup to remove obvious junk (temporary files, previous Windows installations). This reduces the chance you’ll still face update problems after turning the reserve off.
• Make a restore point or a full backup if the machine is important to your workflow. Disabling the reserve increases the risk that updates may fail if free space is insufficient during servicing.

Commands — exact, supported methods​

• Open PowerShell as Administrator (Right‑click Start → Windows Terminal (Admin) or search PowerShell → Run as administrator).
• Check current state:
• PowerShell: Get-WindowsReservedStorageState
• Or Command Prompt: dism /Online /Get-ReservedStorageState. (techcommunity.microsoft.com)
• To disable:
• PowerShell: Set-WindowsReservedStorageState -State Disabled
• Or: dism /Online /Set-ReservedStorageState /Stateisabled. (thewindowsclub.com)
• Reboot and verify the state with the Get/ DISM query again. In many cases you’ll see several gigabytes of free space return after the change completes and any background maintenance finishes.

To re‑enable Reserved Storage​

• PowerShell: Set-WindowsReservedStorageState -State Enabled
• Or: dism /Online /Set-ReservedStorageState /State:Enabled. (techcommunity.microsoft.com)

Notes:

• Some systems will reallocate the reserve only after a reboot or after Windows runs background servicing tasks. The visible free-space change may not be instantaneous.
• If DISM returns “Error 87” on older builds, or the Set‑ReservedStorageState parameter is unknown, the OS build may not support the DISM switch; upgrade Windows first or use supported management routines.

---

Realistic expectations: how much space will you get?​

• Microsoft originally targeted about 7 GB as a baseline on new installs, but real‑world reclaimable space often ranges from about 3GB to 7GB, depending on optional features, language packs, and how the system currently uses the reserved pool. Expect variability; don’t count on an exact number.
• The Pocket‑lint guidance that suggests re‑enabling the feature once you have at least 5GB free is pragmatic but not an official Microsoft threshold; for feature updates and major servicing operations many admins recommend 10–20GB of free space to be safe. Treat the 5GB figure as a short‑term minimum for smaller patches and a reminder to re‑enable the reserve promptly. Any specific “minimum” is advisory rather than an absolute guarantee.

---

Troubleshooting common errors​

• “This operation is not supported when reserved storage is in use.”
• Fix: Finish pending updates, reboot, and retry. Clear temporary files first; a running servicing operation or a queued update can block the change.
• DISM Error 87 / “unknown option”
• Fix: Confirm Windows build supports the ReservedStorage parameters (Windows 10 v2004+ / modern Windows 11 builds). If the option is missing, update Windows or use a supported management flow.
• Reserve reappears after imaging or specialization
• Explanation: Some imaging or OEM setup processes reintroduce the reserve; enterprise imaging workflows sometimes require setting registry keys during the specialize pass to persist the chosen state. Use scripted DISM/PowerShell steps in your provisioning tasks as required.

---

Safer alternatives to disabling Reserved Storage​

For most users the following steps will reclaim space without removing the OS safety net:

• OneDrive Files On‑Demand: Move media and documents to OneDrive and use Files On‑Demand to keep placeholders locally, freeing large amounts of storage without deleting files.
• Storage Sense & Disk Cleanup: Let Windows clear temporary files, previous Windows installations, and update leftovers. These tools often recover multiple gigabytes.
• Uninstall optional features and language packs: These can inflate the reserved pool; removing unused components both lowers the reserve’s work and frees space.
• Move user folders to another drive or external SSD: Offloading Documents, Downloads, Pictures, and Video folders is a durable solution. A modest external NVMe or USB‑C SSD (even 512GB) is a one‑time hardware fix that removes the need for toggling system features.

---

For IT pros: scripting, imaging, and deployment notes​

Enterprise environments should treat Reserved Storage as a policy decision, not a one‑off tweak.

• Integrate checks and toggles into deployment and update task sequences: use Get‑WindowsReservedStorageState → Set‑WindowsReservedStorageState as part of imaging or SCCM/Intune task sequences, and gate feature updates behind a free‑space check.
• Registry method for persistent behavior: some teams set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ReserveManager\ShippedWithReserves (DWORD 32‑bit) to 0 to suppress the reserve across certain setups; use caution and test thoroughly, as registry edits can be overwritten by OEM or setup processes.
• Re-enable before major updates: If you choose to keep Reserved Storage disabled during normal operations, ensure your update pipeline re‑enables it — or guarantees enough free disk space — before delivering large feature upgrades. This practice avoids costly recovery scenarios.

---

Practical, step‑by‑step checklist (safe, minimal risk)​

• Install all pending Windows updates and reboot.
• Run Storage Sense and Disk Cleanup → Clean up system files. Empty the Recycle Bin.
• Backup critical data or create a system restore point.
• Open PowerShell (Admin) and run Get‑WindowsReservedStorageState to confirm current state. (techcommunity.microsoft.com)
• Run Set‑WindowsReservedStorageState ‑State Disabled (or DISM equivalent). Reboot.
• Verify reclaimed space in Settings → Storage and confirm DISM /Online /Get‑ReservedStorageState shows Disabled.
• After completing the one‑off installation or cleanup, re‑enable with Set‑WindowsReservedStorageState ‑State Enabled (or DISM) and reboot when you have at least 5–7GB free; for major upgrades aim for 10–20GB free. Consider 5–7GB a short‑term minimum, not a guarantee.

---

Critical analysis: strengths, trade‑offs and risk assessment​

Reserved Storage is a pragmatic engineering trade: a small but deliberate reduction in available user storage in exchange for far fewer failed updates and servicing surprises. For average users on 512GB+ drives the feature is invisible and adds resilience. For users on 64GB–256GB drives the reserved allocation can meaningfully constrain day‑to‑day use, pushing them toward hacks or hardware upgrades.
Strengths

• Improves update reliability: Reduces the incidence of failed or partial updates caused by low disk space. (techcommunity.microsoft.com)
• Automatic, low‑maintenance protection: Works without user intervention and absorbs many temporary/maintenance files.

Risks and downsides

• Reduced usable capacity on small drives: The baseline target (~7GB) is material on budget laptops.
• No fine‑grained user control: Windows exposes the reserve size but not a simple in‑UI dial to adjust it — toggling requires admin commands.
• Potential for update failure if left disabled: Disabling the reserve removes that safety net; updates may fail if free space is insufficient. Administrators must plan around this.

Bottom line: disabling Reserved Storage is a valid, supported tool in the toolbox — useful for short‑term emergencies and tightly provisioned deployment images — but it must be used responsibly. Where possible, choose safer alternatives (cloud offload, Storage Sense, external SSD) before removing a system reliability feature.

---

Quick decision guide (who should disable it and when)​

• Disable Reserved Storage if:
• The device has a very small system drive (64–256GB) and you urgently need space to install a required app or complete a task, and you can re‑enable the reserve before the next major update.
• The machine is non‑critical (test systems, VDI templates, disposable devices) and updates are manually managed.
• Leave it enabled if:
• The device is mission‑critical or managed in a production environment where unattended updates must succeed without manual intervention.
• You have enough storage (≥256–512GB) and prefer the hands‑off protection.

---

Final recommendations​

• Treat disabling Reserved Storage as a short‑term, targeted action. Re‑enable it as soon as practical.
• If storage is chronically constrained, invest in an external SSD or increase cloud storage rather than relying on toggling system features — hardware upgrades are often cheaper and more reliable in the long run.
• Document any change in managed environments and automate checks so devices are not left unprotected at the time of a big feature update. Use DISM/PowerShell commands in scripted workflows and gate updates on free‑space checks.

Reserved Storage exists to avoid a familiar class of Windows failures. For power users and IT pros it is a reversible, supported lever that can reclaim a few gigabytes when every byte matters — but the convenience of extra space comes with a responsibility to manage updates and system maintenance deliberately. (techcommunity.microsoft.com)

---

Source: Pocket-lint How I clear up gigabytes of PC storage with one Windows 11 setting