Support NeoGAF

[dgrdsv]

And this also occurs with Windows Server. Those idiots at Microsoft didn't plan this thing through....

Yep. It's also missing an interface to performance counters and I don't think that BypassIO is supported by that new driver.
Mind boggling that a company as big as MS would produce a new driver which would just miss half of features of the current one.

 

[winjer]

Yep. It's also missing an interface to performance counters and I don't think that BypassIO is supported by that new driver.
Mind boggling that a company as big as MS would produce a new driver which would just miss half of features of the current one.

No. BypassIO is not supported fully by this driver.

This is Microsoft, even when they do something right for once, they somehow manage to screw it up.
I swear Microsoft is by the biggest idiots in the industry.

 

[dgrdsv]

No. BypassIO is not supported fully by this driver.

 

[winjer]

I have that too. Though mine shows it's using volmgr.sys
What it seems to mean is that we get half of the benefits of BypassIO. It is skipping the filters but travelling in the volume stack.

 

[dgrdsv]

I have that too. Though mine shows it's using volmgr.sys
What it seems to mean is that we get half of the benefits of BypassIO. It is skipping the filters but travelling in the volume stack.

Well coupled with the fact that BypassIO isn't working on BitLocker encrypted drives and that Windows 11 22H2+ is encrypting all drives on installation on all PCs now I'd say that BypassIO as a feature is essentially dead now.

 

[winjer]

Well coupled with the fact that BypassIO isn't working on BitLocker encrypted drives and that Windows 11 22H2+ is encrypting all drives on installation on all PCs now I'd say that BypassIO as a feature is essentially dead now.

That is true. BypassIO seems to get disabled by everything. Not only Bitlocker. But also, split volumes. Indexing service. EFI partitions with only 100MB. Etc.
And it's also very limited, as it's a feature for Direct Storage. And with so limited adoption, it doesn't matter.
Also, this new driver also bypasses a ton of legacy layers, so it makes BypassIO a bit redundant.
And Direct Storage still works, it just doesn't do all of the BypassIO stuff.

With the stornvme.sys driver, BypassIO was working on my PC.

BTW, I prefer to have Bitlocker service disabled. After seeing Windows encrypt one of my drives without any input or authorization from me. Fortunately it was still waiting for me for the final go.
But after I saw several people only getting their drives encrypted by Bitlocker, and then not being able to decrypt the data and losing all of it. I prefer to have this service disabled.
Microsoft is too incompetent and untrustworthy for me to allow them to automatically start encrypting everything on my PC.

 

[dgrdsv]

BTW, I prefer to have Bitlocker service disabled. After seeing Windows encrypt one of my drives without any input or authorization from me.

I got that during 22H2 installation and then again after 24H2 installation.
TBF I've done some benchmarks with BL and w/o it and overall I'd say that I would prefer BL to be on. Will probably just leave it on after the next clean Windows install.

 

[moogman]

That is true. BypassIO seems to get disabled by everything. Not only Bitlocker. But also, split volumes. Indexing service. EFI partitions with only 100MB. Etc.
And it's also very limited, as it's a feature for Direct Storage. And with so limited adoption, it doesn't matter.
Also, this new driver also bypasses a ton of legacy layers, so it makes BypassIO a bit redundant.
And Direct Storage still works, it just doesn't do all of the BypassIO stuff.

With the stornvme.sys driver, BypassIO was working on my PC.

BTW, I prefer to have Bitlocker service disabled. After seeing Windows encrypt one of my drives without any input or authorization from me. Fortunately it was still waiting for me for the final go.
But after I saw several people only getting their drives encrypted by Bitlocker, and then not being able to decrypt the data and losing all of it. I prefer to have this service disabled.
Microsoft is too incompetent and untrustworthy for me to allow them to automatically start encrypting everything on my PC.

When I had an issue which my Bitlocker and needed the key, I was pleasantly surprised that MS hold it on your Microsoft online account. It could be considered a security flaw to be fair, but it got me out of a big issue at the time.

 

[crazyriddler]

I have tested the directstorage benchmark, and the difference is only marginal for games that use it. It should benefit games that don't use it, although further testing would be needed to confirm this. Initially, it does not appear to have a negative impact on games that use DS.

New stack enable

DIsable

 

[winjer]

Windows 11 Native NVMe Support Gives PCIe SSDs a Performance Lift

 

[StereoVsn]

Windows 11 Native NVMe Support Gives PCIe SSDs a Performance Lift

In real life I think overall performance increase is not that large. However if you work with storage more heavily, it's pretty good improvement.

So for gaming - generally meh. Doing large video exports, DB work, some LLM activities, etc… this should all help.

 

[winjer]

In real life I think overall performance increase is not that large. However if you work with storage more heavily, it's pretty good improvement.

So for gaming - generally meh. Doing large video exports, DB work, some LLM activities, etc… this should all help.

It still brings a decent improvement for games. Slightly lower CPU usage and higher SSD throughput. It also depends on the SSD.
I have seen on some doing almost nothing. But in others doing some nice improvements.

Still, this is a beta feature on Windows Home and Pro, so there can be issues. Because of that, it's only recommended for more advanced users and not to be used on critical systems.

 

[//DEVIL//]

I am not sure if i did it correctly. I went YOLO and went to CMD under admin and copy paste the commands winjer posted

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

it told me it did successfully. but I am not seeing any changed in device manager. using windows 11 pro here

 

[Bojji]

I am not sure if i did it correctly. I went YOLO and went to CMD under admin and copy paste the commands winjer posted

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

it told me it did successfully. but I am not seeing any changed in device manager. using windows 11 pro here

I did everything based on this post:

News  Post in thread 'Microsoft introduces "Native NVMe" driver stack'

Dec 20, 2025

Did you add the keys using Powershell in Admin elevated prompt?

Ok i managed to get it working

So the steps are

Update W11 to 25H2, it should come with the KB thing
Create a restore point
Run as admin powershell
Copy, paste enter the 3 lines one after another :

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

• peish

• 
• 

And then keys that fix safe mode - posted by winjer

 

[winjer]

I am not sure if i did it correctly. I went YOLO and went to CMD under admin and copy paste the commands winjer posted

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

it told me it did successfully. but I am not seeing any changed in device manager. using windows 11 pro here

Did you restart the PC?

 

[ResilientBanana]

A lot of stutters in UE games comes from shaders caching in memory.

 

[//DEVIL//]

Ok i managed to get it working

So the steps are

Update W11 to 25H2, it should come with the KB thing
Create a restore point
Run as admin powershell
Copy, paste enter the 3 lines one after another :

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

Download run the .msi policy file from M$ https://download.microsoft.com/download/123547b0-bff7-419d-96ba-d1cfee92f442/Windows 11 24H2, Windows 11 25H2 and Windows Server 2025 KB5066835 251014_21251 Feature Preview.msi
Reboot PC, go to local group policy editor - computer configuration - administrative templates - kb5066835 251014_21251 Feature Preview. Enable

So far, nothing usual happened or changes to the settings.

Hwinfo is still able to readout the temps and such

I run a quick CDM9 benchmark, before and after, the Rnd4K Q32T16 RW results a bit higher >30%, but im not sure if the before was correctly done, i just did it once

i followed these. Enabled it I will do a reboot. but how do i tell if its actually working ?

Also thank you and winjer for this.

 

[winjer]

i followed these. Enabled it I will do a reboot. but how do i tell if its actually working ?

Also thank you and winjer for this.

To check if it's enabled. Open devicee manager and check it's using this driver:

 

[//DEVIL//]

To check if it's enabled. Open devicee manager and check it's using this driver:

yup. got it on both drivers. thanks.

 

[amigastar]

Does this work on SSD also because i changed everything but the drives are not displayed under Storage disks?
Edit: oh man it doesn't work with normal SSDs.

 

[MayaXG]

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.

Windows' ubiquity is its biggest curse. They don't have the luxury of slamming every new thing into the OS and end up breaking a 30 year old piece of software that a Fortune 50 or government agency uses. That's billions of dollars of risk. No other company has that burden on top of having to run on every combination of crap PC parts you can think of.

 

[Pejo]

Between these improvements and the latest metrics for Win 10 vs. Win 11 gaming performance, maybe it's finally time to upgrade my gaming PC to Win11?

I'm still a little gunshy about it, if I'm being honest.

 

[Det]

Windows' ubiquity is its biggest curse. They don't have the luxury of slamming every new thing into the OS and end up breaking a 30 year old piece of software that a Fortune 50 or government agency uses. That's billions of dollars of risk. No other company has that burden on top of having to run on every combination of crap PC parts you can think of.

That's why Microsoft makes new versions of Windows.

The old version continues running on the old hardware that ALREADY runs it.

The new version has new software for new hardware.

It's curious that they loved to force PAID upgrades to the new version of Windows, so the user could access the new version of DirectX that was only "possible" in the new version of Windows.

Nobody here is an idiot; Microsoft is just incompetent and only exists because it has two monopolies.

 

[peish]

Been dailying this for 3 months and every thing has been fine. From windows update to driver chipset updates. No ssd degradation seen, still at 99%

 

[Sardaukarama]

Got brave and thought fuck the backup (nothing of note on this system worthy to lose)...Everything went great !
Thanks for the info winjer
Will update on any differences I notice

 

[winjer]

Microsoft disables NVMe registry tweak in Windows 11 Insider builds

Microsoft has removed a widely used workaround that allowed Windows 11 users to enable a newer native NVMe driver through registry edits. The change, first observed in recent Insider Preview builds, blocks the ability to force-load the driver using manual registry modifications, effectively closing off a method that had gained traction among enthusiasts. The NVMe driver in question originates from Windows Server 2025 and has demonstrated measurable performance improvements in various storage benchmarks. Testing across multiple platforms showed consistent gains in random I/O performance, particularly in 4K workloads. In some cases, users reported up to 65% faster random read speeds, alongside improvements in write performance depending on the SSD and system configuration.

Despite these gains, the workaround came with notable trade-offs. Switching to the native driver caused compatibility issues with vendor-specific SSD utilities, including Samsung Magician and Western Digital Dashboard. Additionally, systems using BitLocker encryption could trigger recovery prompts after the driver change, introducing potential risks for less experienced users.

Although the registry-based method is no longer functional, the feature itself has not been entirely removed. Users can still access the native NVMe driver through alternative means, such as ViVeTool, which enables hidden Windows features by activating specific feature IDs. This method requires administrative privileges and a system reboot, and it retains the same compatibility and stability concerns as the original tweak.

Microsoft has not yet confirmed when the native NVMe driver will be officially integrated into mainstream Windows 11 releases. Future updates, including versions 25H2 and 26H2, are expected to bring further clarity on broader support. Until then, access to the driver remains limited to experimental methods within preview builds.

 

[LiquidMetal14]

Microsoft disables NVMe registry tweak in Windows 11 Insider builds

It's very much appreciated but I stopped going with The insider builds as I had to do a complete reinstall and I don't like the idea of having to read sort the furniture so to speak.

You appreciate the progress on something that really should have been implemented a long time ago. And if this actually impacts performance overall across the board due to the driver's stack then the update can't come soon enough and should have been here, as I said, a while ago.

 

[Bojji]

Microsoft disables NVMe registry tweak in Windows 11 Insider builds

So if I enabled it months ago it should still work?

 

[winjer]

So if I enabled it months ago it should still work?

It's an update that changes how the feature is enabled.
To enable it again, if necessary, instead of using this reg: 735209102

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

Use this instead:

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

The other 2 keys are still necessary, but remain the same:

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

 

[Bojji]

It's an update that changes how the feature is enabled.
To enable it again, if necessary, instead of using this reg: 735209102


Use this instead:


The other 2 keys are still necessary, but remain the same:

I still see nvme driver without doing anything:

Does is mean it's on or I have to use first reg key again?

 

[winjer]

I still see nvme driver without doing anything:

Does is mean it's on or I have to use first reg key again?

It's still on. Just leave it as is.

 

[dgrdsv]

FYI: this got disabled in Win11 25H2 2026-03 Update (KB5086672) (26200.8117)
Dunno if it can be re-enabled, will wait for an official release now.

 

[LiquidMetal14]

I hope they can stop or we can stop bumping This thread to talk about something that isn't out yet I suppose? But I tell you with the prices of everything I hope they figure out a little ways to improve the hardware we already have. That's why I'm really for dlss not just because it works really well but because it could potentially extend our hardware.

I feel like the propaganda against AI or what it could potentially do for us positively is like what United States has gone through with the mainstream media being mainly Democratic then practically brainwashing the country with bullshit have truths.

I had to toss in that bit of reality here for those of us in the States but these kinds of technology I want to evolve and exist when they make sense rather than paying exorbitant amounts of money. Like that rumored neural rendering texture stuff for the ps6, yes, yes all the time if it's going to reduce the headroom for some things that are expensive.

 

[peish]

It's an update that changes how the feature is enabled.
To enable it again, if necessary, instead of using this reg: 735209102


Use this instead:


The other 2 keys are still necessary, but remain the same:

FYI: this got disabled in Win11 25H2 2026-03 Update (KB5086672) (26200.8117)
Dunno if it can be re-enabled, will wait for an official release now.

can confirm these 2 points.

My pc updated to 26200.8117 and the "storage disks" in device manager disappeared.

added this DWORD 32bit in regedit, reboot and "storage disk" is back in business

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