SSD Turbo: NVMe driver quietly switched back

If you used the new NVMe SSD driver in Windows 11 with a registry hack, you are likely using the old driver again without being informed.

(Image: c't)

Apr 27, 2026 at 2:14 pm CEST

2 min. read

By

Dirk Knop

Last December, Microsoft released a new NVMe driver for Windows Server 2025 and Windows 11 from version 24H2, which eliminated SATA translation and promised performance gains. It could be activated for testing with a registry hack. However, Microsoft has since changed the relevant registry entries. Those who used the registry hacks are now generally working with the old driver again.

Shortly before Christmas, information emerged that allowed the “SSD Turbo” to be enabled by changing a few registry values. The effectiveness could be recognized by the fact that the SSD no longer appeared under “Disk drives” in the Device Manager but under “Storage controllers.” And this is now being noticed by more and more users who had previously made the switch using a registry hack: The SSD is sorted under “Disk drives” again.

This is not particularly surprising. Microsoft only wants to test the driver within a limited scope and apparently does not yet consider it stable enough for mass deployment. It is advisable to at least back up and have BitLocker keys accessible before making any changes, and ideally to create a backup of the SSDs. However, many have not noticed the change – the speed gains therefore seem not to be that significant.

Videos by heise

SSD Turbo: New Workaround

Anyone who still wants to use the new NVMe driver at their own risk can help themselves elsewhere. With “ViVeTool,” individual Windows functions can be enabled or disabled using a feature ID. A quick search online reveals the feature IDs 60786016 and 48433719 for this purpose.

The ViVeTool can be downloaded from the project pages on GitHub. To enable the functions, interested parties must start a terminal with administrator rights, for example, by clicking the Start menu, typing “cmd,” and selecting “Run as administrator.” Then, users must change to the directory where ViVeTool was extracted using “cd.” The command vivetool /enable /id:60786016,48433719 reactivates the NVMe driver. A system restart is then required.