How to import a virtual machine into VMware Workstation
To import a virtual machine into VMware Workstation, you have two primary paths: open an existing VMware virtual machine file (with a .vmx extension) or import an Open Virtualization Format file (.ovf or .ova). Your immediate first step is always the same: launch VMware Workstation and use File > Open (Pro) or Player > File > Open (Player) to browse to your virtual machine files.
Prerequisites for a smooth import
Before you begin, ensure your system meets these consolidated requirements. You need VMware Workstation Pro or Player installed on your host machine. Your processor must support hardware virtualization (Intel VT-x or AMD-V) and have it enabled in BIOS. Allocate sufficient RAM and disk space for the imported virtual machine, check the source VM's disk size and add overhead for snapshots and VMware Tools. You'll also need administrative privileges on your host to modify system settings and import files. Finally, you must already possess the source virtual machine files: a .vmx configuration file for existing VMware VMs, or an .ovf/.ova package for VMs from other platforms like VirtualBox or Hyper-V. If your VM came from a non-VMware platform, export it first using that platform's export feature, ensuring you capture the disk image (VMDK is supported) and all associated configuration files.
Open or import your existing virtual machine file
This is the core verified step-by-step process. Launch VMware Workstation Pro or Player on your host machine. In Pro, navigate to File > Open; in Player, use Player > File > Open. A file browser dialog will appear.
For existing VMware virtual machines
Browse to the folder containing your virtual machine files and select the configuration file with the .vmx extension. Click Open. VMware Workstation will load the VM into its library without any conversion, it's ready to configure and power on.
For OVF or OVA packages
Browse to the .ovf or .ova file you downloaded or exported from another platform. Click Open. VMware Workstation will prompt you to provide a name for the new virtual machine and specify a destination directory for its files. Choose a location with sufficient disk space, then confirm. The import process will extract the disk images and configuration files, which may take several minutes depending on the VM's size. Note that VMware Workstation supports OVF 1.x files and VMDK virtual disks, if your OVA contains a VHD or VHDX disk, you'll need to convert it first (see the troubleshooting section below).
Review and configure imported virtual machine settings
After the import completes, the VM appears in your library but is not yet ready to boot optimally. Right-click the VM and select Settings (or go to VM > Settings). In the Virtual Machine Settings dialog, verify these critical items before first boot:
Network adapter mode
Go to the Network Adapter section. Confirm the adapter type matches your needs: Bridged for direct network access (the VM appears as a separate device on your LAN), NAT for shared internet access through your host's IP, or Host-only for isolation from the physical network. If the source VM used a specific adapter model, change it to one VMware supports (e.g., e1000, vmxnet3).
Memory and CPU allocation
In the Memory and Processors sections, adjust RAM and CPU cores to match the guest OS requirements and your host's available resources. A common mistake is leaving the imported VM with too little memory, the source platform may have used different allocation defaults.
Storage settings
Check the Hard Disk section. Verify the disk controller type (IDE, SATA, or SCSI) is compatible with the guest OS. VMware Workstation supports virtual machine hardware versions 4 through 15, if your VM uses an older version, consider upgrading it via VM > Manage > Change Hardware Compatibility to unlock newer features, but do this after confirming the guest OS boots.
Power on and install VMware Tools
Once settings are verified, select the virtual machine in the library and click the Power On button in the toolbar, or go to VM > Power > Power On. Watch the console window as the VM boots, you should see the guest OS's startup sequence. If you encounter a black screen or boot errors, refer to the troubleshooting section below.
After the OS loads, install VMware Tools for optimal driver support and host-guest integration. In VMware Workstation, go to VM > Install VMware Tools. This mounts a virtual CD containing the installer. Run it inside the guest OS and follow the prompts. VMware Tools provides essential drivers for video, networking, and mouse integration, plus features like shared folders and clipboard sharing. For Linux guests, you may need to mount the ISO manually and run the installer from a terminal. If you are setting up a retro environment, you will also want to install ms-dos 6.22 on vmware workstation before adding these drivers. Restart the VM after installation completes.
Troubleshooting a failed OVF import and other common issues
If your OVF import fails due to OVF specification conformance, the first thing to try is clicking Retry, this often resolves transient validation errors and allows the import to continue. If retrying doesn't work, verify your file matches VMware's supported formats: OVF 1.x, VMDK disks, and hardware versions 4 through 15. If your OVA contains a VHD or VHDX disk, you cannot import it directly, you'll need to convert it using a third-party tool or use vCenter Converter. Similarly, if you want to use vhd in vmware workstation from a Hyper-V export, convert the VHD to VMDK first, then import the resulting OVF package.
For network connectivity issues after import, double-check the adapter type in settings. If the VM cannot reach the internet, switch from Host-only to NAT or Bridged mode. If you need to isolate the VM for testing, configure a custom host-only network and ensure the guest OS's firewall allows the required traffic.
If the VM powers on but the OS fails to boot, verify the disk controller type matches what the guest OS expects. Windows guests often require SCSI (LSI Logic or BusLogic), while older Linux distributions may need IDE. Also check that the virtual disk file is not corrupted, compare its size to the original and ensure the path in settings points to the correct VMDK file. If you need to work with a standalone disk, you can use a vmdk file in vmware workstation as a secondary disk by attaching it to a new VM or mounting it in an existing one.
Insufficient resources manifest as slow performance or failure to allocate memory. Close unnecessary host applications, reduce the VM's RAM allocation, or increase your host's available memory. If VMware Tools fails to install, verify the guest OS is fully updated and that you have the correct Tools version for your Workstation release. For persistent issues, check the VM's log files in the virtual machine folder, they contain detailed error messages that can pinpoint the root cause.
If you're migrating a physical machine, you'll need to make a VM from your physical machine using VMware Workstation with vCenter Converter Standalone, which performs a P2V conversion and outputs a VMware-compatible VM.
Next steps with your virtual machine
With your VM imported, configured, and powered on, you can now treat it like any other VMware Workstation VM. To connect multiple VMs or isolate test environments, you'll want to setup a network in vmware workstation using the Virtual Network Editor to create custom NAT or host-only networks. For deeper integration, explore snapshotting, cloning, and linked clones to streamline your workflow. If you need to move the VM to another host, use File > Export to OVF to create a portable package. For more advanced tasks, refer to our guides on configuring shared folders, enabling 3D acceleration, or automating VM startup with Workstation's command-line tools. Your imported VM is now fully operational, leverage VMware Workstation's power to test software, simulate environments, and run multiple operating systems side by side.
For the wider topic, see use vhd in vmware workstation.
