{"id":9540,"date":"2026-01-31T15:36:20","date_gmt":"2026-01-31T15:36:20","guid":{"rendered":"https:\/\/www.kevinmaschke.com\/?p=9540"},"modified":"2026-01-31T15:36:22","modified_gmt":"2026-01-31T15:36:22","slug":"importing-windows-vhdx-proxmox-vm","status":"publish","type":"post","link":"https:\/\/www.kevinmaschke.com\/en\/importing-windows-vhdx-proxmox-vm\/","title":{"rendered":"Proxmox VHDX import. Convert a physical Windows PC to a VM by creating a VHDX image"},"content":{"rendered":"\n

I recently had to set up a Proxmox Hypervisor and convert a physical Windows 10 machine into a virtual machine<\/strong> running on this server. It\u2019s not a very complicated process, but since it was my first time doing this on Proxmox, there were a few steps I didn\u2019t know beforehand and I wanted to document the process.<\/p>\n\n\n\n

Create the Windows VHDX Image<\/strong><\/h2>\n\n\n\n

This guide won\u2019t go over the whole process to create the VHDX file, but you can do this by downloading Disk2VHD<\/a>, and running it on the machine you want to migrate. Keep in mind that the file will be quite large (depending on your disk size), so make sure you have enough space for it.<\/p>\n\n\n\n

Transfer the VHDX to Your Proxmox Host<\/strong><\/h2>\n\n\n\n

We have to move the VHDX file to the Proxmox server to we can import it. There are a few ways you can do this.<\/p>\n\n\n\n

Option 1: Copy the VHDX via SFTP (WinSCP)<\/strong><\/h3>\n\n\n\n

You can download and install WinSCP<\/a> on the same Windows machine, and copy the VHDX file to Proxmox through SFTP.<\/p>\n\n\n\n

Option 2: Use a USB Drive to Move the VHDX<\/strong><\/h3>\n\n\n\n

You can copy the VHDX file to a USB drive, then connect it to the Proxmox server and mount to access the files.<\/p>\n\n\n\n

First, make sure that the USB is connected correctly<\/strong>. The following command will show a list of all block devices connected to your system. Search for a device that matches the size and\/or label of your USB drive. It might appear as \/dev\/sdb<\/code>, \/dev\/sdc<\/code>, or similar.<\/p>\n\n\n\n

lsblk\n<\/pre>\n\n\n\n
Create the folder<\/strong> where you\u2019ll mount the USB drive. You can choose any location and name, but \/mnt<\/code> is a common place for this.<\/p>\n\n\n\n
mkdir \/mnt\/usb\n<\/pre>\n\n\n\n
Mount the USB drive<\/strong> to make it accessible within the file system. Mount it to the mount point you created.<\/p>\n\n\n\n
mount \/dev\/sdb1 \/mnt\/usb\n<\/pre>\n\n\n\n
Replace sdb1<\/code> with the device name you identified earlier. Make sure you specify the partition (e.g sdb1<\/code>) and not the device (eg sdb<\/code>). If the USB drive is formatted with NTFS<\/strong> you need to specify this, and it might require installing the ntfs-3g<\/code> package:<\/p>\n\n\n\n
apt update\napt install ntfs-3g\nmount -t ntfs-3g \/dev\/sdb1 \/mnt\/usb\n<\/pre>\n\n\n\n
Once mounted, you can check the contents of the mount point<\/strong> with ls -l \/mnt\/usb<\/code> and the mounted filesystem and disk usage with df -h \/mnt\/usb<\/code>.<\/p>\n\n\n\n
Create the New Proxmox Windows VM<\/strong><\/h2>\n\n\n\n
Create a new VM in Proxmox. There are a few settings we need to set.<\/p>\n\n\n\n
    \n
  • On the OS<\/strong> tab:\n
      \n
    • Don\u2019t use any installation media.<\/li>\n\n\n\n
    • For Type<\/strong>, select Microsoft Windows<\/strong>.<\/li>\n\n\n\n
    • For Version<\/strong>, select the version that matches the VHDX.<\/li>\n\n\n\n
    • Select Add additional drive for VirtIO Drivers<\/strong>.<\/li>\n\n\n\n
    • Select the ISO image for your VirtIO drivers.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • On the System<\/strong> tab:\n
        \n
      • For Machine<\/strong>, select q35<\/strong>.<\/li>\n\n\n\n
      • For SCSI Controller<\/strong>, select VirtIO SCSI<\/strong>.<\/li>\n\n\n\n
      • Select QEMU Agent<\/strong>.<\/li>\n\n\n\n
      • For BIOS<\/strong>, select OVMF (UEFI)<\/strong>.<\/li>\n\n\n\n
      • Select Add EFI Disk<\/strong>.<\/li>\n\n\n\n
      • For EFI Storage<\/strong>, select your storage location.<\/li>\n\n\n\n
      • \u26a0\ufe0f If you are converting a Windows 10\/11 machine, select Add TPM<\/strong>, set the TPM Storage<\/strong> volume, and for Version<\/strong>, select v2.0<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • On the Disks<\/strong> tab, remove the default disks.<\/li>\n\n\n\n
      • Set the CPU and memory as you see fit.<\/li>\n\n\n\n
      • On the Network<\/strong> tab, for Model<\/strong>, select VirtIO<\/strong>.<\/li>\n\n\n\n
      • Finish creating the VM. \u26a0\ufe0f Uncheck<\/strong> \u201cStart after created\u201d.<\/li>\n\n\n\n
      • \u26a0\ufe0f Note the VM ID<\/strong> for later use.<\/li>\n<\/ul>\n\n\n\n
        Add the Converted Disk to the VM<\/strong><\/h2>\n\n\n\n
        Import the VHDX into Proxmox Storage <\/strong><\/h3>\n\n\n\n
        Open the shell on the Proxmox node and run the following command:<\/p>\n\n\n\n
        qm importdisk [vm_id] [vhdx_file] [storage]\n<\/pre>\n\n\n\n
          \n
        • Replace [vm_id]<\/code> with the ID of the VM you created.<\/li>\n\n\n\n
        • Replace [vhdx_file]<\/code> with the path and filename for the VHDX file, either on the USB drive or the path you copied it to using SFTP.<\/li>\n\n\n\n
        • Replace [storage]<\/code> with your storage name.<\/li>\n<\/ul>\n\n\n\n
          Example:<\/p>\n\n\n\n
          qm importdisk 200 \/mnt\/usb\/WIN10.vhdx local_lvm\n<\/pre>\n\n\n\n
          This process might take a while, depending on the size of the disk.<\/p>\n\n\n\n
          Attach the imported disk and boot from it<\/h3>\n\n\n\n
          We will do a few changes to the VM’s settings. On the Hardware<\/strong> tab:<\/p>\n\n\n\n
            \n
          • Look for the imported disk, usually shown as Unused Disk 0<\/em>, double click on it and set the Bus\/Device<\/strong> to SATA.<\/strong><\/li>\n\n\n\n
          • Add a new 1GB VirtIO Block disk. This is just temporary to force Windows to load the VirtIO drivers.<\/li>\n<\/ul>\n\n\n\n
            On the Options tab:<\/p>\n\n\n\n
              \n
            • Select Boot Order<\/strong> and set the SATA disk as the first device and make sure Enabled<\/strong> is checked.<\/li>\n<\/ul>\n\n\n\n
              Start the Virtual Machine, and open the Console. Let Windows boot and once inside the VM, install the VirtIO disk drivers. Once installed, open Disk Management<\/strong> and verify the VirtIO disk appears correctly. You may also need to install VirtIO network drivers so the VM\u2019s network adapter works correctly.<\/p>\n\n\n\n
              If everything is fine, shutdown the VM.<\/p>\n\n\n\n
              \"Windows<\/figure>\n\n\n\n
              Now we will edit the VM’s settings again. On the Hardware<\/strong> tab:<\/p>\n\n\n\n
                \n
              • Detach both the 1GB VirtIO disk and the main disk you imported. Select each disk, and click Detach > Yes.<\/li>\n\n\n\n
              • Re-attach the main disk, but this time as a VirtIO Block disk<\/strong>.<\/li>\n\n\n\n
              • Remove the 1GB VirtIO disk.<\/li>\n<\/ul>\n\n\n\n
                On the Options<\/strong> tab:<\/p>\n\n\n\n
                  \n
                • Update the Boot Order<\/strong> to use the VirtIO disk.<\/li>\n<\/ul>\n\n\n\n
                  Start the Virtual Machine and open the Console. Windows should boot up fine and the VM should run natively in Proxmox<\/strong> and with better performance than with the default SATA configuration.<\/p>\n","protected":false},"excerpt":{"rendered":"
                  I recently had to set up a Proxmox Hypervisor and convert a physical Windows 10 machine into a virtual machine running on this server. It\u2019s not a very complicated process, but since it was my …<\/p>\n","protected":false},"author":1,"featured_media":9537,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[410,207,219,412,414],"tags":[2815,2817,2816],"class_list":["post-9540","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guides","category-linux-en","category-technology","category-virtualization","category-windows-en","tag-proxmox","tag-virtualization","tag-windows"],"acf":{"book_cover":null,"special_featured_image":null},"_links":{"self":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/posts\/9540","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/comments?post=9540"}],"version-history":[{"count":4,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/posts\/9540\/revisions"}],"predecessor-version":[{"id":9567,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/posts\/9540\/revisions\/9567"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/media\/9537"}],"wp:attachment":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/media?parent=9540"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/categories?post=9540"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/tags?post=9540"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}