Microsoft introduces "Native NVMe" driver stack

winjer

Member

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.
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.

LqyuxQlc8Ybeli1g.png
pxxLTYaTXY1dp6RG.png




To enable the feature. It also works on Windows Pro and Home. Though this is still a feature only meant for servers.
But please make sure to backup your registry first, in case something goes wrong.
It requires KB5066835 to be installed. But this was released several months ago, and most people should have it.
It also requires Windows 11 24H2 or 25H2.

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 1853569164 /t REG_DWORD /d 1 /f
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 156965516 /t REG_DWORD /d 1 /f
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 735209102 /t REG_DWORD /d 1 /f

My experience:
I didn't do proper benchmarks, just ran a few games to see if there was any difference.
With games that use Direct Storage, such as BF6, Spiderman I didn't notice any changes. With Ratchet and Clank the loading seemed faster, but could be just my impression.

But then I tested games using UE4 and 5. One thing that always happened wit these games is that due to it's streaming system, when I started running in game, performance would drop 10-15 FPS, and CPU utilization would increase a bit.
So I installed Kena, The Forbidden City, High on Life, and Talos Principle Reawakened. These are games where I had previously noticed they would drop performance whenever I started running in game.
With this driver stack, CPU utilization barely moved. And the frame rate was almost stable, only changing a bit due to the scenery moving. But not the drop in performance that UE4 and 5 games usually have.
Also, stutters were fewer. Talos Principle always ran very well. But Kena and The Forbidden City and High on Life, always had a good amount of stutters, even after shader compilation, due to asset streaming.
 
Fourteen years since NVMe was created and only now this piece of crap from Microsoft has started working natively? Without being a workaround for an old protocol? What a filthy and worthless company.

Woidla27
Copper Contributor
Dec 17, 2025


I don't know whether to laugh or cry now. It's 2025 and Microsoft is celebrating the storage revolution.

Linux Kernel supports real nvme for more than 10 years. VMware for 7 years.

Meanwhile Windows customers paied for many Windows Server versions still shipping the old inefficient legacy code.

Microsoft finally get your basics right before adding more and more useless AI stuff on top of that.
 
Last edited:
Don't forget to share your thoughts.
It would be cool having someone confirm these results.
Definitely will. Need to find a good test for it as well.

Edit: Wonder if Dead Space Remake or the Star Wars games would be a good test. Also Outlaws maybe?
 
Last edited:
I thought NVMe discs weren't suitable for server use and long-term storage because they degrade over time. Or at least, degrade over time at a much more rapid pace than traditional hard discs.
 
I thought NVMe discs weren't suitable for server use and long-term storage because they degrade over time. Or at least, degrade over time at a much more rapid pace than traditional hard discs.
If you need IO, need to use NVME. Also, Enterprise NVME have a lot more durability due type of flash memory used (SLC as an example), controllers with lots of cache, and they leave a lot of space reserved for wear and tear.
 
Last edited:
If you need IO, need to use NVME. Also, Enterprise NVME have a lot more durability due type of flash memory used (SLC as an example), controllers with lots of cache, and they leave a lot of space reserved for wear and tear.
OK, that makes sense.

When I was building a NAS a few years ago, I was warned against buying/building one that used NVMe, but that was clearly consumer-grade stuff, not Enterprise.
 
One thing I forgot to mention. Apps that monitor or upgrade an SSD, such as Samsung Magician and the like, will not work with this driver stack.
So if you think you need to do some firmware upgrade, or some other task with these types of softwares, do it before enabling the new driver.
 
One thing I forgot to mention. Apps that monitor or upgrade an SSD, such as Samsung Magician and the like, will not work with this driver stack.
So if you think you need to do some firmware upgrade, or some other task with these types of softwares, do it before enabling the new driver.
To revert to the previous state, I simply need to delete these registry keys ?
Thanks !
 
To revert to the previous state, I simply need to delete these registry keys ?
Thanks !

Yes. And don't forget to backup your registry. Or do a Restore Point.
You can also control it through the Group Policy. It's explained in the article the required steps.

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.
 
Last edited:
One thing I forgot to mention. Apps that monitor or upgrade an SSD, such as Samsung Magician and the like, will not work with this driver stack.
So if you think you need to do some firmware upgrade, or some other task with these types of softwares, do it before enabling the new driver.
Can you please explain where this driver, regarding storport.sys, volmgr.sys and mountmgr.sys fits in?

Am I correct, that this doesn't employ mountmgr.sys or volmgr.sys, because it doesn't count as a "Disk drives"-, but as a "Storage disks"-class now?
 
Last edited:
Fourteen years since NVMe was created and only now this piece of crap from Microsoft has started working natively? Without being a workaround for an old protocol? What a filthy and worthless company.

Yeah, I'm honestly trying to understand why it took this long. Have video games on PC been hurt by this NOT being native until now?

This.. I don't try it. I'm still on W11 21H2

WHAT?!?! O_O

How in the world do you guys not update for this long?
 
I straight up do not trust Microsoft to do something like this without also creating a bug which wipes everyone's drives randomly

I'll wait a year or so before enabling this feature like most new Windows features
 
Is there any down sides to enabling this on a home PC? Is it stable?

If it has been deemed safe enough to run on Microsoft powered servers, I would imagine it is stable enough for your home PC. You'd think server administrators would have been cautious about updating to the latest patch/ registry keys.

I guess Microsoft can pop a cork that their new file system has features that have been found in the APFS and EXT4 for decades now.
 
Last edited:
OK, that makes sense.

When I was building a NAS a few years ago, I was warned against buying/building one that used NVMe, but that was clearly consumer-grade stuff, not Enterprise.

The main thing you wanna check for on nvme drives is endurance, and what kind of memory they use. You typically want TLC NAND over QLC, and you can just search what drives have what. It's not that uncommon to get it with Samsung, Sandisk, WD or previously Crucial. I've used nvme drives for cache and storing docker containers on my NAS for 4 years using some budget crucial stuff, and still going strong.

Yeah, I'm honestly trying to understand why it took this long. Have video games on PC been hurt by this NOT being native until now?
I doubt until the start of this gen when consoles added SSDs, that many games were even coded to take full advantage of nvme at all, beyond what MS could do at the OS level.
 
Yeah, I'm honestly trying to understand why it took this long. Have video games on PC been hurt by this NOT being native until now?
Not really. There have been very few IO bound games so far and even those have mainly been bottlenecked by the disk controller itself rather than CPU performance or interface bandwidth. This new driver might help CPU performance in the server space but this is at much higher IO rates than any current games need.

DirectStorage already supports BypassIO anyway which also exists to reduce CPU overhead. I've yet to see it make a difference.
 
Yes. And don't forget to backup your registry. Or do a Restore Point.
You can also control it through the Group Policy. It's explained in the article the required steps.
I have ran a few quick tests on my system with Dead Space Remake, Jedi Survivor and latest Mafia.

I "think" I am seeing less stuttering in Dead Space and Jedi, but going to run some more comprehensive tests tomorrow and with more games.

So far so good basically and the gameplay feels a bit smoother.

I didn't see any difference with Mafia.

Going to check frame pacing tomorrow for more consistent results.
 
I have ran a few quick tests on my system with Dead Space Remake, Jedi Survivor and latest Mafia.

I "think" I am seeing less stuttering in Dead Space and Jedi, but going to run some more comprehensive tests tomorrow and with more games.

So far so good basically and the gameplay feels a bit smoother.

I didn't see any difference with Mafia.

Going to check frame pacing tomorrow for more consistent results.

I don't think this is going to fix stuttering from asset streaming.
It does improve latency and throughput in I/O bound scenarios, especially at 32k queues, which might help get data a bit faster, thus reducing the stutter impact a bit.
So it won't magically fix games. The thing I did notice is that CPU usage and performance was much better, when streaming assets.
 
WHAT?!?! O_O

How in the world do you guys not update for this long?


22H2 make my PC more longer (boot are more longer), break many thing (Virtualisation, Hyper-V). I don't want to make a clean install years ago.

I need to do a clean install now... But my god. Windows 25H2 is a bloat nightmare with all this AI shit. In my opinions... 21H2 is the better W11 version.

 
Last edited:
I don't think this is going to fix stuttering from asset streaming.
It does improve latency and throughput in I/O bound scenarios, especially at 32k queues, which might help get data a bit faster, thus reducing the stutter impact a bit.
So it won't magically fix games. The thing I did notice is that CPU usage and performance was much better, when streaming assets.
Ahh, good point. Will need to double check CPU utilization as well.
 
BTW, check if Directstorage BypassIO is enabled on your system.
It wasn't for some reason (24H2), enabled it. But not too many games use Directstorage still so don't see it changing much.

This wouldn't work with Vulcan since this is DX12, right?
 
It wasn't for some reason (24H2), enabled it. But not too many games use Directstorage still so don't see it changing much.

This wouldn't work with Vulcan since this is DX12, right?

Direct Storage is a part of DirectX, so I don't see it going to Vulkan.
On the other hand, there are even fewer games using Vulkan.
 
Last edited:
Top Bottom