Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstalliTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
How you import a virtual machine into VMware Workstation depends on the files you have: export a VirtualBox VM as an OVA, open an existing Workstation .vmx configuration, or create a new VM around a remaining .vmdk disk. Identify the file first; the workflows are not interchangeable.
Choose the workflow for your VM files
| What you have | What to do |
|---|---|
| A VirtualBox VM | Shut it down, export it as an OVA, then import the OVA into Workstation. See Broadcom’s VirtualBox migration instructions. |
A Workstation .vmx file |
Open the configuration in Workstation with File > Open. The cited example is tied to a Workstation Pro 17.5.1 scenario, so treat it as an example rather than a description of every current import case. See Broadcom’s VMX example. |
A .vmdk disk but no usable .vmx |
Create a new VM and select the existing virtual disk. Keep any child VMDK files alongside the selected disk. See Broadcom’s existing-VMDK guidance. |
| A native Workstation VM that needs a new location | Copy or move its powered-off folder rather than converting it. This is a relocation workflow, not an import of a foreign package. See Broadcom’s copy/move instructions. |
Menu names and controls can vary by Workstation and VirtualBox release. Use the instructions below as a guide, and confirm labels in the versions installed on your computer.
Import a VirtualBox VM using an OVA
An OVA packages a VM for transfer. Broadcom’s documented sequence is to shut down the VirtualBox guest, export it as an OVA, and then import that file into Workstation.
Recommended Free Tools
- Shut down the VM in VirtualBox. If it is suspended, start it and shut it down before exporting.
- Export an appliance. In VirtualBox, use File > Export Appliance, select the VM, choose OVA as the archive format, and export. The exact labels may differ in newer releases.
- Import the OVA in Workstation. Open the exported OVA using Workstation’s import workflow. Follow the prompts to create the VM.
- Replace the guest integration tools. After import, remove VirtualBox Guest Additions, restart the guest, and install VMware Tools.
Export time depends on the virtual disk’s size. Broadcom documents “Retry with lower specifications” as a first step when Workstation reports that an OVA failed OVF specification conformance or virtual-hardware compliance checks. It is not a guaranteed fix for every package or Workstation version.
#1 Best Overall
For the source procedure, see Broadcom’s VirtualBox-to-Workstation migration article.
Open an existing Workstation VMX file
If the VM folder contains a usable .vmx file, open Workstation and choose File > Open, then select that configuration. Broadcom’s example prompts the user to choose a new VM name or location. Its context is a specific Workstation Pro 17.5.1 issue, so current prompts and behavior may differ by release.
Rebuild the VM configuration around a VMDK
If the .vmx file is missing or damaged but the virtual disk remains, create a new VM and choose the option to use an existing virtual disk. Select the appropriate .vmdk file and keep any child VMDK files in the same folder as the selected disk.
Attaching an existing disk can lock it against use by another VM. If the original VM still needs the disk, copy the disk files first and attach the copy. Broadcom’s instructions are at Creating a Workstation virtual machine using existing VMDK virtual disks.
Move or copy a native Workstation VM
For a native Workstation VM that only needs to move to another folder or drive, copying its VM folder while it is powered off may be simpler than importing or converting it. A copy made while the VM is powered on or suspended may fail to boot.
At first launch, Workstation asks whether the VM was moved or copied:
- Moved It retains the VM identity and settings.
- Copied It generates a new UUID and MAC address to help avoid identity conflicts.
Choose according to whether this is the same VM in a new location or a separate copy. See Broadcom’s copy/move guidance.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Check the VM settings after import or repair
Review the configuration before relying on the VM. The relevant settings depend on the guest operating system, host capacity, and intended workload; there are no universal memory or processor values that fit every machine.
- Guest operating system selection
- Virtual hardware compatibility
- Memory and processor allocation
- Virtual disk capacity
- Network configuration
Broadcom’s VM creation guidance covers these configuration areas. The page lists older Workstation generations, so verify exact controls in your installed version.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
