Microsoft’s Dev Drive feature in Windows 11 has recently been pitched as a surprise gaming performance booster by PCWorld, but the claim deserves a closer look. Dev Drive is a specialized storage volume built on the Resilient File System (ReFS) and tuned for developer workloads—specifically, compiling and building source code, which involves handling thousands of small files. The argument now is that those same optimizations can accelerate game load times and in-game asset streaming, because modern games also juggle directories full of tiny configuration files, shader caches, and texture assets. While there’s a kernel of truth here, the real-world impact on gaming is far from the universal speedup that hype might suggest.

What is Dev Drive, exactly?

Dev Drive arrived in Windows 11 with the 23H2 update (build 22631) as a performance-focused volume created on a dedicated virtual hard disk (VHD/VHDX) or a physical drive partition. It’s not a file system you apply to your existing C: drive; instead, you allocate a chunk of storage—ideally 50 GB or more—and format it with ReFS. The magic is in the default settings: Windows disables content indexing, eliminates the Last Access Time update, and turns off any filesystem filter drivers that aren’t absolutely necessary. Most importantly, the anti-malware scanning performed by Microsoft Defender is set to “performance mode,” which delays real-time checks so that small-file operations don’t get bogged down by continuous security inspections.

Under the hood, ReFS gives Dev Drive a different structural backbone than the NTFS volumes most users know. ReFS was originally designed for resilience and data integrity, but for Dev Drive, Microsoft turns off those integrity checks (the “integrity streams”) to remove write-costly metadata operations. Combined with the filter driver changes, Dev Drive can achieve significantly lower per-file overhead—exactly what a developer needs when running a build tool that touches 10,000 files in 30 seconds. The question is whether that translates to games, which also do plenty of small-file I/O, albeit in a different pattern.

The PCWorld argument: small-file speed for games

PCWorld published benchmarks showing that certain games ran faster when installed on a Dev Drive volume. The cited reason is that games like “Horizon Zero Dawn” or “Cyberpunk 2077” contain thousands of tiny files—configuration scripts, localization strings, shader bytecode, and mesh LOD data—and the ReFS-based Dev Drive reduces the overhead of opening them. In theory, when a game engine streams assets on the fly, fewer filesystem bottlenecks mean quicker access, lower CPU usage during I/O, and potentially smoother performance. The idea is that the same optimizations that make “make” or “MSBuild” fly will also give your games a lift.

But here’s the catch: gaming I/O is dominated by reading large, compressed archive files—think “data.pak” or “textures.bin.” Modern engines rarely open individual loose files during gameplay; they pre-load everything from monolithic archives to avoid exactly the small-file problem. While some legacy titles or indie projects might scatter files everywhere, the majority of AAA games are packaged. Even when shader caches are compiled at runtime, they’re typically written once and read sequentially. That limits the scenarios where Dev Drive’s small-file speed truly shines.

Benchmarks: mixed, not miraculous

PCWorld’s own numbers tell a nuanced story. In their testing, a few titles showed 5-10% shorter load times, but frame rates remained virtually unchanged. Some games even performed slightly worse, possibly due to the lack of certain optimizations that NTFS has honed over decades. For example, NTFS’s built-in compression and sparse file support, absent in ReFS, can actually boost gaming performance on slower drives by reducing the amount of I/O. Dev Drive also abandons the SuperFetch/Prefetch caching that Windows uses to anticipate frequently accessed files based on usage patterns—a feature that NTFS volumes leverage to shave seconds off boot and load times.

In independent community tests, similar results appear. A user who tries copying a 100 GB Steam library to a Dev Drive may see a load-time drop of a second or two in some games, but no difference in others. The gains are most noticeable when the game is split into thousands of individual files—for instance, a heavily modded “Skyrim” installation with 50,000 loose asset files—but even then, the improvement is marginal compared to a clean NTFS install. Real-world, you’re looking at a few percentage points at best, often within the margin of error for modern NVMe SSDs.

The security trade-off nobody talks about

Perhaps the most critical omission in the “Dev Drive for gaming” pitch is the security configuration. By turning off Microsoft Defender’s real-time scanning for the volume, you’re opening a door that malware could waltz through. Games themselves aren’t typically malware vectors, but the modding scene, cracked save files, and unofficial patches often are. If you download a mod that turns out to be a trojan and drop it onto your Dev Drive, Windows won’t scan it until it’s executed or moved elsewhere—and by then, it might be too late. The performance gain is simply not worth the elevated risk for a home environment where you’re also storing personal data, documents, and credentials on the same machine.

Additionally, ReFS volumes do not support all of Windows’ features. File History, System Restore, and some Hyper-V snapshots don’t work with ReFS. Certain backup tools can’t see the volume. If you’re a gamer who occasionally tinkers, you might find that your usual workflow—restoring a system image, migrating data, or using a cloud sync client—breaks in unexpected ways.

When might it actually help?

A legitimate use case does exist for a subset of players. If you’re a game developer or modder who frequently compiles Unreal Engine projects, works with asset pipelines, or handles thousands of loose assets in a test environment, a Dev Drive can speed up iteration times dramatically. Storing the game’s development build and its tools on the same volume means you reap the intended benefits of Dev Drive while occasionally running the game to test. In that scenario, the gaming performance boost is a happy side effect, not the primary goal.

Enthusiasts who run dedicated gaming rigs with no sensitive data could experiment without much downside, provided they understand the security gaps. But calling Dev Drive a general-purpose gaming upgrade is like calling a race car a good family hauler because it has four wheels. The optimizations are real, but they’re tailored to a narrow I/O pattern that only occasionally overlaps with gaming demands.

The bottom line for gamers

Microsoft never intended Dev Drive for gaming, and the data shows why: the file system micro-optimizations that matter in a build-chain context have a negligible impact on frame rates and load times for most commercial games. You’re better off investing in a faster NVMe SSD, ensuring your game drive is connected via a PCIe 4.0 or 5.0 link, and keeping Windows Defender on so that you don’t end up with a cryptominer masquerading as a game mod. If you’re curious, set aside a small partition, enable Dev Drive, and benchmark your own library—but don’t expect miracles. For everyone else, NTFS remains the sane, secure, and battle-tested choice for gaming on Windows 11.

As Windows evolves, we may see more of ReFS’s DNA bleed into consumer NTFS features, especially with DirectStorage already pushing the boundaries of game I/O. Until then, treat any “Dev Drive makes games faster” claims as a fun experiment rather than a recommended tweak.