Unlocking the Speed: Windows Server 2025 Delivers 80% IOPS Boost with New Native NVMe Stack
As early as the spring of 2024, Microsoft promised a substantial performance boost for Windows Server 2025 on modern NVMe storage, even citing a concrete figure: up to a 70 percent increase in IOPS compared with Windows Server 2022. At the time, this sounded like one of those rare cases where “storage subsystem optimization” translated into something more than marketing rhetoric—into a genuinely measurable gain. Eighteen months later, the company has now officially confirmed that native NVMe support has indeed arrived in Windows Server 2025.
The feature became available once Windows Server 2025 reached general availability and was delivered via the October 2025 Patch Tuesday update (KB5066835). One important caveat remains: it is currently opt-in. The functionality is disabled by default, requiring administrators to enable it manually.
Notably, Microsoft has raised the bar on its original promises. While the roadmap initially referenced roughly a 70 percent IOPS uplift, the company now speaks of an improvement closer to 80 percent—an increase of ten percentage points over earlier claims. In addition, Microsoft cites approximately 45 percent savings in CPU cycles per I/O operation in 4K random read scenarios on NTFS volumes. In other words, the gains extend beyond raw throughput to include a meaningful reduction in the processor overhead consumed by disk access itself.
The underlying explanation is surprisingly straightforward. Historically, Windows has built much of its storage stack around the SCSI model, an approach originally designed for spinning hard drives. With Windows Server 2025, the system no longer attempts to treat all storage devices as SCSI by default. For NVMe, this translates into a far more direct path to the hardware’s capabilities. In Microsoft’s own terms, native NVMe enables true multi-queue access, eliminates unnecessary synchronization and locking within the kernel I/O path, reduces latency, and offloads the CPU—leaving more resources available for application workloads.
The rollout is deliberately designed to give administrators room to assess both impact and risk within their own environments. Microsoft provides two activation paths: via the registry or through Group Policy. The registry method involves a PowerShell command that adds a key under FeatureManagement Overrides, after which the system begins using the native NVMe stack. Alternatively, administrators can deploy an MSI policy package and enable the corresponding setting through the Local Group Policy Editor.
One particularly intriguing aside in Microsoft’s documentation is the observation that, thanks to the NVMe 2.0 specification, NVMe can theoretically apply not only to SSDs but also to HDDs. In practice, however, the real significance of this change for Windows Server 2025 lies squarely in unlocking the full potential of NVMe SSDs in server workloads.
Given that Windows Server 2025 and Windows 11 24H2 share a closely aligned codebase—and that Windows 11 25H2 is reportedly continuing along the same servicing branch—a natural question arises: could similar storage subsystem improvements eventually matter for desktop Windows as well? Microsoft has made no explicit promises, but the broader logic of platform unification suggests that such optimizations may gradually find their way into client builds. If they do, the impact could be especially compelling for heavy I/O workloads and gaming scenarios.
Support Our Threat Intelligence
If you find our technology report and cybersecurity news helpful, consider supporting our work.
Buy Me a Coffee
PayPal
