If you write code, build projects or run Python-based local AI tools on your PC, Windows 11 has a feature you may have missed: Dev Drive. It's a special kind of storage volume that Microsoft designed to improve performance for developer workloads, using the ReFS file system and a lighter-touch Microsoft Defender scanning mode.
Forge PC hasn't measured Dev Drive performance for this guide. Everything below follows Microsoft's Dev Drive documentation, which links to Microsoft's own performance measurements if you want numbers.
What is a Dev Drive?
Microsoft describes Dev Drive as a form of storage volume built on ReFS (Resilient File System) that uses targeted file system optimisations for development, plus more control over volume settings and security. Two things make it different from a normal NTFS drive:
ReFS optimisations. Microsoft says ReFS contains several optimisations for key developer scenarios.
Defender performance mode. Dev Drives are marked as trusted when created, which tells Microsoft Defender Antivirus to run in performance mode on that drive. Microsoft says this balances threat protection and performance, while real-time protection stays on for all your other drives.
Who should use one (and who shouldn't)
Microsoft says Dev Drive is intended for:
source code repositories and project files
package caches (Microsoft gives examples including npm, NuGet, vcpkg, pip, Cargo, Maven and Gradle)
build output and intermediate files
Microsoft says developer tools themselves, such as Visual Studio, MSBuild, the .NET SDK and Windows SDK, should stay on your C: drive. Microsoft also warns that Dev Drive is "intended only for key developer scenarios". It isn't a gaming feature, so don't move your Steam library onto one expecting faster loading.
It's a sensible fit if you build software, or if you run Python-based local AI projects and want your code and pip cache on a Dev Drive. If you never touch a terminal, you can skip it.
What you need
Microsoft lists these prerequisites:
Windows 11, build 10.0.22621.2338 or later (check Windows Update)
16GB of memory recommended, 8GB minimum
at least 50GB of free space (the minimum Dev Drive size)
local administrator permissions
Dev Drive is available on all Windows editions. On a work PC, your IT team may need to enable it through security policy. You also can't make your C: drive a Dev Drive, and existing volumes can't be converted: a Dev Drive has to be newly formatted.
How to create a Dev Drive in Settings
Open Settings > System > Storage > Advanced storage settings > Disks & volumes.
Select Create dev drive.
Choose where it will live:
Create new VHD: builds the Dev Drive inside a virtual hard disk file on an existing drive. Microsoft recommends the VHDX format and a dynamically expanding disk, and suggests storing it in a per-user folder.
Resize an existing volume: shrinks a partition to make at least 50GB of unallocated space for the new volume.
Unallocated space on disk: only appears if you already have unallocated space.
Give it a label and drive letter, set the size, and select Format.
Microsoft says a partition generally offers faster performance because it uses the disk directly, while a VHD may be slightly slower but is easier to resize, move or back up. Resizing partitions is riskier, so back up first; our guide to backing up Windows 11 covers the built-in options.
How to create one from the command line
Microsoft also documents two commands, both of which need an administrator terminal and format the target drive (erasing it):
Replace D with the correct drive letter, and double-check it before you press Enter.
Check (or set) trust
To check whether a Dev Drive is trusted, open an administrator terminal and run fsutil devdrv query D:. To mark it as trusted, run fsutil devdrv trust D:. Microsoft says a Dev Drive moved to another PC is treated as an ordinary volume until it's trusted again, and advises caution when designating trust after the drive was first created. Performance mode also needs Microsoft Defender real-time protection switched on. For more on Defender, see our Microsoft Defender vs paid antivirus comparison.
Moving your caches
Once the drive exists, point your tools' caches at it. Microsoft's documentation gives examples, such as setting a system environment variable for vcpkg's binary cache, and similar steps for pip, npm, Cargo, Maven and Gradle. Restart open terminals (or reboot) after changing environment variables. If you work in Linux, note that WSL keeps its own files; our WSL 2 local AI guide covers that set-up.
Our verdict
Dev Drive is a ReFS-formatted volume with Microsoft Defender performance mode, designed for source code, package caches and build output, not games or everyday files. If you code or run Python-based AI projects, create one in Settings > System > Storage > Advanced storage settings > Disks & volumes > Create dev drive, ideally as a dynamically expanding VHDX, with at least 50GB. Keep developer tools on C:, and use fsutil devdrv query to confirm it's trusted. Forge PC hasn't measured Dev Drive performance; the steps follow Microsoft's documentation.