Black screen after test failover

Category: microsoft azure site recovery


VRK13 on Fri, 09 Feb 2018 09:35:12

I'm having trouble with ASR test failover. This is not related to SCVMM in any way, but I could not find other forum, so hope this is the correct one.

I am protecting a Hyper-V virtual machine. However, since this is a service provider shared platform, we do not have access to hypervisor, so we have to protect it like a physical server. A configuration server has been installed in the same local subnet with the protected server.

The virtual server has only c drive, and nothing extra installed (just testing ASR). OS is Windows Server 2012 R2. The disk is GPT/UEFI disk, which became supported lately (only one-way failover to Azure, no need to failback): EDIT: The information is now corrected, physical servers with EFI boot are NOT supported.

After test failover the virtual server boots and stays in black screen, what I can tell from the boot diagnostics screenshot. I have tried to resize the virtual machine, redeploy, reset, whatever I can think of, but no help. I have also gone through all similar threads and posts I can find about this issue, but no help.

Any ideas are very much appreciated.


SumanthMarigowda-MSFT on Fri, 09 Feb 2018 16:39:55

If your Windows virtual machine (VM) in Azure encounters a boot or disk error, you may need to perform troubleshooting steps on the virtual hard disk itself. A common example would be a failed application update that prevents the VM from being able to boot successfully. This article details how to use the Azure portal to connect your virtual hard disk to another Windows VM to fix any errors, Blank/Black screen or more. 


This article describes how to run a disaster recovery drill to Azure, using a Site Recovery test failover.

However, you can also refer to the Troubleshoot Remote Desktop connections to an Azure virtual machine running Windows. 

For more information related Remote Desktop connections issues; Click here


Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

VRK13 on Mon, 12 Feb 2018 12:38:06

Thank you for the reply. However, I still haven't found any clue, why the VM fails to boot in Azure. There are no pending updates or reboots, no third party software or enything else. I can attach the disk to other virtual machine to check it seems to be in order, but I can't find any problems.

I can't avoid thoughts that this is due to GPT/UEFI disk. Even though ASR now supports that, there must be some glitches with it. Any help is greatly appreciated.

SumanthMarigowda-MSFT on Tue, 13 Feb 2018 20:24:21

Sometime this issue occurs due to low disk space on C: drive.  

Additional information: Refer to the below mentioned link

Disclaimer: This response contains a reference to a third-party World Wide Web site.

Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.

There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.


Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

VRK13 on Wed, 14 Feb 2018 09:24:35


the C drive has about 30 GB free space.

I created a new virtual machine, this time with MBR OS disk, and that works perfectly. So the GPT/UEFI disk is the reason. Just wondering how to fix that...

VRK13 on Wed, 14 Feb 2018 10:55:59

Update: I opened a support case with Microsoft. It looks like there are some issues with UEFI, and they are working on that. I will update here when something new comes up.

VRK13 on Wed, 14 Feb 2018 14:26:06

And it seems the information in

is incorrect. Physical servers with EFI are NOT supported, this is confirmed by Microsoft support. According to support engineer, the document is going to be edited soon, to remove incorrect information.

Adam Smith (Azure) on Mon, 05 Mar 2018 21:36:12

Was the issue resolved by support or do you need any further help ?

VRK13 on Wed, 07 Mar 2018 07:51:00

The issue is resolved. Not the way I expected, but maybe in the future ;)

Brent Criddle on Mon, 07 May 2018 02:53:19

Hi VRK13,

We are currently experiencing basically the same issue with one of our customers. Is the resolution of your issue something you're able to share? We have a ticket open currently, but if your fix works, it would be worth a try :)


VRK13 on Tue, 15 May 2018 13:51:41

Hello Brent,

I have shared the solution: The scenario I described is not supported at the moment.

Now the article behind the mentioned link above has been corrected, it was showing incorrect information at the time of my problem, stating also physical servers with efi boot would be supported. Unfortunately they are not, hopefully later they will be.