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

Question

question

TechGuyMS1-3710 asked · Mar 01 at 06:49 AM

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

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

azure-virtual-machines windows-10-setup windows-10-virtualization azure-virtual-machines-images azure-virtual-machines-migration

· 3

10 |1000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

XiaoweiHe-MSFT · Mar 02 at 07:27 AM

Hi,

uploaded on azure created an image.

Could you explain more about the sentence, I'm not clear about where do you get the VM image, it is an ISO from the official site?

Best Regards,
Anne

0 ·

TechGuyMS1-3710 XiaoweiHe-MSFT · Mar 02 at 09:06 AM

Yes an ISO image downloaded from Microsoft website.

0 ·

TechGuyMS1-3710 · Mar 02 at 08:34 PM

waiting for help please.
appreciate your time.

thanks.

0 ·

Answer 1 · 2021-03-03T20:31:34.417Z

TravisCragg-MSFT answered · Mar 03 at 08:31 PM

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.

·

10 |1000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question