Solved Tweak Windows 11 to Speed up NVMe SSD Performance

In this guide, I’ll outline the steps to enable the hidden NVMe driver to improve SSD performance on Windows 11.


Windows 11 have hidden Registry tweak derived from Windows Server 2025 NVMe driver behavior.

The tweak removes legacy SCSI translation, potentially improving SSD latency and IOPS.

On Windows 11, registry tweak can improve NVMe Solid-State Drive (SSD) performance, tweak that enables a newer native NVMe driver behavior originally introduced on Windows Server 2025. This change may reduce storage latency, increase IOPS, and improve overall system responsiveness by removing legacy SCSI command translation from the storage stack.


To enable the new NVMe driver to improve SSD performance on Windows 11, follow these steps:

If you plan to use these instructions, it’s recommended to perform a performance test of the NVMe SSD and compare it with the new driver enabled.


Download CrystalDiskMark




From Start Menu search bar type cmd.exe, right-click the top result, and choose the Run as administrator option.

Type this command to enable the new storage driver on Windows 11 and press Enter:



Restart the computer.


Open the device manager and expand “Storage disks” branch, and that your drive appears on the list.



Open GitHub website.

Download the ViveTool-vx.x.x.zip file on your computer.





If the “Storage disks” branch isn’t available, it’s likely because the driver isn’t available on your computer. In this case, you can try enabling the feature using the ViveTool and running the following command:


After restarting the computer, “Storage disks” should appear in the Device Manager, indicating that the driver is now working on your computer.


Hidden Windows 11 Tweak to Speed up NVMe SSD Performance

Previous threads, for funsies:

Apparently it should give significant advantage in SSD performance. But why developers still didn't deliver it officially to non-server Windows versions, even for Insiders? Could it be an intentional decision due to (rare) chance of unwanted consequences in some configurations, including no performance improvement at best and unbootable OS, BSOD and/or data loss at worst? If so, at least the warning here would be reasonable.
Otherwise it may be a result of higher priority of developing K2...

Slavic said:

But why developers still didn't deliver it officially to non-server Windows versions, even for Insiders?

Click to expand...

Higher speed = higher heat. Peak NVMe already runs at 80C with a cooler, so this could be a breaking point, not worth the risk.
It is not much different from overclocking CPU/GPU/RAM, not all PCs are built equal, only some have a better cooling than other.

TairikuOkami said:

Higher speed = higher heat. Peak NVMe already runs at 80C with a cooler, so this could be a breaking point, not worth the risk.
It is not much different from overclocking CPU/GPU/RAM, not all PCs are built equal, only some have a better cooling than other.

Click to expand...

You are correct if PC does not have good cooling system then it may cause problem so far i had no problems enabling the tweak.

i don't think this works in current Windows builds.

BEFORE AFTER

kelper said:

i don't think this works in current Windows builds.

Click to expand...

It depends, my old NVMe 3.0 got slower, my new NVMe 4.0 got faster. I wonder about NVMe 5.0, my motherboard supports it.

I did this on one system with NVMe 4.0 drives, no measurable difference. It might be dependent on the processor, faster processors may not show much improvement. I should try it on my laptop, it has an i3 processor, probably a better candidate for something that is processor dependent.

gunrunnerjohn said:

It might be dependent on the...

Click to expand...

BIOS and chipset drivers also go hand in hand, like AGESA in AMD, neither works without the other, there are many variables.

I think I'll let sleeping dogs lie. Upgrading to NVMe 4.0 drives in my new build got me over a 10:1 improvement speed increase over the SATA SSD drives I was using in the previous computer, I think I can live with that.

Never seen significant speed improvements with this enabled.

Mostly where you would see an advantage is server use.

I came across these potential issues if you do this.

kelper said:

i don't think this works in current Windows builds.

BEFORE AFTER

View attachment 180520View attachment 180521

Click to expand...

Does your drive appear on the list under Storage disks branch in Device Manager?

working fine on my system but i did set this up after i installed Windows
Windows Home 25H2



my bad but i cant get this to work, MS seem to have locked out this tweak
best of luck Steve ..

XxXxX said:

working fine on my system but i did set this up after i installed Windows
Windows Home 25H2

View attachment 180603

best of luck Steve ..

Click to expand...

You need NVMe SSD listed under Storage disks branch in Device Manager not Storage Controller.

If the “Storage disks” branch isn’t available, it’s likely because the driver isn’t available on your computer. In this case, you can try enabling the feature using the ViveTool and running the following command:


And reboot Windows 11 to make the changes take affect.

There's a full GitHub project that wraps this feature safely:

GitHub - SysAdminDoc/win11-nvme-driver-patcher: GUI tool to enable the experimental Windows Server 2025 NVMe storage driver on Windows 11.

garlin said:

There's a full GitHub project that wraps this feature safely:

GitHub - SysAdminDoc/win11-nvme-driver-patcher: GUI tool to enable the experimental Windows Server 2025 NVMe storage driver on Windows 11.

Click to expand...

To complicated to follow what is wrong with my guide?

Because it's not just enabling two feature ID's and praying you don't hose your NVMe. You don't need to follow all of the commands.

What you're getting is someone who's studied the driver problem with caution, and not some tech writer. Like your method doesn't work in Safe Boot mode.

Like i said to complicated to flow i enable the tweak on two computer without problems but having image backup is recommended just in case.