Can anyone brave test it with safe mode? For me it brakes boot sequence and i need to fix it with USB repair, think this migration can brake boot in some cases as i enable it via vivetool and not as reg entry in policies When it works ok try DDU to get into safe mode and see, as i got this bug triggered when i try to cleanup my display drivers via DDU(before new nvme driver all works perfect and can say it 100% as i test new drivers alot)
You can delete the Policies CFR registry key or the delete [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\8] used by the Vivetool default to undo the changes.
It works for me but only with microsoft nvme driver. I have 4 m.2 disc all from samsung and after windows instalation i did driver update to samsung driver. I had to restore microsoft driver to get it to work.
question at everyone.. i used this to activate it from deskmodder (it works) Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides] "735209102"=dword:00000001 "1853569164"=dword:00000001 "156965516"=dword:00000001 is there something important missing ? also please can someone show me how an "disable it" regfile would look of that please ? (to have it saved when i need to disable it in the future maybe)
For me its not worth the problem it generates with safe mode for now, think i wait for proper Client version.
Which driver did you update to a Samsung driver? Samsung has never built or offered a disk drive driver. Samsung's NVMe driver is only usable by an NVMe Storage Controller.