Page 1 of 1
Bluetooth mouse not captured
Posted: 4. Dec 2016, 14:20
by dwpman
I have just updated my host system to Sierra OS (Mac) only to discover that when I open my Windows 10 guest in the latest build of VB, the bluetooth mouse I am using is not captured. I have tried an older version of VB but still the bluetooth mouse is not available.
Anyone else encountered this problem? And does anyone have a work-round?
Re: Bluetooth mouse not captured
Posted: 4. Dec 2016, 15:01
by socratis
dwpman wrote:latest build of VB
dwpman wrote:an older version of VB
Versions please. Exact.
Re: Bluetooth mouse not captured
Posted: 4. Dec 2016, 16:18
by dwpman
Hi, VB is current version 5.1.10 plus extensions pack...Windows is 10 Pro 64 bit. To try to overcome the problem I have tried VB 5.1.6 and 5.1.8 but neither of them captures the mouse.
This problem has happened since my OS upgrade. I formerly had Mac OS Yosemite on my MacBook Pro host and everything worked fine. I upgraded to Sierra OS yesterday on my Mac and now, when I launch VB, the mouse loses connection as VB loads the guest system.
Re: Bluetooth mouse not captured
Posted: 6. Dec 2016, 21:53
by scottgus1
Virtualbox capturing a mouse is a host OS thing, not a guest OS thing, So I'd suspect this is a Mac Hosts forum issue, not Windows Guests.
But are there new drivers you can download for the Bluetooth mouse?
This:
when I launch VB, the mouse loses connection
doesn't mean the same as this:
when I open my Windows 10 guest...the bluetooth mouse I am using is not captured.
So is the connection lost, as in the mouse doesn't work at all when the Virtualbox guest is started?
Or when you say "capture" do you mean the mouse used to normally constrict itself into the guest window and not come out until you hit the host key on the keyboard? Or does the mouse input not activate anything in the guest OS?
Not a Mac guy here, just happened along and had some thoughts...
Re: Bluetooth mouse not captured
Posted: 6. Dec 2016, 22:19
by socratis
Scott had some great thoughts. Please answer his questions, because I'm reading your posts over and over again and I'm not sure I understand what the problem is.
Re: Bluetooth mouse not captured
Posted: 7. Dec 2016, 18:33
by dwpman
Hi, thanks for the suggestions and queries. Before the upgrade to Mac OS Sierra, VB worked fine and the bluetooth mouse worked fine within the Windows 10 guest and was not confined to the guest, but operated with the Mac host as well. Now, with the Sierra OS, as VB launches, I get the notification from the mouse that connection is lost...VB then continues to launch and everything works apart from the bluetooth mouse. I can use the MacBook trackpad and I can plug in a USB mouse and work with that in VB, but not the bluetooth mouse.
I think you might be right, it seems to be a Mac host thing. I can't trace any new drivers for the bluetooth mouse (it's a Kensington Suretrack) and though an Apple bluetooth host controller is listed and ticked in the Ports/USB window in VB management, it is not allowing the mouse to work.
Just wondering if anyone else has encountered the same issue. As I say above, I can use a USB mouse, or the trackpad, so the loss of the bluetooth mouse is no big deal. Thanks for your interest and help.
Re: Bluetooth mouse not captured
Posted: 7. Dec 2016, 18:41
by scottgus1
dwpman wrote:an Apple bluetooth host controller is listed and ticked in the Ports/USB window in VB management
If this means that your guest USB filters show the blutetooth controller as a filtered device in this window:

- Virtualbox USB filters.PNG (22.56 KiB) Viewed 4468 times
Then it shouldn't be ticked. The guest is taking the Bluetooth mouse from the host, but it doesn't know what to do with it.
Maybe you could post a PNG of what you see?
Re: Bluetooth mouse not captured
Posted: 8. Dec 2016, 00:00
by dwpman
Hey, I have followed your post and unticked the Apple bluetooth USB host controller and voila the bluetooth mouse is working!
Brilliant! Thanks so much!
Re: Bluetooth mouse not captured
Posted: 8. Dec 2016, 14:33
by scottgus1
Glad you got it working again!