VMware Communities
drmarc
Contributor
Contributor
Jump to solution

Fusion 8.5 - macOS Sierra 10.12 (GM) - MacBook Pro Camera Malfunction

I was waiting to report this until both Fusion 8.5 and the Sierra golden master were out, but the problem persists.

I have a Mid 2012 Retina MacBook Pro with a built-in FaceTime HD Camera (UVC Camera VendorID_1452 ProductID_34064).

After I start a virtual machine the camera cannot be turned on by any other application (FaceTime, Photo Booth, Skype).  The camera remains unresponsive even after shutting down virtual machines and quitting Fusion, until I reboot the MacBook.  If another app is using the camera when I start a Fusion VM, the camera continues to work until I close the other app, then it will not reactivate if I restart the other app.

Has anyone else experienced this?  Can anyone suggest a resolution?  I'm happy to provide more information if necessary.  Thanks!

Tags (3)
41 Replies
rodegaard
Contributor
Contributor
Jump to solution

It appears that this problem has been going on for at least a year now. I upgraded from Fusion 8.x in the hopes of fixing the issue but no joy.

I can confirm that I'm using High Sierra 10.13.1 and Fusion 10.0.1 (6754183) on a MacBook Pro Mid-2012 and the camera problem persists.

Come on VMware, how hard can this be to fix?

Rick

Reply
0 Kudos
jimsold
Enthusiast
Enthusiast
Jump to solution

I am running the latest release of High Sierra and the latest release of Fusion 10.

This problem persists for me!!

  Model Name:MacBook Pro
  Model Identifier:MacBookPro10,1
  Processor Name:Intel Core i7
  Processor Speed:2.6 GHz
  Number of Processors:1
  Total Number of Cores:4
  L2 Cache (per Core):256 KB
  L3 Cache:6 MB
  Memory:16 GB

Really annoying as I can use the Zoom client to have video during a meeting if Fusion is open.

Even if I shut Fusion down, the camera does not come back. I have to reboot and then the camera works until I launch Fusion again.

I guess VMware is blaming Apple for this persistent issue.

It's 2018!! Time for a fix.

Reply
0 Kudos