This blog moved to a new location, new link
Updated Jun 30, 2025
Version 3.0
phleiten
Microsoft
MicrosoftBlog Post
If someone is having similar issues, you need to modify other registry keys:
reg delete HKLM\SYSTEM\CurrentControlSet\Services\stornvme\StartOverride /f
reg ADD "HKLM\SYSTEM\CurrentControlSet\services\stornvme" /v "ErrorControl" /t REG_DWORD /d 0 /f
reg ADD "HKLM\SYSTEM\CurrentControlSet\services\stornvme\StartOverride" /v 0 /t REG_DWORD /d 0 /f
Then shut down the machine from inside the OS, wait for it to be Shutdown, Deallocate it and then run the script.
Source of the additional registry keys: https://www.reddit.com/r/pchelp/comments/11uxekv/windows_failed_repair_or_recovery_blue_screen/jcsz8dd/
raindropsdev,
I appreciate you finding the extra registry changes but did you ever happen to find any more registry changes that need made?
We've attempted to change a Server 2019 VM from SCSI to NVMe using the three registry commands listed and while the script runs without any errors, the VM blue screens on start up - even though everything else appears to work prior.
Thanks for your time.
- phleiten
I'm working on a new version of the script which would run the commands using Az-RunCommand, this will make it easier to convert to NVMe.
Hi,
phleiten
I am encountering a blue screen error on Windows Server 2022 with the message “INACCESSIBLE_BOOT_DEVICE” after making some changes.
I have already run the `reg delete` and `reg add` commands as part of troubleshooting.
Additionally, I tested the newer version of your script with the `fixos` option, but unfortunately, it did not resolve the issue.
Could you please assist further? Thank you!- phleiten
hi,
can you try this procedure:
- run "sc.exe config stornvme start=boot" in an elevated powershell or command line
- shutdown the OS inside the operating system
- convert the VM
also, please check any 3rd party antivirus or security solutions, if in use please check with the vendor.
