Windows 11: Native NVMe Driver Blocked and Alternatives to Boost SSD Performance
Microsoft has disabled registry editing to enable the built-in NVMe driver (nvmedisk.sys) in the latest Windows 11 Insider builds. Previously, this delivered up to an 85% boost in random write performance. The alternative is ViVeTool with IDs 60786016 and 48433719.
What Changed in Insider Builds
The built-in NVMe stack from Windows Server 2025 was previously ported to client versions 24H2 and 25H2 via FeatureManagement registry keys. These four parameters no longer enable nvmedisk.sys, which replaces SCSI translation. The driver was already present in Windows 11 but disabled.
Microsoft announced nvmedisk.sys for Server 2025 with improvements:
- 80% higher IOPS;
- 45% lower CPU usage under high IO loads.
Enthusiast tests confirmed the gains:
- Random 4K reads up to 64.89% (FIO from StorageReview);
- Write speeds in AS SSD — up to 85%.
Results varied by SSD and CPU, but consistent gains in random IO were reliably observed.
Limitations and Risks
Switching to the native driver broke compatibility:
- Samsung Magician and WD Dashboard didn't work;
- BitLocker required key recovery after the driver change.
These issues persist with alternative methods. Suspend BitLocker before enabling.
How to Enable with ViVeTool
ViVeTool lets you unlock hidden features. Steps for mid/senior developers and sysadmins:
- Download ViVeTool (official release from GitHub);
- Run CMD as administrator;
- Run:
```cmd
ViVeTool.exe /enable /id:60786016
ViVeTool.exe /enable /id:48433719
```
- Restart the system.
Verify nvmedisk.sys is loaded via Device Manager or driverquery. Test IO with fio or AS SSD.
Additional Changes in 25H2
Microsoft switched the Appxsvc service (AppX deployment) to automatic start by default in 24H2/25H2. This boosts reliability but increases CPU, RAM, and disk load in peak scenarios.
In 25H2 updates and Server 2025, CLFS driver protection has been strengthened, adding system overhead.
These changes explain why Windows 11 feels heavier, impacting performance in IO-intensive tasks.
Key Takeaways
- Native NVMe driver blocked in registry for Insider builds, but available via ViVeTool;
- Up to 80% IOPS boost, 45% lower CPU load when enabled;
- Risks: incompatibility with SSD utilities and BitLocker;
- Appxsvc now auto-starts; monitor resource usage;
- CLFS protection adds system overhead in 25H2.
Developers, test in a VM before production. Expect official support in 25H2/26H2 — timelines unknown.
— Editorial Team
No comments yet.