Announcing Native NVMe in Windows Server 2025



 Windows Server News and Best Practices:

Native NVMe support in Windows Server 2025 is a leap forward in storage innovation that will redefine what’s possible for your most demanding workloads. Enable Native NVMe today using a registry key after applying October’s latest cumulative update for WS2025!

We’re thrilled to announce the arrival of Native NVMe support in Windows Server 2025—a leap forward in storage innovation that will redefine what’s possible for your most demanding workloads. Modern NVMe (Non-Volatile Memory Express) SSDs now operate more efficiently with Windows Server. This improvement comes from a redesigned Windows storage stack that no longer treats all storage devices as SCSI (Small Computer System Interface) devices—a method traditionally used for older, slower drives. By eliminating the need to convert NVMe commands into SCSI commands, Windows Server reduces processing overhead and latency. Additionally, the whole I/O processing workflow is redesigned for extreme performance. This release is the result of close collaboration between our engineering teams and hardware partners, and it serves as a cornerstone in modernizing our storage stack.

Native NVMe is now generally available (GA) with an opt-in model (disabled by default as of October’s latest cumulative update for WS2025). Switch onto Native NVMe as soon as possible or you are leaving performance gains on the table! Stay tuned for more updates from our team as we transition to a dramatically faster, more efficient storage future.

Why Native NVMe and why now?

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

bS00NDc3MzUzLXA3ckVyag

Graph showing IOPS gains on WS2025 (with Native NVMe) compared to WS2022 on 1, 8, and 16-threaded 4K random read tests using an NTFS-formatted volume.

bS00NDc3MzUzLWJ6aUo3UQ

Graph showing reduction in CPU cycles per I/O on WS2025 (with Native NVMe) compared to WS2022 on 8 and 16-threaded 4K random read tests using an NTFS-formatted volume.

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.

Top Use Cases: Where You’ll See the Difference

Try Native NVMe on servers running your enterprise applications. These gains are not just for synthetic benchmarks—they translate directly to faster database transactions, quicker VM operations, and more responsive file and analytics workloads.
  • SQL Server and OLTP: Shorter transaction times, higher IOPS, and lower tail latency under mixed read/write workloads.
  • Hyper‑V and virtualization: Faster VM boot, checkpoint operations, and live migration with reduced storage contention.
  • High‑performance file servers: Faster large‑file reads/writes and quicker metadata operations (copy, backup, restore).
  • AI/ML and analytics: Low‑latency access to large datasets and faster ETL, shuffle, and cache/scratch I/O.
How to Get Started
  1. Check your hardware: Ensure you have NVMe-capable devices that are currently using the Windows NVMe driver (StorNVMe.sys). Note that some NVMe device vendors provide their own drivers, so unless using the in-box Windows NVMe driver, you will not notice any differences.
  2. Enable Native NVMe: After applying the 2510-B Latest Cumulative Update (or most recent), add the registry key with the following PowerShell command:

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

    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.

    bS00NDc3MzUzLWtwMjRoRQ

    Screenshot of Device Manager where NVMe devices show up under the Storage disks section.
  3. Monitor and Validate: Use Performance Monitor and Windows Admin Center to see the gains for yourself. Or try DiskSpd.exe yourself to measure microbenchmarks in your own environment! A quick way to measure IOPS in Performance Monitor is to set up a histogram chart and add a counter for Physical Disk>Disk Transfers/sec (where the selected instance is a drive that corresponds to one of your attached NVMe devices) then run a synthetic workload with DiskSpd. Compare the numbers before and after enabling Native NVMe to see the realized difference in your real environment!

    bS00NDc3MzUzLUlqa3QwOQ

    Screenshot of Performance Monitor, showing how to add a counter for Disk Transfers/sec to measure IOPS of an NVMe drive.

    bS00NDc3MzUzLW96WUFGeg

    Screenshot of higher IOPS when running Native NVMe stack on Windows Server 2025.
Join the Storage Revolution

This is more than just a feature—it’s a new foundation for Windows Server storage, built for the future. We can’t wait for you to experience the difference.

Share your feedback, ask questions, and join the conversation. Let’s build the future of high-performance Windows Server storage together. Send us your feedback or questions at [email protected]!


Yash Shekar (and the Windows Server team)


 Source:

 
The problem is the new driver is not DirectStorage compatible.

Before,

fsutil bypassIo state c:\
BypassIo on "c:\" is currently supported
Storage Type: NVMe
Storage Driver: BypassIo compatible

After making the registry changes in order the get new driver

fsutil bypassIO state /v c:\
BypassIo on "c:\" is currently supported
Storage Type: NVMe
Storage Driver: Not BypassIo Compatible
Driver Name: volmgr.sys

So you may actually get lower performance in games that use DirectStorage. Benchmarks don't always show everything.

I think maybe native nvme supersedes bypassio - it appears to do most of the same things, but maybe better and not for games only.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro x64
    Computer type
    PC/Desktop
    Manufacturer/Model
    📷🔈🎧 🪛 DIY Photoshop/Audio/Game/tinker
    CPU
    i9 14900K P/E 5.8/4.5 GHz, cache 5.0 GHz
    Motherboard
    Asus ROG Maximus Z790 Dark Hero
    Memory
    🐏 96GB (2x48) G.skill Ripjaws 6800 MT/s
    Graphics Card(s)
    Asus ROG Strix 4070 Ti OC
    Sound Card
    🔊Bowers & Wilkins 606 S3 speakers; Audiolabs 7000a integrated amp; RSL 10S Mk2 sub; Creative Pebble Pro Minimilist
    Monitor(s) Displays
    🖥️🖥️ Eizo CG2730 ColorEdge, ViewSonic VP2768
    Screen Resolution
    🖥️🖥️ 2560 x 1440p x 2
    Hard Drives
    💾 WDC SN850X 4TB nvme, SN850 1TB nvme, SK-Hynix 2 TB P41 nvme,. Sabrent USB-C DS-SC5B 5-bay docking station: 6TB WDC Black, 6TB Ironwolf Pro; 2x 2TB WDC Black HDD
    PSU
    ⚡️ 850W Seasonic Vertex PX-850 ATX 3.0/PCI-E 5.0
    Case
    Fractal Design North XL Mesh, Black Walnut
    Cooling
    ❄️ EK Nucleus black 360 AIO w/Phanteks T30-120 fans, 2 Noctua NF-A14 Chromax case fan, 1 T30-120 fan cooling memory
    Keyboard
    ⌨️ Keychron Q3 Max TKL with custom GMK Redsuns Red Samuri keycaps, TX Stabs
    Mouse
    🖱️ Logitech G305 wireless gaming
    Internet Speed
    ⬇️ 500 Mb/s ⬆️ 12 Mb/s
    Browser
    🔥🦊 Firefox
    Antivirus
    🦺 Defender, Macrium Reflect X 🏆
    Other Info
    Phangkey Amaterasu V2 Desk Mat
  • Computer type
    Laptop
    Manufacturer/Model
    💻 Apple 13" Macbook Pro 2020 (m1)
    CPU
    Apple M1
    Screen Resolution
    2560x1600
    Browser
    Firefox
Seems to have been removed in the latest preview build
 

My Computers

System One System Two

  • OS
    Windows 11 25H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom Built
    CPU
    Intel i9 14900KF
    Motherboard
    ASUS Z790 ProArt Creator WiFi
    Memory
    64GB Corsair Vengeance RGB
    Graphics Card(s)
    MSI 4090 Suprim X
    Sound Card
    Onboard
    Monitor(s) Displays
    1 x Asus 24". 1 x Asus 32"
    Screen Resolution
    1920 x 1080 & 2560 x 1440
    Hard Drives
    Multiple
    PSU
    Corsair 1200HX
    Case
    Corsair 7000D RGB
    Cooling
    Corsair H150I Capellix XT
    Keyboard
    Corsair K70 RGB PRO
    Mouse
    Corsair M55 RGB Pro
    Internet Speed
    1000Mbps
    Browser
    Edge
    Antivirus
    Windows Default
  • Operating System
    Windows 11 25H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom Built
    CPU
    Intel i7 6800K
    Motherboard
    ASUS Z99 Deluxe
    Memory
    32GB DDR4 (Corsair)
    Graphics card(s)
    ASUS GTX 1080ti
    Sound Card
    Onboard
    Monitor(s) Displays
    1x Viewsonic 24" 1x LG 19"
    Screen Resolution
    1920 x 1080 & 1600 x 900
    Hard Drives
    3 x SATA SSD
    PSU
    650W Gigabyte Bronze
    Case
    Coolermaster HAF-X
    Cooling
    Noctua NH-15 Chroma black
    Keyboard
    Generic RGB
    Mouse
    Microsoft Basic
    Internet Speed
    1000Mbps
    Browser
    Edge
    Antivirus
    Windows Default
Hi All,
I would like to ask, if there is a painbless way to undo these changes?

I have switched to the native NVME drivers a few months ago - slight improvements, nothing special, everything was working fine.
Until the March OOB update from 31st of March - this one goes fine until 30% and reboot, which causes an error of inaccessible boot device, which ulitiately leads to undoing the update by my laptop itself. Not the latest cumulative update from April causes the same error of inaccessible boot device.
I havr changed the reg keys to 0, but this ended with the same error on reboot and undoing the values to "1" again.

Any help would be appreciated.
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Asus TUF A15 FA507NV
    CPU
    AMD Ryzen 7 7735HS
    Memory
    64GB
    Graphics Card(s)
    RTX 4060 Mobile & AMD Radeon
    Monitor(s) Displays
    15,6"
    Hard Drives
    2x Kingston Fury Renegade 1 TB
Hi All,
I would like to ask, if there is a painbless way to undo these changes?

I have switched to the native NVME drivers a few months ago - slight improvements, nothing special, everything was working fine.
Until the March OOB update from 31st of March - this one goes fine until 30% and reboot, which causes an error of inaccessible boot device, which ulitiately leads to undoing the update by my laptop itself. Not the latest cumulative update from April causes the same error of inaccessible boot device.
I havr changed the reg keys to 0, but this ended with the same error on reboot and undoing the values to "1" again.

Any help would be appreciated.
There are 3 ways to enable native NVMe. Two involve registry edits. One involves using Vivetool. If you tell us which method and which registry keys you edited, if any, someone here can surely help. Also, there was an optional registry edit to re-enable Safe Boot after enabling native NVMe. If you made that edit, it requires a bit of finessing to undo, but it can be done.
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    PC/Desktop
    Manufacturer/Model
    iBUYPOWER
    CPU
    Intel i9-13900KF
    Motherboard
    ASUS ROG Maximus Z790 Hero
    Memory
    32 GB Corsair Vengeance DDR5-6000 MHz
    Graphics Card(s)
    ASUS Dual GeForce RTX 4070
    Sound Card
    none
    Monitor(s) Displays
    Dell U2412M
    Screen Resolution
    1920 x 1200
    Hard Drives
    WD Black SN850X NVMe SSD - 1 TB
    PSU
    Thermaltake Toughpower GF3 1000W
    Case
    Fractal Design Meshify 2 RGB
    Cooling
    Corsair H150i RGB Elite
    Keyboard
    Deck Hassium Pro
    Mouse
    Logitech MX Master 4
    Internet Speed
    1500 Mbps download, 40 Mbps upload
    Browser
    Firefox
    Antivirus
    Bitdefender Internet Security
There are 3 ways to enable native NVMe. Two involve registry edits. One involves using Vivetool. If you tell us which method and which registry keys you edited, if any, someone here can surely help. Also, there was an optional registry edit to re-enable Safe Boot after enabling native NVMe. If you made that edit, it requires a bit of finessing to undo, but it can be done.

Attached is what I use to Enable it. Just edit this file to change the two enabledStates from 2 to 0 then run the file and reboot.
 

Attachments

My Computers

System One System Two

  • OS
    Windows 11 Pro x64
    Computer type
    PC/Desktop
    Manufacturer/Model
    📷🔈🎧 🪛 DIY Photoshop/Audio/Game/tinker
    CPU
    i9 14900K P/E 5.8/4.5 GHz, cache 5.0 GHz
    Motherboard
    Asus ROG Maximus Z790 Dark Hero
    Memory
    🐏 96GB (2x48) G.skill Ripjaws 6800 MT/s
    Graphics Card(s)
    Asus ROG Strix 4070 Ti OC
    Sound Card
    🔊Bowers & Wilkins 606 S3 speakers; Audiolabs 7000a integrated amp; RSL 10S Mk2 sub; Creative Pebble Pro Minimilist
    Monitor(s) Displays
    🖥️🖥️ Eizo CG2730 ColorEdge, ViewSonic VP2768
    Screen Resolution
    🖥️🖥️ 2560 x 1440p x 2
    Hard Drives
    💾 WDC SN850X 4TB nvme, SN850 1TB nvme, SK-Hynix 2 TB P41 nvme,. Sabrent USB-C DS-SC5B 5-bay docking station: 6TB WDC Black, 6TB Ironwolf Pro; 2x 2TB WDC Black HDD
    PSU
    ⚡️ 850W Seasonic Vertex PX-850 ATX 3.0/PCI-E 5.0
    Case
    Fractal Design North XL Mesh, Black Walnut
    Cooling
    ❄️ EK Nucleus black 360 AIO w/Phanteks T30-120 fans, 2 Noctua NF-A14 Chromax case fan, 1 T30-120 fan cooling memory
    Keyboard
    ⌨️ Keychron Q3 Max TKL with custom GMK Redsuns Red Samuri keycaps, TX Stabs
    Mouse
    🖱️ Logitech G305 wireless gaming
    Internet Speed
    ⬇️ 500 Mb/s ⬆️ 12 Mb/s
    Browser
    🔥🦊 Firefox
    Antivirus
    🦺 Defender, Macrium Reflect X 🏆
    Other Info
    Phangkey Amaterasu V2 Desk Mat
  • Computer type
    Laptop
    Manufacturer/Model
    💻 Apple 13" Macbook Pro 2020 (m1)
    CPU
    Apple M1
    Screen Resolution
    2560x1600
    Browser
    Firefox
Hi,
I have used the commands as per post #10

Not sure if I have edited the Safe Boot entries as well, would have to check it first.
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Asus TUF A15 FA507NV
    CPU
    AMD Ryzen 7 7735HS
    Memory
    64GB
    Graphics Card(s)
    RTX 4060 Mobile & AMD Radeon
    Monitor(s) Displays
    15,6"
    Hard Drives
    2x Kingston Fury Renegade 1 TB
Hi,
I have used the commands as per post #10

Not sure if I have edited the Safe Boot entries as well, would have to check it first.
Run the following 4 commands in an elevated command prompt and then reboot. Or you can manually delete the 4 numbered keys in the registry editor.

reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 1176759950 /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 1853569164 /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 156965516 /f

reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 735209102 /f
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    PC/Desktop
    Manufacturer/Model
    iBUYPOWER
    CPU
    Intel i9-13900KF
    Motherboard
    ASUS ROG Maximus Z790 Hero
    Memory
    32 GB Corsair Vengeance DDR5-6000 MHz
    Graphics Card(s)
    ASUS Dual GeForce RTX 4070
    Sound Card
    none
    Monitor(s) Displays
    Dell U2412M
    Screen Resolution
    1920 x 1200
    Hard Drives
    WD Black SN850X NVMe SSD - 1 TB
    PSU
    Thermaltake Toughpower GF3 1000W
    Case
    Fractal Design Meshify 2 RGB
    Cooling
    Corsair H150i RGB Elite
    Keyboard
    Deck Hassium Pro
    Mouse
    Logitech MX Master 4
    Internet Speed
    1500 Mbps download, 40 Mbps upload
    Browser
    Firefox
    Antivirus
    Bitdefender Internet Security
Hi,
I've ran the commands as advised by @drminer, after reboot a brief appearance of the "inaccessible boot device" screen appeared (photo), then another quick restart without issues, but seems that the disks are still recognized as storage devices under the NVME driver :(

Windows update is still not possible, as it causes the inaccessible boot device screen & restarts & reverts the update finally, so I am stuck with 26200.8039 :(

Any ideas what prevents the original generic driver to be loaded and associated with the disks?

Everything was working fine until the OOB update (which I am not able to uninstall now)... KB5085516 Windows 11 Out-of-band Update build 26100.8039 (24H2) and 26200.8039 (25H2) - March 21
 

Attachments

  • WhatsApp Image 2026-04-20 at 20.33.50.webp
    WhatsApp Image 2026-04-20 at 20.33.50.webp
    146.7 KB · Views: 1
  • Zrzut ekranu 2026-04-20 204350.webp
    Zrzut ekranu 2026-04-20 204350.webp
    32.8 KB · Views: 1

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Asus TUF A15 FA507NV
    CPU
    AMD Ryzen 7 7735HS
    Memory
    64GB
    Graphics Card(s)
    RTX 4060 Mobile & AMD Radeon
    Monitor(s) Displays
    15,6"
    Hard Drives
    2x Kingston Fury Renegade 1 TB
Hi again,
after browsing through internet it looks like the recent windows update (probably 8039 in my case) has blocked the options to add/remove the overrides for native NVME.
Now each time I remove the reg keys and reboot the pc has inaccessible boot device problems and restores back the overrides :(

Any help to cure this issue, please?
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Asus TUF A15 FA507NV
    CPU
    AMD Ryzen 7 7735HS
    Memory
    64GB
    Graphics Card(s)
    RTX 4060 Mobile & AMD Radeon
    Monitor(s) Displays
    15,6"
    Hard Drives
    2x Kingston Fury Renegade 1 TB
Hi again,
after browsing through internet it looks like the recent windows update (probably 8039 in my case) has blocked the options to add/remove the overrides for native NVME.
Now each time I remove the reg keys and reboot the pc has inaccessible boot device problems and restores back the overrides :(

Any help to cure this issue, please?
It is unlikely that the keys are being added back by the system, unless the system is reverting to a restore point. What is more likely is that the keys are not being removed. After running the deletion commands using administrative rights, check that the keys have actually been deleted. If not, there is a permissions issue. If that is the case, you will need to take ownership of the keys; give Administrator full permissions; then delete them. Admittedly, that is a much more tedious process.

Also, as I said earlier, there is another place in the registry where the keys can be stored. You may be looking at the wrong place in the registry. If you put them in HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\xx\, where xx is a digit between 0 and 15, then they need to be removed from there.

I have successfuly reverted to the older standard NVMe stack. I just tested. Not sure what is happening with your system. Good luck!
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    PC/Desktop
    Manufacturer/Model
    iBUYPOWER
    CPU
    Intel i9-13900KF
    Motherboard
    ASUS ROG Maximus Z790 Hero
    Memory
    32 GB Corsair Vengeance DDR5-6000 MHz
    Graphics Card(s)
    ASUS Dual GeForce RTX 4070
    Sound Card
    none
    Monitor(s) Displays
    Dell U2412M
    Screen Resolution
    1920 x 1200
    Hard Drives
    WD Black SN850X NVMe SSD - 1 TB
    PSU
    Thermaltake Toughpower GF3 1000W
    Case
    Fractal Design Meshify 2 RGB
    Cooling
    Corsair H150i RGB Elite
    Keyboard
    Deck Hassium Pro
    Mouse
    Logitech MX Master 4
    Internet Speed
    1500 Mbps download, 40 Mbps upload
    Browser
    Firefox
    Antivirus
    Bitdefender Internet Security
Is it fair to say that this driver is for people who like living on the bleeding edge of progress?

Any speculation as to when his feature will make it into a normal Windows update?
 

My Computer

System One

  • OS
    Windows 11 2H25
    Computer type
    PC/Desktop
    Manufacturer/Model
    DIY
    CPU
    AMD 9900X
    Motherboard
    MSI X870E Carbon
    Memory
    64 GB
    Graphics Card(s)
    AMD 9070 XT
    Sound Card
    built-in
    Monitor(s) Displays
    Dell 24"
    Hard Drives
    Sabrent 1 TB NVMe, 4 x SSD (need to check models), 4 x 3.5" HDD, 8-16 TB, all WD
    PSU
    Seasonic 850
    Case
    Fractal Design North XL (which I likw)
    Cooling
    Corsair AIO for CPU, fans for case
    Keyboard
    Das Keyboard 4
    Mouse
    Corsair M65 (white)
    Internet Speed
    1 TB download
    Browser
    Firefox
    Antivirus
    Bitdefender
    Other Info
    Also have Lenovo T14S laptop (me) and Lenovo Slim 71 (wife)
Is it fair to say that this driver is for people who like living on the bleeding edge of progress?

Any speculation as to when his feature will make it into a normal Windows update?

IDK. Working fine for me and I have 3 nvme drives that I use a lot. Perhaps in 26h2 , maybe earlier in 25H2.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro x64
    Computer type
    PC/Desktop
    Manufacturer/Model
    📷🔈🎧 🪛 DIY Photoshop/Audio/Game/tinker
    CPU
    i9 14900K P/E 5.8/4.5 GHz, cache 5.0 GHz
    Motherboard
    Asus ROG Maximus Z790 Dark Hero
    Memory
    🐏 96GB (2x48) G.skill Ripjaws 6800 MT/s
    Graphics Card(s)
    Asus ROG Strix 4070 Ti OC
    Sound Card
    🔊Bowers & Wilkins 606 S3 speakers; Audiolabs 7000a integrated amp; RSL 10S Mk2 sub; Creative Pebble Pro Minimilist
    Monitor(s) Displays
    🖥️🖥️ Eizo CG2730 ColorEdge, ViewSonic VP2768
    Screen Resolution
    🖥️🖥️ 2560 x 1440p x 2
    Hard Drives
    💾 WDC SN850X 4TB nvme, SN850 1TB nvme, SK-Hynix 2 TB P41 nvme,. Sabrent USB-C DS-SC5B 5-bay docking station: 6TB WDC Black, 6TB Ironwolf Pro; 2x 2TB WDC Black HDD
    PSU
    ⚡️ 850W Seasonic Vertex PX-850 ATX 3.0/PCI-E 5.0
    Case
    Fractal Design North XL Mesh, Black Walnut
    Cooling
    ❄️ EK Nucleus black 360 AIO w/Phanteks T30-120 fans, 2 Noctua NF-A14 Chromax case fan, 1 T30-120 fan cooling memory
    Keyboard
    ⌨️ Keychron Q3 Max TKL with custom GMK Redsuns Red Samuri keycaps, TX Stabs
    Mouse
    🖱️ Logitech G305 wireless gaming
    Internet Speed
    ⬇️ 500 Mb/s ⬆️ 12 Mb/s
    Browser
    🔥🦊 Firefox
    Antivirus
    🦺 Defender, Macrium Reflect X 🏆
    Other Info
    Phangkey Amaterasu V2 Desk Mat
  • Computer type
    Laptop
    Manufacturer/Model
    💻 Apple 13" Macbook Pro 2020 (m1)
    CPU
    Apple M1
    Screen Resolution
    2560x1600
    Browser
    Firefox
It is unlikely that the keys are being added back by the system, unless the system is reverting to a restore point. What is more likely is that the keys are not being removed. After running the deletion commands using administrative rights, check that the keys have actually been deleted. If not, there is a permissions issue. If that is the case, you will need to take ownership of the keys; give Administrator full permissions; then delete them. Admittedly, that is a much more tedious process.

Also, as I said earlier, there is another place in the registry where the keys can be stored. You may be looking at the wrong place in the registry. If you put them in HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\xx\, where xx is a digit between 0 and 15, then they need to be removed from there.

I have successfuly reverted to the older standard NVMe stack. I just tested. Not sure what is happening with your system. Good luck!
Hi @drminer

I have found 156965516 and 1853569164 in overrides\0 - I couldn't edit it to 0 nor remove them - lack of permissions - so probably this was the problem and causes the error/restore of previous keys

1853569164 was also in overrides\8 - set to 0, I was able to remove it immediately

all 4 keys were of course present in the feature management overrides in controlset001 and currentcontrolset again

I have now removed the keys from overrides in featuremanagement and policies, but these are still returning to the registry, so something is recreating them...
 
Last edited:

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Asus TUF A15 FA507NV
    CPU
    AMD Ryzen 7 7735HS
    Memory
    64GB
    Graphics Card(s)
    RTX 4060 Mobile & AMD Radeon
    Monitor(s) Displays
    15,6"
    Hard Drives
    2x Kingston Fury Renegade 1 TB
Hi @drminer

I have found 156965516 and 1853569164 in overrides\0 - I couldn't edit it to 0 nor remove them - lack of permissions - so probably this was the problem and causes the error/restore of previous keys

1853569164 was also in overrides\8 - set to 0, I was able to remove it immediately

all 4 keys were of course present in the feature management overrides in controlset001 and currentcontrolset again

I have now removed the keys from overrides in featuremanagement and policies, but these are still returning to the registry, so something is recreating them...

/0 is Microsoft so you can't change that.

If I understand it correctly, you could take the key in /0 and replicate it in /8 with a 0 to override it.

Someone correct me if I am wrong about the order of priorities.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro x64
    Computer type
    PC/Desktop
    Manufacturer/Model
    📷🔈🎧 🪛 DIY Photoshop/Audio/Game/tinker
    CPU
    i9 14900K P/E 5.8/4.5 GHz, cache 5.0 GHz
    Motherboard
    Asus ROG Maximus Z790 Dark Hero
    Memory
    🐏 96GB (2x48) G.skill Ripjaws 6800 MT/s
    Graphics Card(s)
    Asus ROG Strix 4070 Ti OC
    Sound Card
    🔊Bowers & Wilkins 606 S3 speakers; Audiolabs 7000a integrated amp; RSL 10S Mk2 sub; Creative Pebble Pro Minimilist
    Monitor(s) Displays
    🖥️🖥️ Eizo CG2730 ColorEdge, ViewSonic VP2768
    Screen Resolution
    🖥️🖥️ 2560 x 1440p x 2
    Hard Drives
    💾 WDC SN850X 4TB nvme, SN850 1TB nvme, SK-Hynix 2 TB P41 nvme,. Sabrent USB-C DS-SC5B 5-bay docking station: 6TB WDC Black, 6TB Ironwolf Pro; 2x 2TB WDC Black HDD
    PSU
    ⚡️ 850W Seasonic Vertex PX-850 ATX 3.0/PCI-E 5.0
    Case
    Fractal Design North XL Mesh, Black Walnut
    Cooling
    ❄️ EK Nucleus black 360 AIO w/Phanteks T30-120 fans, 2 Noctua NF-A14 Chromax case fan, 1 T30-120 fan cooling memory
    Keyboard
    ⌨️ Keychron Q3 Max TKL with custom GMK Redsuns Red Samuri keycaps, TX Stabs
    Mouse
    🖱️ Logitech G305 wireless gaming
    Internet Speed
    ⬇️ 500 Mb/s ⬆️ 12 Mb/s
    Browser
    🔥🦊 Firefox
    Antivirus
    🦺 Defender, Macrium Reflect X 🏆
    Other Info
    Phangkey Amaterasu V2 Desk Mat
  • Computer type
    Laptop
    Manufacturer/Model
    💻 Apple 13" Macbook Pro 2020 (m1)
    CPU
    Apple M1
    Screen Resolution
    2560x1600
    Browser
    Firefox

Latest Support Threads

Back
Top Bottom