This blog moved to a new location, new link
Updated Jun 30, 2025
Version 3.0
phleiten
Microsoft
MicrosoftBlog Post
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-m365
Is 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.