This blog moved to a new location, new link
Updated Jun 30, 2025
Version 3.0
phleiten
Microsoft
MicrosoftBlog Post
23 Comments
Hello, I have customized GEN2 Win2019 STD VM image and trying to update SCSI to NVME, but unable to do. I am getting below error.
- phleiten
this is fixed in the new version of the script available here: SAP-on-Azure-Scripts-and-Utilities/Azure-NVMe-Utils at main · Azure/SAP-on-Azure-Scripts-and-Utilities
I did this, just a few weeks back and it worked fine, now I am getting the same error. :-(
- phleiten
we know about the behavior of migrations to e.g. v6 instances and we are working on a fix.
at the moment you can't convert a source VM (v3, v4, v5) with tempdisk ("d" in the name) to a v6 instance, only works for VMs without tempdisk.
- phleiten
There are actually two errors here. One seems to be related to your permissions, access token denied.
The second one might be related to a situation where you can't convert to v6 instances. We are investigating this at the moment.
I have Owner rights on the Subscription. What additional permissions we need.
Can this be done to a V1 virtual machine?
- phleiten
NVMe only works for Gen2 VMs.
- phleiten
thank you raindropsdev for adding the additional content, I check and add it to the blog
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 /fThen 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.
We're getting bluescreens after deleting the registry key and then using the powershell script to enable NVME on Windows 11 images:
<INSTANCE CLASSNAME="BLUESCREEN"> <PROPERTY NAME="STOPCODE" TYPE="string"><VALUE>"0x7B"</VALUE></PROPERTY><machine-info>The script doesn't seem to care about whether the image is supported or not and enables it anyway:
Though this is a Windows 11 image which is indicated as supported in the documentation, so I'm a bit confused:
Source image publisher: microsoftwindowsdesktop Source image offer: office-365 Source image plan: win11-23h2-avd-m365Is there any way to address this? We have tested enabling NVME on both Windows 11 and Windows Server 2022 VMs and all of them have been getting this BSOD, despite deleting the reg key before shutdown.
The only way we've succeeded in having a VM with NVME enable was deploying it as such from scratch, which is not really feasible for many of our workloads.
if it helps anyone... I used the script but always ran into the bluescreen issue. After banging my head against the wall I found that if you do all the prep, run the script without start, leave it off, then take a snapshot of the disk, convert it to managed, attach it as a 2nd disk to a new v6 vm, boot it, shut it down, then swap your os disk with the new managed disk... it boots. I didn't do a ton of testing to see if I could have just mounted the converted managed disk from snapshot (maybe that would work). Succeeded on a win 10 multi-user AVD, probably works on server 2019, I might try that later.
