Available article translations:

Cannot find migrated virtual machine. Only virtual hard drive appears.

  • Parallels Desktop 9 for Mac Standard Edition
  • Parallels Desktop 8 for Mac Standard Edition


  • While setting up migration Parallels Desktop notified me that it cannot detect operating system on remote computer. So I migrated my PC as data disks.

  • After migration I cannot find migrated virtual machine, only virtual hard drive file (.hdd) is shown in ~/Documents/Parallels/


  • Parallels Desktop 8 does not support EFI migration. For migrating EFI installations, please install Parallels Desktop 9.

  • When migrating data from a remote Windows or Linux computer, Parallels Transporter Agent transfers data from the specified volume(s) of the source computer to a newly created Parallels virtual hard disk (.hdd) and creates a virtual machine configuration file (.pvs). These two files constitute a ready-to-use virtual machine. During the remote migration, only the active volume (the source computer boot volume) is made bootable, and the resulting virtual machine has the same operating system that was active during the migration. If Parallels Transporter is unable to identify the source operating system, all source volumes are migrated as data disks.

  • If you migrated your PC as data disks, the virtual machine won't work under Parallels Desktop. You will be able to use the data by mounting migrated hard drive using Parallels Mounter.


  1. Check if your PC has EFI or BIOS installation: How to know if my computer is using EFI/UEFI or BIOS firmware interface

  2. For EFI - download/install Parallels Desktop 9 and Parallels Transported Agent 9 on Mac and PC accordingly.

  3. On PC computer please open Disk Management (Start -> Run... -> diskmgmt.msc). Check partitions of Disk 0:

Your text to link here...

NOTE: If you have several volumes without drive letters, as shown on the example above, and in section Status - 'EFI System Partition' is shown not under volume (C:), it means that Parallels Desktop does not support migration 'as virtual machine' of such configuration, but only 'as data disks'.

  1. Try to start the migration.

1e5db16426987d561060acdf56d947b4 97cd84747b25a2e5a06065a21a747a53 a9c6e0b6a5209e617a7c0dd5eace86cf 3307fff3682b15f0ba3fbe13d779296d

Was this article helpful?
Tell us how we may improve it.
Yes No