This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 42%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Is anyone else having this nightmare with their VM's failing to restart in Azure? Support have been no help and will only help once I have a crash dump file which is very hit and miss unless I enable full crash dump on all our servers.
The issue is the server restarts and never comes back up, you can still ping but the Boot Diagnostics screen is just black, the only option is to force a shutdown and restart.
We haven't imported this issue into Azure as it also affects VM's we built in Azure.
We're having the same issue too (exact same symptoms).
While I'm ranting... why hasn't Microsoft seen fit to separate the Shutdown and Restart controls into separate group policies. Every comment I've ever read from Microsoft says "why on earth would you want to do that?!?!? If they can reboot, they should be able to shutdown, right?"...
to which, of course, the answer is NO.
I will add a little bit of detail. In our case, we have Windows 10 Enterprise For Desktop and the VM agent installed on our boxes (Agent version 2.7.41491.1071), but we do NOT have identity turned. We CAN'T turn it on, since Microsoft, in their wisdom, decided to put a check for machine identity first in the authentication stack for Azure integration authentication. Dumbest thing I've ever seen. It checks the machine, to which we DON'T grant rights in Azure, fails, and then doesn't try any other kind of authentication. That... combined with the fact that you either turn off Shutdown/Restart, or turn it on with group policy, but not one or the other, shows Microsoft is clearly way behind the game in terms of the concept of running VMs as managed workstations in a corporate environment.
Anyways... the agent doesn't do jack crap in terms of informing Azure that the machine is in a shutdown state. Without identity turned on, I can shutdown a vm, and Azure has no clue it's not still running (other than the BLACK screen it shows on boot diagnostics). I can actually run a ping -t, and which it go offline, and then come back to Azure and the Stop button is still clickable.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 89%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
Hi @Andrew Azure ,
We are experiencing the same or similar issues. Ping is okay but the boot diagnostics is as follows:
This is happening only with Windows Server (2019) GEN2 VM's. Were you able to find any resolution to this issue? This seems to occur randomly - not every reboot ends up in this state. Frustrating issue tbh.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 34%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hi @Justin Credible ,
We have excactly the same issue as seen in your printscreen on Windows Server 2019 and Windows 10 Enterprise multi-session GEN2 VMs.
And as you described the issue doesn't happen on every reboot.
Hi @Justin Credible ,
No 3rd party AV, just built-in Defender. The VMs are all built from marketplace images.
In which Azure location are your VMs located? Ours are located in the Switzerland North region.
Hi @Mike ,
Thanks. We are deploying marketplace images also. We are located Amsterdam, West Europe.
We're experiencing similar issues on Windows Server 2019 Gen2 instances running in different Azure regions. All VM were built from the Azure market place. Using 3rd party AV (Carbon Black). I'm curious if there's been any feedback from Microsoft on this issue?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 2%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hello,
@Andrew Azure @Justin Credible @Mike
Have you found the RCA?
we have the same problem. A lot of times we had the problem after the installation of the patches (so on on the patching reboot) but for the moment we aren't sure that every black screen is related to them
Thank you
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 18%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
I am experiencing the same problem as well. Got a case opened with MS right now to see if I can get it resolved. I have notice that this issue occurs on multiple subscription that I own and randomly on different VMs each time when patching time comes around. I just have a suspicion that something is wrong either on the image/VM combo or the host that is it hosting on. This issue has been going on for a while while i have been trying to generate a memory dump to investigate on. But since the VM is stuck at a state where it seems to not response to the dump triggered by NMI, i have been having trouble getting a dump for them to work on. Have anyone of you experience the same thing on generating a dump?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 74%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESV%3C/text%3E%3C/svg%3E)
I have created a separate thread on this which has had a response since.
If you manage to progress with your investigation please do let us know. This is affecting a number of my VMs in different Azure Regions.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 56.00000000000001%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFL%3C/text%3E%3C/svg%3E)
Good morning everyone, we have the same problem on our VMs, on different tenants, when they are restarted programmatically. Totally randomly we end up with VMs stuck with black screen, and Azure Agent offline. This happens even with Windows 10 Multisession (AVD) VMs!!! Has anyone maybe found a solution or the reason for this problem? Thank you very much
Has anyone found a solution yet for this issue? Experiencing the same issue with the same VM Image specifications:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 75%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENE%3C/text%3E%3C/svg%3E)
You need to set the registry first for it to listen to the NMI. You should also change registry to get a full dump. (Active dump may be preferred to get a bit smaller)
Perhaps you can add a policy to your VMs which can have this issue that adds/sets the registry keys to create full dump and to trigger it on NMI.
Then use Serial Console to send the NMI signal.
https://learn.microsoft.com/en-gb/troubleshoot/azure/virtual-machines/serial-console-windows#use-the-serial-console-for-nmi-calls
https://learn.microsoft.com/en-GB/troubleshoot/windows-client/performance/generate-a-kernel-or-complete-crash-dump#use-nmi
https://support.microsoft.com/kb/969028
:: Enable dump on NMI
reg add HKLM\System\CurrentControlSet\Control\CrashControl /v NMICrashDump /t REG_DWORD /d 1 /f
:: Set Pagefile to RAM+256MB (e g MIN 8448 and MAX 12000 on 8GB VM) and enable Complete memory dump, add also FilterPages to get Active memory dump (smaller, from Windows 10+/2016+)
reg add HKLM\System\CurrentControlSet\Control\CrashControl /v CrashDumpEnabled /t REG_DWORD /d 1 /f
reg add HKLM\System\CurrentControlSet\Control\CrashControl /v FilterPages /t REG_DWORD /d 1 /f