Bluetooth virtual com port not openable in Windows 10. Last worked in 8.1.
How do I add a Bluetooth COM port in the Win8 Device Manager? Unless the driver supports the Bluetooth Serial Port Profile, you’re out of luck. However, in your screenshot, the “COM Ports” tab is available. If the COM port on your PC is properly exported and is.
Symptom: I am an application developer and have tried my application on two computers I just upgraded to Windows 10 (an Acer W510 tablet formerly win 8.1 and a Dell Precision M6600 formerly win 7). Our devices use a serial port (SPP) service on Bluetooth.
Windows automatically creates the serial ports when pairing the devices. The devices pair well and the necessary virtual serial ports are created. They all look great but on both computers, no software is able to open the serial port. (I must say: I do like Windows 10 even though I have already seen a 'blue screen'.) tried: - my commercial software - a test application written in Visual Studio Express 2013 - a test application written in Delphi - terminal software that would open a serial port and talk with the device the serial port connection can't be opened due to an error 1168 (ERRORNOTFOUND) in CreateFile( ). As I said, this affects both machines that I upgraded to the official release of Windows 10. POSSIBLE CAUSES: Security/permissions?
Turned off UAC (user account control); still doesn’t work. User account is Administrator. Tried a new Administrator account (possible account corruption?): no improvement.
Might this be part of a new “windows store” expectation where applications must declare the operating system features they intent to use? This would be a little bit strange since it allowed pairing/unpairing with code. Change to application manifest?
Turned off firewall; still doesn’t work. Is the radio off as some kind of power-saving feature?
![]()
Having trouble determining whether this is the case. One would think that if one attempted to open such a serial port, it would turn on the radio as needed.
Tried also a laptop not having built-in bluetooth (really!); using external BT dongle, see BT module indicator is blinking (suggesting it is powered-up and operational). Add something to the application manifest?
Is the com port busy? Shouldn't be. Besides, then it should say that the port is in use or “access denied”. Any “allow windows to turn off the device to save power” features are turned off on relevant devices. No improvement. Acer W510 Device manager shows some motherboard features (nothing to do with USB/bluetooth or our devices) that may not have suitable device drivers. The Dell laptop has no Device Manager issues (but has the same inability to use the virtual com port) suggests that these driver issues are not 'the' problem.
“Allow Bluetooth devices to find this PC” is not helpful. “Bluetooth Smart”, “Bluetooth Smart Ready” feature may be implicated in this but don't know enough about them. Using 'Developer mode' provided no insight. Using compatibility mode was no help either.
Starting to think maybe the driver provided by Windows is not compatible with the Bluetooth hardware in the device. Other people experiencing this problem: can you leave a comment here about any of your findings?
Pairing a Bluetooth Device that supports BT-SPP Profile, Windows 10 is automatically adding incoming & outgoing Virtual Com-Ports to the system (this step is a success). Incoming COM port works but Outgoing port fails to open the virtual COM port (tried with many applications and drivers bluetooth and COMM). Due to problems in Windows 10 handling virtual serial ports with class SPP it's unfortunatelly not as straight forward as it has been with Windows 7 / 8. If you're writing your own applications for Windows 10 you simply use the class 'RFCOMM' instead of 'SPP' to communicate with the bluetooth device and then you bypass the error.
Or use an external Serial - Bluetooth adapter Or wait until Microsoft fixes this problem Jean-Louis Jean-Louis. Hi, I apologize for the inconvenience caused. I suggest you to try installing the Qstarz Bluetooth GPS logger driver/software in compatibility mode and check if it works for you.
This is to check if this is caused due to any driver/software compatibility. Refer to the following Microsoft Help article to install driver/software in compatibility mode, the steps for Windows 8.1 applies to Windows 10 as well. Please feel free to visit our website for any help with Windows Operating System. Basith M - Forum Moderator (Multiple Forums).
I would mean if you install the version from the repository (ending with OSE, the versions from the repository are open source and has not support for USB), i suggest you uninstall the current version and follow this link, this will install the last version of Virtualbox free but not open source with support for USB. Just in case you are running Intrepid Ibex 8.10 you can select from the link the Hardy repositories that works OK in my case Be sure to add the refered repositoy to your sources and also the key as indicates the link.
I have version 2 and it supports usb but I dont know how to use it. Go to System - Administration - Users & Groups. Unlock 'Users Settings' using the 'Unlock' button near the lower right of the box (next to the close button). Click on 'Manage Groups'. Click on '+ Add Group'.
In the 'Group Name' text box, type 'usbuser'. IMPORTANT: Write down the Group ID number on a piece of paper. You'll need this later!. Click on your user name in the 'Group Members' table - a check mark will appear in front of the user name. Do this for each user you wish to allow USB access in VirtualBox. Click OK, and then Close, then Close again.
Now, open Applications - Accessories - Terminal. Type 'gksudo gedit /etc/fstab' (without the quotes). Add following lines to the end of the file. Go to System - Administration - Users & Groups. Unlock 'Users Settings' using the 'Unlock' button near the lower right of the box (next to the close button).
Click on 'Manage Groups'. Click on '+ Add Group'. In the 'Group Name' text box, type 'usbuser'.
IMPORTANT: Write down the Group ID number on a piece of paper. You'll need this later!. Click on your user name in the 'Group Members' table - a check mark will appear in front of the user name. Do this for each user you wish to allow USB access in VirtualBox. Click OK, and then Close, then Close again. Now, open Applications - Accessories - Terminal.
Type 'gksudo gedit /etc/fstab' (without the quotes). Add following lines to the end of the file. Code: # For USB access with Virtualbox none /proc/bus/usb usbfs devgid=1001,devmode=664 0 0. IMPORTANT: Replace 1001 with the Group ID number that you wrote down earlier.
Save the edited file (File - Save) and then exit gedit. Reboot your system. Make sure you've enabled USB Controller in VirtualBox. Enjoy USB goodness in VirtualBox I tried this setup with VB in 8.10. The Group ID that was assigned was 1001. Upon following all the steps I still cannot read USB flash drives.
The printer is recognized as a USB device but nothing else. Any other info you would need? Edit: I was not running the PUEL version but the one through Synaptic. It did have options for USB but they did nothing to make it work. Last edited by 73ckn797; November 11th, 2008 at 03:05 AM. Reason: Update. Go to System - Administration - Users & Groups.
Unlock 'Users Settings' using the 'Unlock' button near the lower right of the box (next to the close button). Click on 'Manage Groups'. Click on '+ Add Group'. In the 'Group Name' text box, type 'usbuser'.
IMPORTANT: Write down the Group ID number on a piece of paper. You'll need this later!. Click on your user name in the 'Group Members' table - a check mark will appear in front of the user name. Do this for each user you wish to allow USB access in VirtualBox. Click OK, and then Close, then Close again.
Now, open Applications - Accessories - Terminal. Type 'gksudo gedit /etc/fstab' (without the quotes). Add following lines to the end of the file. Code: # For USB access with Virtualbox none /proc/bus/usb usbfs devgid=1001,devmode=664 0 0. IMPORTANT: Replace 1001 with the Group ID number that you wrote down earlier. Save the edited file (File - Save) and then exit gedit.
Reboot your system. Make sure you've enabled USB Controller in VirtualBox. Enjoy USB goodness in VirtualBox I've followed your steps accurately, but during the reboot, the ubuntu welcome screen showed me the error: 'mount point /proc/bus/usb does not exist' and a choice between skipping that mount operation and manually mounting it. Looking under /proc/bus I found only those folders: input pccard pci I'm trying to enable bluetooth on virtual box v3.2.8 so that I can use it on my windows XP VM. If I enable bluetooth on the ubuntu host, it is shown as dimmed (unavailable) on the VM menu under USB devices, and if I disable it, it is not shown at all.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |