Blog Post

Screenshot of higher IOPS when running Native NVMe stack on Windows Server 2025.
Windows Server News and Best Practices
5 MIN READ

Announcing Native NVMe in Windows Server 2025: Ushering in a New Era of Storage Performance

Yash_Shekar's avatar
Yash_Shekar
Icon for Microsoft rankMicrosoft
Dec 15, 2025

Native NVMe support in Windows Server 2025 is a leap forward in storage innovation that will redefine what’s possible for your most demanding workloads. Enable Native NVMe today using a registry key after applying October’s latest cumulative update for WS2025!

We’re thrilled to announce the arrival of Native NVMe support in Windows Server 2025—a leap forward in storage innovation that will redefine what’s possible for your most demanding workloads. Modern NVMe (Non-Volatile Memory Express) SSDs now operate more efficiently with Windows Server. This improvement comes from a redesigned Windows storage stack that no longer treats all storage devices as SCSI (Small Computer System Interface) devices—a method traditionally used for older, slower drives. By eliminating the need to convert NVMe commands into SCSI commands, Windows Server reduces processing overhead and latency. Additionally, the whole I/O processing workflow is redesigned for extreme performance. This release is the result of close collaboration between our engineering teams and hardware partners, and it serves as a cornerstone in modernizing our storage stack. 

Native NVMe is now generally available (GA) with an opt-in model (disabled by default as of October’s latest cumulative update for WS2025). Switch onto Native NVMe as soon as possible or you are leaving performance gains on the table! Stay tuned for more updates from our team as we transition to a dramatically faster, more efficient storage future.

Why Native NVMe and why now?

Modern NVMe devices—like PCIe Gen5 enterprise SSDs capable of 3.3 million IOPS, or HBAs delivering over 10 million IOPS on a single disk—are pushing the boundaries of what storage can do. SCSI-based I/O processing can’t keep up because it uses a single-queue model, originally designed for rotational disks, where protocols like SATA support just one queue with up to 32 commands. In contrast, NVMe was designed from the ground up for flash storage and supports up to 64,000 queues, with each queue capable of handling up to 64,000 commands simultaneously.

With Native NVMe in Windows Server 2025, the storage stack is purpose-built for modern hardware—eliminating translation layers and legacy constraints. Here’s what that means for you:

  • Massive IOPS Gains: Direct, multi-queue access to NVMe devices means you can finally reach the true limits of your hardware.
  • Lower Latency: Traditional SCSI-based stacks rely on shared locks and synchronization mechanisms in the kernel I/O path to manage resources. Native NVMe enables streamlined, lock-free I/O paths that slash round-trip times for every operation.
  • CPU Efficiency: A leaner, optimized stack frees up compute for your workloads instead of storage overhead.
  • Future-Ready Features: Native support for advanced NVMe capabilities like multi-queue and direct submission ensures you’re ready for next-gen storage innovation.

Performance Data

Graph showing IOPS gains on WS2025 (with Native NVMe) compared to WS2022 on 1, 8, and 16-threaded 4K random read tests using an NTFS-formatted volume.Graph showing reduction in CPU cycles per I/O on WS2025 (with Native NVMe) compared to WS2022 on 8 and 16-threaded 4K random read tests using an NTFS-formatted volume.

Using DiskSpd.exe, basic performance testing shows that with Native NVMe enabled, WS2025 systems can deliver up to ~80% more IOPS and a ~45% savings in CPU cycles per I/O on 4K random read workloads on NTFS volumes when compared to WS2022. This test ran on a host with Intel Dual Socket CPU (208 logical processors, 128GB RAM) and a Solidigm SB5PH27X038T 3.5TB NVMe device. The test can be recreated by running "diskspd.exe -b4k -r -Su –t8 -L -o32 -W10 -d30" and modifying the parameters as desired. Results may vary.

Top Use Cases: Where You’ll See the Difference

Try Native NVMe on servers running your enterprise applications. These gains are not just for synthetic benchmarks—they translate directly to faster database transactions, quicker VM operations, and more responsive file and analytics workloads.

  • SQL Server and OLTP: Shorter transaction times, higher IOPS, and lower tail latency under mixed read/write workloads.
  • Hyper‑V and virtualization: Faster VM boot, checkpoint operations, and live migration with reduced storage contention.
  • High‑performance file servers: Faster large‑file reads/writes and quicker metadata operations (copy, backup, restore).
  • AI/ML and analytics: Low‑latency access to large datasets and faster ETL, shuffle, and cache/scratch I/O.

How to Get Started

  1. Check your hardware: Ensure you have NVMe-capable devices that are currently using the Windows NVMe driver (StorNVMe.sys). Note that some NVMe device vendors provide their own drivers, so unless using the in-box Windows NVMe driver, you will not notice any differences.
  2. Enable Native NVMe: After applying the 2510-B Latest Cumulative Update (or most recent), add the registry key with the following PowerShell command: 
    reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 1176759950 /t REG_DWORD /d 1 /f
    Alternatively, use this Group Policy MSI to add the policy that controls the feature then run the local Group Policy Editor to enable the policy (found under Local Computer Policy > Computer Configuration > Administrative Templates > KB5066835 251014_21251 Feature Preview > Windows 11, version 24H2, 25H2). Once Native NVMe is enabled, open Device Manager and ensure that all attached NVMe devices are displayed under the “Storage disks” section. Screenshot of Device Manager where NVMe devices show up under the Storage disks section.
  3. Monitor and Validate: Use Performance Monitor and Windows Admin Center to see the gains for yourself. Or try DiskSpd.exe yourself to measure microbenchmarks in your own environment! A quick way to measure IOPS in Performance Monitor is to set up a histogram chart and add a counter for Physical Disk>Disk Transfers/sec (where the selected instance is a drive that corresponds to one of your attached NVMe devices) then run a synthetic workload with DiskSpd. Compare the numbers before and after enabling Native NVMe to see the realized difference in your real environment!

Screenshot of Performance Monitor, showing how to add a counter for Disk Transfers/sec to measure IOPS of an NVMe drive.Screenshot of higher IOPS when running Native NVMe stack on Windows Server 2025.

Join the Storage Revolution

This is more than just a feature—it’s a new foundation for Windows Server storage, built for the future. We can’t wait for you to experience the difference.

Share your feedback, ask questions, and join the conversation. Let’s build the future of high-performance Windows Server storage together. Send us your feedback or questions at nativenvme@microsoft.com!


Yash Shekar (and the Windows Server team)

Updated Dec 15, 2025
Version 1.0

1 Comment

  • Hi Yash! Why do you compare with WS2022? Please, show us a comparison with WS2025 w/o this feature enabled.