Parallels Desktop disables iSight Camera on Macbook Pro with OS X Sierra

BorisP1

Bit poster
After I upgraded from OS X El Capitan to Sierra, whenever Parallels desktop starts, it disables built in camera on my MacBook Pro. After laptop boots, camera works with any application (photo booth, facetime, skype, vydio, etc), but as soon as I start Parallels, camera stops working (green light stops coming on). It happens without starting any virtual machines. I had Parallels 11, then I paid $49 and upgraded to 12 -- no difference. After I reboot, camera works as long as I do not start Parallels Desktop. My laptop is 2012 Retina MacBook Pro.
 
same thing happens on 2012 MacBook Air. camera works fine, until you start parallels, then it fails. happens every single time.
 
I have the same situation and after start a virtual machine the camera cannot work with any other applications.
 
I am trying VMWare (cost me 80.00 to upgrade an old license), wish me luck I perfer Parallels over VMWare but I got to get the issue resolved
 
I have tried the VMware in test version but always the same problem. The only virtualizer software without this matter is VirtualBox (on my MBP 2012), but I prefer Parallels
 
camera hardware has not change, the app that controls it has had minor changes (El Capitan and Sierra) codebase, this is really a Parallels issue they certify against apple not the other way around! Does anyone from Parallels read these posts? Just asking
 
I have the same issue! Techincian checked my computer remotely today also, I hope it can be solve.
Actually, this issue start from OS X 10.11 BETA but after release of 10.11 is no problem.
OSX 10.12 BEAT happened again until now even more serious, in my case, reboot can't solve this problem!
Temperately, I solve it by this way below...
1. Shutdown PARALLELS.
2. open Terminal
3. sudo rm Library/Preferences/com.apple.FaceTime.plist
4. reboot
And then you can use the built in camera, but it will disable again after you start again PARALLELS.
 
Hi,
Unfortunately it appears to be a problem on Mac OS Sierra and MacbookPro10,1. So far there is no known workaround. The main version is that it is an issue of Mac OS. We are working on it.
 
Back
Top