VMware Fusion Black Screen After macOS Update – Fixed

You just updated macOS to Ventura or Sonoma, and now your VMware Fusion virtual machine boots to a black screen. The cursor moves, you hear the guest OS chime, but the display stays dark. This is a known issue, and the culprit is almost always the graphics driver or the VMware kernel extension being out of sync with the new macOS version.

Why This Happens

macOS updates change the kernel and graphics subsystem. VMware Fusion relies on kernel extensions (kexts) and a custom display driver that talks directly to the guest OS. When macOS updates, those extensions can get disabled or fail to load properly. The result? The VM starts, the guest OS runs, but no video output. It's not a hardware problem, and it's not your VM being corrupt. It's a software handshake that broke.

I've seen this on every major macOS update since Big Sur. The pattern is always the same: black screen after reboot, VM still alive (you can SSH in or hear sounds), but no display.

The Fix – Step by Step

Step 1: Reinstall VMware Tools

VMware Tools is the driver package that gives you proper graphics, mouse integration, and shared folders. When it's broken, you get a black screen. Here's how to reinstall it from the host:

1. Boot the VM with the black screen. Don't force quit. Let it sit for 30 seconds.
2. From the Fusion menu go to Virtual Machine > Install VMware Tools. This mounts a virtual CD.
3. If you can't see the VM, use the keyboard shortcut Ctrl + Opt + T to toggle the menu bar. Then press Ctrl + Opt + Enter to enter full screen—sometimes the display flashes on.
4. In the guest OS (say Windows), press Win + R, type D:\setup.exe and hit Enter. The installer should launch.
5. Choose Modify or Repair, then reboot.

If the guest is Linux, you'll need to SSH into it and run sudo vmware-config-tools.pl after mounting the ISO. That's your fallback if the black screen stays.

Step 2: Reset Graphics Settings in Fusion

Sometimes the issue is just a stale graphics config. Do this:

1. Shut down the VM (force quit if you must).
2. Go to ~/Library/Preferences/VMware Fusion/ and delete the file called preferences. It'll regenerate on next launch.
3. Open Fusion, select the VM, click Settings > Display.
4. Uncheck Accelerate 3D graphics. Apply.
5. Boot the VM. If it works now, the 3D acceleration was the problem. You can try re-enabling it later after a Tools reinstall.

Step 3: Force Load Kernel Extension

macOS sometimes blocks VMware's kext after a security update. To fix that:

1. Open System Settings > Privacy & Security.
2. Scroll down to Security. You'll see a message like System software from developer "VMware, Inc." was blocked from loading.
3. Click Allow next to that message. You'll need to enter your admin password.
4. Reboot your Mac, then try the VM again.

If you don't see that message, open Terminal and run:

sudo kmutil load -p /Library/Extensions/vmmon.kext

That forces the kernel extension to load. If it fails with a permissions error, you need to allow it via the security panel first.

Step 4: Switch to UEFI Boot (Legacy Users)

Some older VMs set to BIOS boot get confused after a macOS update. Change it to UEFI:

1. Shut down the VM.
2. Go to Virtual Machine > Settings > General.
3. Under Boot, select Firmware Type and choose UEFI.
4. Apply and boot.

If It Still Fails

First, check if the VM actually boots. Use SSH from your Mac: ssh user@vm-ip. If you can log in, the guest is alive—the problem is purely graphical. In that case, reinstall VMware Tools using the command line inside the guest.

For Windows guests, try this in an admin PowerShell session:

Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA" -Value 0

Then reboot. That disables UAC, which sometimes blocks the Tools installer. Re-enable it after the fix.

If nothing works, downgrade VMware Fusion to the version that came before your macOS update. You can find older builds on VMware's site. I've had to do that twice in 14 years. It's rare, but it happens.

One last thing—check if your VM has enough RAM. Fusion can trip over itself with less than 2GB allocated. Give it at least 4GB if you can spare it.