Fusion 12 can’t use Boot Camp volume

This post was originally published on this site

Running: VMware Fusion Player Version 12.0.0 (16880131)
on software: macOS Big Sur Version 11.0 Beta (20A5364e) (latest / beta 6)
on hardware: MacBook Pro (15-inch, 2016)




Boot Camp VM from Fusion 11 encountered error: The operation on file “/dev/disk0s1” failed.

This error occurs when “Attempting to start up from: -> EFI VMware Virtual SATA Hard Drive (0.0) …”

The problem persists when starting fresh and creating a new Boot Camp VM.


All non-BootCamp VMs seem to work fine so far.


What I’ve tried:

  • Granting Full Disk Access to VMware Fusion 12
  • Deleting the VM are starting anew with VMware Fusion 12
  • Disabling SIP
  • Reset NVRAM
  • Running First Aid on all disks/volumes from Recovery Mode
  • Launching VMware Fusion as root (sudo)
  • Booted MacBook directly into boot camp partition and:
    • verified free space
    • verified no file system problems/errors
    • installed updates


Notable/relevant errors in Console App:

client     error     19:20:26.109292-1000     vmware-vmx     unable to normalize volume: “<private>”, tmp_result: <private>

client     error     19:20:26.109386-1000     vmware-vmx     Failed to get available space for volume <private>: Error Domain=CacheDeleteErrorDomain Code=10 UserInfo={Volume=<private>}

client     error     19:20:26.109509-1000     vmware-vmx     unable to normalize volume: “<private>”, tmp_result: <private>

client     error     19:20:26.109654-1000     vmware-vmx     validatedCachedResults: unable to create keyName from: {
     “CACHE_DELETE_VOLUME” = “/dev”;

(See attachment for more from Console.)


I assume this is due to some new security feature in macOS 11 preventing programs from taking control of partitions/volumes.
Is this a known issue? Is there a fix or workaround?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.