25H2 26200.8116/8117 work vivetool /enable /id:60786016,48433719 Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides] "3244671118"=dword:00000001 "1853569164"=dword:00000001 "156965516"=dword:00000001 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 3244671118 /t REG_DWORD /d 1 /f
Which method works to re-enable on 24H2 26100.7628? EDIT: fixed with this tool: NVMe Driver Patcher for Windows 11
You need to add a couple of new reg entries to fix SafeBoot: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\nvmedisk] @="Service" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\nvmedisk] @="Service" Code: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\nvmedisk" /ve /t REG_SZ /d "Service" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\nvmedisk" /ve /t REG_SZ /d "Service" /f
Actually since 25H2 KB5079391 (March 2026) you need both (GUID + canonical service-name pattern used by storport/stornvme/storahci), plus there are errors in your GUID entries: Code: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\{75416E63-5912-4DFA-AE8F-3EFACCAFFB14}" /ve /t REG_SZ /d "Storage Disks" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\{75416E63-5912-4DFA-AE8F-3EFACCAFFB14}" /ve /t REG_SZ /d "Storage Disks" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\nvmedisk" /ve /t REG_SZ /d "Service" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\nvmedisk" /ve /t REG_SZ /d "Service" /f
Thats not correct, but i do see the error in my edit, since i only modified the existing key name in my tiredness. The nvmedisk service entry under safeboot is not required, no Disk type requires it - nvmedisk included
I used those 3 keys on 26100.8457 (24H2) for Storage disks, and rebooted to Safe Mode (4/no-network) seemingly fine without needing to do the nvmedisk service stuff
The nvmedisk driver on 26H1 seems to corrupt data. Symptoms include zeroized first sector of various files, including ones that were not accessed.
Yes, can confirm, as soon as I removed 3 mentioned registry records and Native NVME feature was disabled after OS restart Component Store shows no sign of corruption: Code: DISM /Online /Cleanup-Image /ScanHealth Deployment Image Servicing and Management tool Version: 10.0.26100.9549 Image Version: 10.0.26100.9550 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully. DISM /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.26100.9549 Image Version: 10.0.26100.9550 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully.