Available article translations:

How to use Mac Bluetooth in virtual machine?

  • Parallels Desktop 11 for Mac Home Edition
  • Parallels Desktop 10 for Mac Home Edition
  • Parallels Desktop 9 for Mac Standard Edition
  • Parallels Desktop 8 for Mac Standard Edition


I would like to connect my Bluetooth device straight to the virtual machine. How can I do that?


The functionality has been implemented since Parallels Desktop 8 to share the Host (Mac) Bluetooth connection with virtual machine.

In order to switch on the sharing:

  1. Open virtual machine configuration > Switch to Hardware > USB & Bluetooth and enable Share Bluetooth devices with Windows:


With Bluetooth sharing you can:

  • Search for devices;
  • Lookup advanced device data;
  • Lookup the list of profiles, supported by the device;
  • Couple virtual machines with the device;
  • Send/Sync files;
  • Use com-port, modem, etc.

IMPORTANT: On Parallels Desktop 12 due to stability reasons it is not recommended to assign Apple Bluetooth USB Host Controller manually to the virtual machine, please use Share Bluetooth devices with Windows feature as mentioned above.

NOTE: In case Apple Bluetooth USB Host Controller functionality is vital for your experience, please use the instructions from the following article:

Unable to use Apple Bluetooth USB Host Controller in virtual machine

NOTE: The remotely connected Bluetooth device doesn't recognise virtual machine as a separate device, it recognises only Mac.


  • You can initiate coupling of virtual machine and device only at the virtual machine side;
  • You can initiate files sending/syncing only at the virtual machine side. Files, sent from the device will be received by the Mac.

Supported guest Operating Systems:

  • Windows XP and higher;
  • Mac OS 10.5.x and higher;
  • Linux.


  • Bluetooth Syncronization Profile is not supported (being used in Bluetooth Handsfree and Headphones)
  • Secure Simple Paring authentication method is not supported;
  • ActiveSync profile is not supported (Used in Windows Mobile devices).

97cd84747b25a2e5a06065a21a747a53 1e5db16426987d561060acdf56d947b4 a9c6e0b6a5209e617a7c0dd5eace86cf 3307fff3682b15f0ba3fbe13d779296d 39e36b0abb33520c52ec8a15b563c41d 97a8ac9f376ccb34ff8a388d158b8d2e

Was this article helpful?
Tell us how we may improve it.
Yes No