Who This Is For
- • Dominator EFI users on ARM hardware
- • Mac + Windows VM setups
- • USB CAN communication and ECU sync issues
Dominator EFI on MacBook Pro 14 M3 Max Troubleshooting Guide
Use this page when Holley Dominator EFI fails to detect hardware, connect to ECU, or complete driver setup on MacBook Pro 14 M3 Max. Steps are tailored to your product and ARM-specific workflow.
Your Device Specs
- • Device: MacBook Pro 14 M3 Max
- • Processor: M3 Max
- • Platform: Windows 11 ARM via virtualization
Supported Hardware
- • All engine types
- • Forced induction
- • Nitrous systems
- • All transmission types
Common Errors and Fixes
Holley Dominator EFI cannot detect USB CAN device
Symptom: The software opens, but your ECU or USB CAN adapter does not appear as connected.
Likely Cause: USB passthrough is not assigned to the Windows 11 ARM virtual machine.
- 1. Open your VM settings and confirm USB device passthrough is enabled.
- 2. Reconnect the USB CAN adapter and attach it to Windows (not macOS).
- 3. Re-run iCANDrivers installer inside Windows and reboot the VM.
- 4. Launch the tuning software again and verify COM/USB device detection.
Holley Dominator EFI opens but fails to connect to ECU
Symptom: You can start the app, but live data and ECU sync fail or time out.
Likely Cause: Incorrect communication selection, unstable power on ECU side, or cable/port quality issue.
- 1. Confirm ECU and adapter power are stable before opening software.
- 2. Use a short, direct USB cable and avoid passive hubs.
- 3. Select the correct communication interface in software settings.
- 4. Try a second USB port on MacBook Pro 14 M3 Max and retry ECU handshake.
iCANDrivers installer runs but setup does not complete
Symptom: Installer exits early, or software still behaves as if no driver is installed.
Likely Cause: Security policy, antivirus interference, or stale prior install state.
- 1. Close tuning software before running the installer.
- 2. Run installer as Administrator in Windows 11 ARM.
- 3. Temporarily pause overly strict endpoint protection during install.
- 4. Restart Windows session after install and retest connection.
Still Stuck?
If these fixes do not resolve your issue, contact support with your exact tool, device, and error behavior. We offer a 30-day money-back guarantee.