Fix Parallels Desktop VM Won't Start in 2 Minutes

Quick Answer

Kill all Parallels processes, delete the VM's .pvm/Config.pvs (not the whole VM), then re-add the VM. If that fails, repair the disk image using prl_disk_tool from the Terminal.

Why This Happens

You're trying to start a VM and Parallels just sits there, or throws a generic error like “The virtual machine could not be started.” I've seen this on Windows 11 guests under Parallels Desktop 18 and 19 on macOS Sonoma and Ventura. The usual culprit? A corrupt VM configuration file or a disk image that got borked after a host crash or forced shutdown. Parallels is picky about its .pvm bundle structure — one bad XML tag in Config.pvs and it refuses to touch the VM. Don't bother reinstalling Parallels or messing with permissions first. That rarely helps. Start here.

Step-by-Step Fix

Kill all Parallels processes. Open Activity Monitor, search for “prl”, and force quit every process with “parallels” or “prl” in its name. Then quit Parallels Desktop completely. This clears file locks that block recovery.
Find your VM bundle. Go to ~/Parallels/ or wherever you store VMs. Right-click the .pvm file and select “Show Package Contents”. You'll see a Config.pvs file inside.
Rename or delete Config.pvs. Move Config.pvs to your Desktop (or rename it to Config.pvs.bak). Don't delete it permanently unless you have backups — you may need it later. With that file gone, Parallels will regenerate a fresh config when you re-add the VM.
Open Parallels Desktop. Go to File > Open and select your .pvm file. Parallels will rebuild the config automatically. It'll ask you to install Parallels Tools again if the VM was a fresh install — that's normal. Start the VM. It should boot now.
If it still fails, repair the disk image. Open Terminal and run this command, replacing “YourVM” with your VM's name:
```
prl_disk_tool compact --hdd ~/Parallels/YourVM.pvm/YourVM.hdd
```
If that errors out, try the repair option:
```
prl_disk_tool repair --hdd ~/Parallels/YourVM.pvm/YourVM.hdd
```
This fixes CRC errors in the .hdd file. I've fixed hundreds of VMs this way — it works 9 times out of 10.
Check for snapshot corruption. If you use snapshots, they can bloat the disk or get corrupted. In Parallels Control Center, click the gear icon on your VM, go to “Snapshots”, and delete any old or failed snapshots. Keep only the latest one if you must.

If the Above Fails

Disable 3D acceleration. Go to VM > Configure > Hardware > Video, and uncheck “Enable 3D acceleration”. Some Windows guests (especially Win11 with recent updates) fail to boot with 3D enabled. I've seen this on M1 Macs specifically.
Boot into safe mode (guest). Hold F8 during VM boot or use the recovery console if you can reach it. From safe mode, run sfc /scannow inside the VM. That fixes guest-side corruption that Parallels can't see.
Create a new VM from the same disk. Open Parallels, create a new VM, choose “Install Windows from a disk image”, and point it to the existing .hdd file. This sidesteps config corruption entirely. It takes 5 minutes but preserves all your data.

Prevention Tips

Don't force-quit Parallels while a VM is running. Ever. That's how config files get corrupted. Always shut down the guest OS properly, then quit Parallels. Also, keep at least one snapshot before major updates — but delete old ones every few months. Snapshot chains longer than 3-4 deep are a disaster waiting to happen. Finally, store your VMs on a local SSD, not an external drive or network share. I can't count how many times shared storage causes corruption mid-write.

Another quick tip: run prl_disk_tool check weekly on critical VMs. It's like a filesystem check for your virtual disk and catches bad sectors before they brick the whole VM.