Cannot Create VM by Uploading Generalized VHD from On-Premesis Windows 10

Question

Hello Experts,
I installed and generalized Windows 10 Pro on Hyper V, created fixed VHD file, uploaded on azure created an image. During creation of VM, the process struck and takes very long time, even stop VM doesn't work and eventually I have to delete VM. I tried another time and same result. While checking boot diagnostics, I found the system was waiting for a command at screen "Let's start with your region" as below link

https://www.isumsoft.com/images/windows-10/install-windows-10-on-new-ssd/choose-region.png

Am I missing something? RDP is working but doesn't accept UID/PW. Any quick solution please?

Thanks

Answer 1

This is typically what happens when you create a VM from an image with the wrong create option (attach vs from image for unmanaged disks) or the wrong disk type for managed disks.

Azure thinks this is a specialized VHD, when in reality it is generalized.

To start, lets take a step back. If you are trying to bring an on-premise VM to Azure, you do not necessarily need to sysprep the VM. If you just want to bring a single VM to Azure, converting it to a fixed size .VHD and uploading it should be all that is needed. Sysprep is required if you intend to deploy multiple VMs from a single image.

Are you creating the image with a managed or unmanaged disk? If you are following a doc or instructions, can you link them?

Here is an example of an image creation from an existing .vhd file in an Azure storage account. In that example, only worry about the OS image lines, the data disk lines are not relevant.