What Is Dev Drive on Windows 11 and Who Benefits

What a Dev Drive actually is

A Dev Drive is a separate volume formatted with ReFS and tuned for developer workloads, shipped with Windows 11 23H2. You create it in Settings → System → Storage → Advanced storage settings → Disks & volumes, from unallocated space or a VHD/VHDX file, with a 50 GB minimum size. The headline feature is performance-mode antivirus: on a volume you explicitly mark as trusted, Defender checks files against known-malicious signatures synchronously and does the heavy scanning in the background, so opening ten thousand files in node_modules stops feeling like wading through mud.

ReFS itself brings copy-on-write and cheap block cloning, which is why the workloads that hurt most on NTFS — git checkouts, npm and pnpm installs, incremental builds — benefit first: they are thousands of small file operations, exactly what Dev Drive makes cheaper. Microsoft claims up to 30 percent faster file operations in typical dev scenarios, and that number passes the smell test on a big dependency install. The honest footnote: those are I/O-bound build tasks, not games, browsing or boot times.

Who benefits — and who should not bother

The short answer: people whose daily work is compiling, packaging or checking out large source trees. If your heaviest software is a game launcher or a spreadsheet, Dev Drive does nothing for you, and the 50 GB it demands are better spent on the games themselves. It also cannot host Windows — it is a data volume only, so there is no moving the OS onto it.

Trust deserves a paragraph of its own. During creation you mark the volume as trusted, and that is what enables the async antivirus mode; a file arriving from an untrusted source — a browser download carrying the mark-of-the-web — still gets scanned before opening. The fastest way to waste the benefit is to treat the volume as a magic partition: syncing it to cloud storage or stacking third-party filter drivers on top brings back the overhead Dev Drive was supposed to remove. Keep it a plain, dedicated work volume and it behaves.

• Fits: front-end, .NET, Rust and C++ developers with huge dependency trees and constant rebuilds
• Fits: Windows CI runners and build agents doing clean checkouts all day
• Requires: Windows 11 23H2 or newer, at least 50 GB free, admin rights to create the volume
• Best on a separate fast NVMe SSD, not squeezed onto the OS drive as a partition
• Not for games: load times will not change, and some launchers dislike the corners of ReFS
• Not for everyday apps: browsers, Office and media see zero difference in practice

What it will not fix

Dev Drive is not a general speed upgrade and not a RAM disk. Your IDE, compiler and browser run exactly as before; only the file operations underneath them get cheaper. If the build is slow because of CPU or cold caches, a faster volume changes little; a `git status` that took eight seconds on a huge repo is exactly the kind of pain that shrinks. And if you were manually excluding your projects folder from Defender to make installs bearable — stop; that habit is precisely what Dev Drive replaces, without the security hole.

Questions and Answers

Read next