Error starting machine: Error in driver during machine start

RajeshKumar1

INFO Loading bundle: crc_hyperv_4.17.3_amd64...
DEBU Checking file: C:\Users\uday.crc\machines\crc.crc-exist
DEBU Machine: libhvee -> state
DEBU Machine: libhvee -> get machine
DEBU Machine: libhvee -> state: get
DEBU Machine: libhvee -> state: stopped
DEBU Copying 'C:\Users\uday.crc\cache\crc_hyperv_4.17.3_amd64\oc.exe' to 'C:\Users\uday.crc\bin\oc\oc.exe'
DEBU Copying 'C:\Users\uday.crc\cache\crc_hyperv_4.17.3_amd64\podman.exe' to 'C:\Users\uday_.crc\bin\podman\podman.exe'
INFO Starting CRC VM for openshift 4.17.3...
DEBU Updating CRC VM configuration
DEBU Machine: libhvee -> get machine
DEBU Machine: libhvee -> start
DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" -Name ReleaseId).ReleaseId'
DEBU Running '(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").EditionID'
Error starting machine: Error in driver during machine start: failed to start vm: Job failed with error code: 32788 ()

RajeshKumar1

The error you're encountering:

Error starting machine: Error in driver during machine start: failed to start vm: Job failed with error code: 32788 ()

is commonly related to Hyper-V permissions or configuration issues when trying to start the CRC (CodeReady Containers) VM for OpenShift.

✅ Step-by-Step Fixes:

1. Run CRC with Admin Privileges

Make sure you are running the terminal (PowerShell or CMD) as Administrator.

2. Verify Hyper-V is Enabled

Open PowerShell as Administrator and run:

  Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

If not enabled, enable it:

  Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

Reboot your system afterward.

3. Check Hyper-V Virtual Switch

Ensure that a virtual switch exists and is working:
- Go to Hyper-V Manager → Virtual Switch Manager.
- Create an external virtual switch linked to your active network adapter (Ethernet or Wi-Fi).

If CRC is unable to create a switch, create it manually and specify it in the config:

crc config set network-mode user

Or for external switch:

crc config set network-mode vswitch
crc config set vswitch-name "YourSwitchName"

4. Clean and Re-setup CRC

Sometimes a stale or corrupted VM causes issues.

crc delete --force
crc cleanup
crc setup
crc start

5. Check Windows Version Compatibility

CRC v4.17.3 may have issues with older or very new Windows versions. Run:

(Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").ReleaseId

Ensure you're on a stable version like Windows 10 21H2 or Windows 11 stable builds.

6. Disable Any Conflicting Virtualization (e.g., WSL2 or VMware)

Disable or ensure there's no conflict with:

WSL2 backend
VMware Workstation or VirtualBox with Hyper-V

🔧 Additional Debug Option

Enable verbose logging and check the full trace:

crc start -l debug