Enable write caching on internal drives when you have backups and reliable power. Leave it off for removable drives, unstable power situations, or systems where you cannot tolerate losing recent writes. To check or change the setting for a specific drive, open Device Manager, expand Disk drives, right-click the drive, and go to Properties, then Policies.
TL;DR:
- Enabling write caching on internal drives can significantly improve performance if the system has a recent backup and a stable power source, especially with battery-backed controllers.
- Disabling write caching is advisable for removable drives, unstable power environments, or workloads requiring guaranteed data integrity, as it prevents data loss during power failures.
- External drives with the default quick removal policy disable caching, which reduces speed but allows safe unplugging without data risk, unlike the better performance setting requiring safe removal.
- Hardware limitations such as RAID controllers, OEM drivers, or some NVMe devices may prevent changing the write caching setting, defaulting these drives to write-through mode for safety.
- Regular backups and manual flush checks are recommended before enabling caching on system or sensitive drives to prevent potential data loss from write failures.
Table of Contents
- What write caching does to your data before it hits the disk
- Should you enable write caching? a short decision checklist
- Step-by-step: enable or disable write caching per drive
- External drives and removal policy: quick removal vs better performance
- Risks and safeguards: UPS, batteries, and flush support
- Troubleshooting: missing Policies tab and driver limits
- Why reversible tweaks matter more than aggressive ones
- Let Tempered handle the diagnosis for you
- Primary Microsoft documentation and authoritative references
- FAQ
What write caching does to your data before it hits the disk
Write-back caching lets Windows report a write as complete before the data physically lands on the disk. The operating system holds the data in memory temporarily, then flushes it to the drive later, in bulk, which is faster than writing each request immediately. Write-through caching skips that shortcut: nothing is marked "done" until it is actually on the disk.
The difference matters because a write-back cache is volatile. If power drops before the flush happens, that data is gone even though an application was told the write succeeded.
- Write-back: fast, but data sits in memory until flushed
- Write-through: slower, but nothing is lost between acknowledgment and disk
- Volatile cache: cleared on power loss unless the device has its own backup power
Some hardware changes this equation. A battery-backed RAID controller or an NVMe device with nonvolatile cache can preserve cached writes through a power failure, which makes the Windows-level setting far less risky, or even irrelevant, on that specific hardware.
Should you enable write caching? a short decision checklist
Enabling write caching is a reasonable trade on internal drives handling everyday tasks: browsing, document editing, most games. It becomes a stronger case when the system sits behind a UPS, uses a battery-backed controller, or the drive itself has proven reliable over time. It is a weaker case on removable drives you might unplug without warning, on machines with flaky power, or for workloads like databases and financial software where a lost write actually breaks something.
Run through this before toggling the setting on any drive:
- Is the drive internal and permanently connected, or removable?
- Do you have a current backup or system image?
- Is your power supply stable, or backed by a UPS?
- Does the workload require guaranteed writes (databases, critical logs)?
- Has the drive or controller shown any signs of instability?
If you answered "removable," "no backup," or "unstable power" to any of these, leave caching off until that changes.
Pro Tip: Take a system image or file backup before changing the cache policy on your boot drive, since a bad flush during a crash is the one scenario this setting actually controls.
Step-by-step: enable or disable write caching per drive
The setting lives in Device Manager and applies to one physical drive at a time, not the whole system. According to Microsoft's guidance on write caching, the process is the same for enabling or disabling it.
- Open Device Manager (right-click the Start button and select it, or search for it).
- Expand Disk drives.
- Right-click the physical drive you want to change and select Properties.
- Open the Policies tab.
- Check or uncheck Enable write caching on the device.
- Click OK.
A few things to expect afterward:
- You will not usually need to restart. Only do so if Windows explicitly asks.
- The checkbox affects only the drive you selected, so a multi-drive system needs each drive set individually.
- Some devices will not show the checkbox at all. RAID arrays, certain virtualized storage controllers, and some OEM drivers do not expose this property to Windows.
- For external drives, also check Safe Removal behavior before relying on cached writes, covered next.
External drives and removal policy: quick removal vs better performance
External drives have their own layer on top of the write-cache checkbox: the removal policy. Windows defaults removable media to Quick removal, which avoids caching so you can unplug the drive without a formal eject step. Switching to Better performance allows write caching on that device, which speeds up transfers but means you must use Safely Remove Hardware every time, or risk losing data still sitting in memory.
To change it: open the drive's Properties in Device Manager, go to the Policies tab, and pick the removal policy that fits how you use the device.
- Quick removal: safer default, no eject step needed, slower for heavy transfers
- Better performance: faster, but requires Safely Remove Hardware before unplugging
- Safe-eject workflow: click the Safely Remove Hardware icon in the system tray, select the device, wait for the confirmation, then disconnect
Risks and safeguards: UPS, batteries, and flush support
A UPS or a battery-backed controller changes the practical risk of write-back caching by giving the system time to flush pending writes during a power event instead of losing them outright. Without that protection, the risk sits entirely on the volatile cache clearing before the data reaches the disk.
Flush and sync commands are the mechanism that actually gets cached data onto the disk. Windows tools like Write-VolumeCache trigger this manually, and the write cache property documentation explains that not every device exposes or honors these commands the same way. Microsoft also notes that disabling the cache lowers data-loss risk but carries very significant performance consequences for all I/O on that device, so it is not a setting to flip casually.
- Confirm you have a recent backup before enabling caching on a system disk.
- Run a manual flush and watch for errors or delays that suggest the device is struggling to commit data.
- Check the System log periodically for warnings tied to delayed writes.
Event ID 50 is worth watching for: it appears when Windows' Cache Manager reports a write as successful and later fails to commit it to disk, which is the exact failure mode write-back caching introduces.
Troubleshooting: missing Policies tab and driver limits
If the Policies tab or the write-cache checkbox is missing, the most common causes are RAID configurations, virtualized storage controllers, OEM drivers that do not expose the property, and some NVMe or flash devices that manage caching internally without giving Windows a toggle.
- Check whether the drive sits behind a RAID controller. Use a RAID calculator to confirm your array type if you are unsure how it is configured.
- Update the storage driver from the manufacturer's site rather than relying on the generic Windows driver, which sometimes hides vendor-specific settings.
- Consult the controller or SSD vendor's documentation for its own cache and persistence settings, since some devices manage this outside of Windows entirely.
- If none of that surfaces the option, treat the device as write-through by default and do not assume caching is active.
Why reversible tweaks matter more than aggressive ones
Write caching is a real performance lever, but it is also one of the few Windows settings that trades a small amount of risk for speed instead of being a pure win. We think the right approach is the same one we apply to any system tweak: understand what changes, confirm you can undo it, and only touch settings whose trade-offs you actually accept.
— Ian
Let Tempered handle the diagnosis for you
Figuring out which drive settings are worth changing takes time most people do not have, and guessing wrong on a system disk is not a good way to learn. Tempered scans your live hardware, including disk, CPU, RAM, and GPU metrics, and tells you in plain language what is actually limiting your PC and what changing it would do.
- Every suggested change comes with a clear explanation of the expected outcome before you approve it.
- Nothing gets applied without your approval, and every change carries a one-click undo path.
- The free tier gives you a limited number of AI scans to see how it works, and Torque and Torque Max unlock unlimited scans and premium features.
Check your PC's diagnostics with Tempered and see what your system is actually capable of.
Primary Microsoft documentation and authoritative references
The Device Manager steps, removal policy defaults, write-cache property behavior, and Event ID 50 details above come directly from Microsoft's own documentation, linked throughout this guide for anyone who wants the technical detail behind each setting.
FAQ
Should write caching be enabled?
Write caching is worth enabling on internal drives when you have backups, stable power, and a workload that can tolerate a rare lost write, since it improves throughput noticeably. Leave it disabled on removable drives or systems without reliable power, where a lost write matters more than the speed gain.
What happens if I disable the cache?
Disabling write caching forces every write to complete on the physical disk before Windows reports it as done, which removes the risk of losing acknowledged data during a power failure. Microsoft notes this has significant performance consequences for all I/O on that device, so expect slower file operations in exchange for the added safety.
Should my SSD have cache?
Most SSDs use a volatile write cache by default because it speeds up everyday use, and this is generally fine on an internal drive with stable power and backups. Enterprise SSDs or controllers with nonvolatile or battery-backed cache remove much of the power-loss risk entirely, making the Windows-level setting less critical on that hardware.
What is write caching on an SSD?
Write caching on an SSD lets the drive or the operating system briefly hold incoming writes in fast, volatile memory before committing them to the flash storage itself. This speeds up write operations but means anything still in that cache during a sudden power loss can be lost, which is why Microsoft ties the setting to back up and power reliability rather than treating it as a free performance gain.