locked
Bluetooth for Windows Server 2008 R2

    Question

  • Has anyone gotten a full blue tooth stack to work on Windows Server 2008 R2 yet? There appears to be basic BT functionality to run a BT mouse, but in my case, I'm running on Broadcom BT hardware, and haven't found anything that works. There was a procedure for Windows Server 2008 (not R2), but some have reported that that procedure doesn't work. Any thoughts or experiences?
    Thanks,
    MW61
    • Edited by MW61 Tuesday, October 13, 2009 5:15 PM
    Wednesday, September 02, 2009 4:36 PM

Answers

All replies

  • Hi,

     

    Have you installed the driver?

     

    Please have a look at the following post(Gil Kirkpatrick's reply), it may be helpful.

     

    Windows Server 2008 and Bluetooth

    http://social.technet.microsoft.com/Forums/en-US/winserverPN/thread/fd2b1573-9836-4ddb-90b6-e6c08b31a2c8

     

     

    Best Regards,

    Vincent Hu

     

    Thursday, September 03, 2009 9:55 AM
    Moderator
  • I have not tried installing the drivers per the article you reference. I'm looking to see if anyone has tried the various methods documented for Window Server 2008 RTM with R2. So far, I've seen some commentary that it does not, but very little exists. Plus R2 comes w/ a rudimentary BT stack which seems to work w/ some BT mice. Any thoughts?
    Thanks,
    MW61

    Tuesday, September 08, 2009 1:44 PM
  • I've tried the methods refered to here which worked for Windows Server 2008, but appears not to work for Windows Server 2008 R2 x64. Anyone have any ideas on how to get Bluetooth to work with R2?

    Tuesday, October 13, 2009 5:14 PM
  • I've got a Dell Bluetooth Keyboard and Mouse that seem to work perfect for me in R2 on two different servers.  Not sure you are referencing the basic keyboard and mouse setup, but thought I would throw that out there.  I've never had to install any BT software to get them to work either. I just basically "P&P" and they work fine.  What specifically are you trying to get to work on the R2 server that is BT?
    Thursday, October 15, 2009 6:39 PM
  •  

     

    I found a way finally to make Nokia PC Suite program sync with Microsoft Outlook through Bluetooth on Windows Server 2008 R2 platform.

    If you have Bluetooth devices that work with Microsoft drivers of Windows 7 x64, you can make it to work under Windows Server 2008 R2.

     
    The bad part is that you need to hit F8 and select “Disable Driver Signature Enforcement” every time you reboot your system.

     

    Step 1: Collect files from Windows 7 x64 and modify the INF files

     

    I have packed all the required files from Windows 7 x64; you can download the Win7Bth.zip file from http://www.infoking.com.cn/Win7Bth.zip  and go to step 2 directly.

     

    Here is the detail files collection procedure:

     

    Copy the following files from Windows 7 x64 to a folder named “Drivers” in an USB flash drive.

     

    From C:\Windows\inf folder:

     

    bth.inf

    bthmtpenum.inf

    bthpan.inf

    bthprint.inf

    bthspp.inf

    hidbth.inf

    mdmbtmdm.inf

    netirda.inf

    tdibth.inf

     

    In your Drivers folder, Please use Notepad to open these INF files one by one and replace all “NTamd64...1” to “NTamd64” and save it again.

    This is very important steps; the “NTamd64...1” is specific to Windows 7 and “NTamd64” is for generic x64 platform including Windows Server 2008.

     

    Note: After we modified these INF files, The Bluetooth files and drivers will not pass driver signature requirement for Windows Server 2008.

     

    From C:\Windows\System32\Drivers folder:

     

    bthenum.sys

    bthmodem.sys

    bthpan.sys

    bthport.sys

    BTHUSB.SYS

    hidbth.sys

    irda.sys

    rfcomm.sys

     

    From C:\Windows\System32 folder:

     

    fsquirt.exe

    wshbth.dll

     

     

    Copy the following files from Windows 7 x64 to a folder named “System\x64” in an USB flash drive.

     

    From C:\Windows\System32 folder:

     

    bthci.dll

    BthMtpContextHandler.dll

    bthpanapi.dll

    BthpanContextHandler.dll

    bthprops.cpl

    bthserv.dll

    bthudtask.exe

    btpanui.dll

    collab.cpl

    fdBth.dll

    fdBthProxy.dll

    irftp.exe

    irmon.dll

    irprops.cpl

    wshbth.dll

    wshirda.dll

     

     

    Copy the following files from Windows 7 x64 to a folder named “System\x64\migration” in an USB flash drive.

     

    From C:\Windows\System32\migration folder:

     

    bridgemigplugin.dll

     

     

    Copy the following files from Windows 7 x64 to a folder named “System\x86” in an USB flash drive.

     

    From C:\Windows\SysWOW64 folder:

     

    bthprops.cpl

    bthudtask.exe

    btpanui.dll

    fdBth.dll

    fdBthProxy.dll

    irprops.cpl

    wshbth.dll

    wshirda.dll

     

     

    Copy the following files from Windows 7 x64 to a folder named “System\x86\migration” in an USB flash drive.

     

    From C:\Windows\ SysWOW64 \migration folder:

     

    bridgemigplugin.dll

     

     

    Copy the following files from Windows 7 x64 to a folder named “cat” in an USB flash drive.

     

    From C:\Windows\servicing\Packages folder:

     

    Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.cat

    Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.mum

    Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.cat

    Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum

     

     

    Make a regbth.bat text file under folder “System” in an USB flash drive.

     

    Use Notepad to type following content and save it.

     

    cd c:\windows\sysWOW64

     

    regsvr32 fdBthProxy.dll

    regsvr32 btpanui.dll

     

    cd c:\windows\system32

    regsvr32 BthpanContextHandler.dll

    regsvr32 fdBthProxy.dll

    regsvr32 btpanui.dll

     

     

    Make a bth.reg text file under folder “Registry” in an USB flash drive.

     

    Use Notepad to type following content and save it.

     

    Windows Registry Editor Version 5.00

     

    [HKEY_CLASSES_ROOT\CLSID\{61F7B364-432C-4D04-BBC1-7FC1BF3807A8}]

    @="Bluetooth Bluewire Shell property extension object"

     

    [HKEY_CLASSES_ROOT\CLSID\{61F7B364-432C-4D04-BBC1-7FC1BF3807A8}\InprocServer32]

    @="C:\\Windows\\System32\\bthprops.cpl"

    "ThreadingModel"="Apartment"

     

    [HKEY_CLASSES_ROOT\CLSID\{F08C5AC2-E722-4116-ADB7-CE41B527994B}]

    @="Bluetooth Authentication Agent SSO"

     

    [HKEY_CLASSES_ROOT\CLSID\{F08C5AC2-E722-4116-ADB7-CE41B527994B}\InprocServer32]

    @="C:\\Windows\\System32\\bthprops.cpl"

    "ThreadingModel"="Apartment"

     

    [HKEY_CLASSES_ROOT\DeviceDisplayObject\AllItems\shellex\PropertySheetHandlers\{61F7B364-432C-4D04-BBC1-7FC1BF3807A8}]

    @="Bluetooth services Property Sheet"

     

    [HKEY_CLASSES_ROOT\PairingFolderItemBluetooth]

     

    [HKEY_CLASSES_ROOT\PairingFolderItemBluetooth\shellex]

     

    [HKEY_CLASSES_ROOT\PairingFolderItemBluetooth\shellex\PropertySheetHandlers]

     

    [HKEY_CLASSES_ROOT\PairingFolderItemBluetooth\shellex\PropertySheetHandlers\{61F7B364-432C-4D04-BBC1-7FC1BF3807A8}]

    @="Bluetooth Services Property Sheet"

     

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{61F7B364-432C-4D04-BBC1-7FC1BF3807A8}]

    @="Bluetooth Bluewire Shell property extension object"

     

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{61F7B364-432C-4D04-BBC1-7FC1BF3807A8}\InprocServer32]

    @="C:\\Windows\\SysWOW64\\bthprops.cpl"

    "ThreadingModel"="Apartment"

     

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{F08C5AC2-E722-4116-ADB7-CE41B527994B}]

    @="Bluetooth Authentication Agent SSO"

     

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{F08C5AC2-E722-4116-ADB7-CE41B527994B}\InprocServer32]

    @="C:\\Windows\\SysWOW64\\bthprops.cpl"

    "ThreadingModel"="Apartment"

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Function Discovery\Categories\Layered\Microsoft.Base.DevicePairing\Bluetooth]

    "00000000"="<categoryMetadata name=\"Bluetooth Devices\" ><queryDefinition><category identity=\"Provider\\Microsoft.Devices.Bluetooth\" /></queryDefinition></categoryMetadata>"

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Function Discovery\Categories\Layered\Microsoft.Devices.FunctionEnumerators\Bluetooth]

    "00000000"="<categoryMetadata name=\"Bluetooth Device Function enumerator\" ><queryDefinition><category identity=\"Provider\\Microsoft.Devices.Bluetooth\" /><queryConstraint name=\"PairingState\" value=\"Paired\" /></queryDefinition></categoryMetadata>"

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellServiceObjects\{F08C5AC2-E722-4116-ADB7-CE41B527994B}]

    @="Bluetooth Authentication Agent SSO"

    "AutoStart"=""

     

    [HKEY_CLASSES_ROOT\CLSID\{C5599E1B-FC7B-4883-9FF4-581BBAEF8DBA}]

    @="Bluetooth FD Provider Proxy"

    "AppID"="{1C5221CB-C1F6-4999-8936-501C2023E4CD}"

     

    [HKEY_CLASSES_ROOT\CLSID\{C5599E1B-FC7B-4883-9FF4-581BBAEF8DBA}\InprocServer32]

    @="c:\\Windows\\System32\\fdBthProxy.dll"

    "ThreadingModel"="Both"

     

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{C5599E1B-FC7B-4883-9FF4-581BBAEF8DBA}]

    @="Bluetooth FD Provider Proxy"

    "AppID"="{1C5221CB-C1F6-4999-8936-501C2023E4CD}"

     

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{C5599E1B-FC7B-4883-9FF4-581BBAEF8DBA}\InprocServer32]

    @="c:\\Windows\\SysWOW64\\fdBthProxy.dll"

    "ThreadingModel"="Both"

     

     

    Make a bthserv.reg text file under folder “Registry” in an USB flash drive.

     

    Use Notepad to type following content and save it.

     

    Windows Registry Editor Version 5.00

     

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\bthserv]

    "DisplayName"="@%SystemRoot%\\System32\\bthserv.dll,-101"

    "ErrorControl"=dword:00000001

    "ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\

      74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\

      00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\

      6b,00,20,00,62,00,74,00,68,00,73,00,76,00,63,00,73,00,00,00

    "Start"=dword:00000003

    "Type"=dword:00000020

    "Description"="@%SystemRoot%\\System32\\bthserv.dll,-102"

    "DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00

    "ObjectName"="NT AUTHORITY\\LocalService"

    "ServiceSidType"=dword:00000001

    "RequiredPrivileges"=hex(7):53,00,65,00,43,00,68,00,61,00,6e,00,67,00,65,00,4e,\

      00,6f,00,74,00,69,00,66,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,\

      67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,61,00,74,00,65,00,47,00,6c,\

      00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,\

      65,00,00,00,53,00,65,00,49,00,6d,00,70,00,65,00,72,00,73,00,6f,00,6e,00,61,\

      00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,\

      00,00

    "FailureActions"=hex:84,03,00,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\

      00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00

     

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\bthserv\Parameters]

    "ServiceDllUnloadOnStop"=dword:00000001

    "ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\

      00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\

      62,00,74,00,68,00,73,00,65,00,72,00,76,00,2e,00,64,00,6c,00,6c,00,00,00

     

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\bthserv\Parameters\BluetoothControlPanelTasks]

    "State"=dword:00000001

     

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\bthserv\TriggerInfo]

     

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\bthserv\TriggerInfo\0]

    "Type"=dword:00000001

    "Action"=dword:00000001

    "GUID"=hex:2a,30,50,08,44,b3,da,4f,9b,e9,90,57,6b,8d,46,f0

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost]

    "bthsvcs"=hex(7):62,00,74,00,68,00,73,00,65,00,72,00,76,00,00,00,00,00

     

     

    Make a cpldontload32.reg text file under folder “Registry” in an USB flash drive.

     

    Use Notepad to type following content and save it.

     

    Windows Registry Editor Version 5.00

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Control Panel\don't load]

    "collab.cpl"=""

    "irprops.cpl"=""

    "bthprops.cpl"=""

     

     

    Make a cpldontload64.reg text file under folder “Registry” in an USB flash drive.

     

    Use Notepad to type following content and save it.

     

    Windows Registry Editor Version 5.00

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\don't load]

    "collab.cpl"=""

    "irprops.cpl"=""

    "bthprops.cpl"=""

     

    Step 2 - 5 are in separate post.

    Friday, October 16, 2009 10:42 AM
  • Step 2: Copy files to Windows Server 2008 R2

     

    Start Windows Server 2008 R2, hit F8 just before it boots to Windows logo screen, and select “Disable Driver Signature Enforcement” to boot and Login with administrative privilege.

     

    Note: This is required for Bluetooth to work because we must modify the original INF files and it will make these drivers cannot pass Windows Driver Signature.

     


    Get ready the files that prepared in step1 (in an USB flash drive, you can plug in Windows Server 2008 system now).

    Copy all files in “Drivers” to C:\Windows\Inf

     

    Note: This is very important. You cannot install drivers from the other folder. If you did try install from the other folder and fail, please remove all the installed driver files in C:\Windows\System32\DriverStore\FileRepository folder (bth.inf…) by using pnputil.exe.

     

    Copy all files in “System\x64” to C:\Windows\System32

    Copy all files in “System\x64\migration” to C:\Windows\System32\migration

    Copy all files in “System\x86” to C:\Windows\SysWOW64

    Copy all files in “System\x86\migration” to C:\Windows\ SysWOW64\migration

     

    If you cannot replace the some original files in Windows Server 2008 R2 because of security issue, you can change the ownership of original file to “Administrators” group and then add full control to this file.

    Open “properties” of a file or folder by right mouse click to this file or folder, hit “security” tab, hit “Advanced” button, hit “Owner” tab, hit “Edit” button and then following the screen to change ownership.

     

     

    Step 3: Registration Dll files

     

    Run “System\regbth.bat”

     

     

    Step 4: Install device driver for your Bluetooth device

     

    Plug in the USB Bluetooth device and it will install the driver automatically.

     

     

    Step 5: Modify registry key

     

    Run “Registry \bth.reg”

    Run “Registry \bthserv.reg”


    This step will install "Bluetooth support service" in the system services, you will see "Bluetooth support service" started and running after system reboot.


    In Registry Editor (regedit.exe), open following key:

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\don't load]

     

    Open “Permissions…” dialog box by right mouse click on this key in left panel; change the ownership to “Administrators” group and then make “Administrators” group full control permission.

     

    Do the same thing to following key:

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Control Panel\don't load]

     

    Run “Registry \ cpldontload64.reg”

    Run “Registry \ cpldontload32.reg”

     

     

    Step 6: Reboot Windows Server 2008

     

    Reboot Windows Server 2008 R2, hit F8 just before it boots to Windows logo screen, and select “Disable Driver Signature Enforcement” to boot.

     

    All the Bluetooth functions should work just as Windows 7 x64.

     

    Command Line to bring up Bluetooth setting Window:

     

    rundll32.exe shell32.dll,Control_RunDLL bthprops.cpl,,1

     

     

    Step 7: Installing Nokia PC Suite in Windows Server 2008

     

    Download newest Nokia PC Suite and rename it to Setup.exe

    (Original filename will be Nokia_PC_Suite_7_1_30_9_eng_us_web.exe in the time I wrote this)

     

    Copy “APIHook.dll” to “C:\Windows\SysWOW64” folder

     

    I made this “APIHook.dll” file to cheat the setup program by hooking to GetVersionEx() to return the version of Windows Vista instead of Windows Server 2008 R2 to Setup.exe program.


    Note: APIHook.dll is a 32 bits DLL file and can cheat only 32 bits named "Setup.exe" program.

     

    You can find this file in “APIHook” folder in Win7Bth.zip which can be downloaded from http://www.infoking.com.cn/Win7Bth.zip

     

    You can delete this file after Nokia PC Suite installation.

     

    In Registry Editor (regedit.exe), open following key:

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows]

     

    On right panel of this key:

     

    Change “LoadAppInit_DLLs” to 0

    Change “AppInit_DLLs” to “C:\Windows\SysWOW64\ APIHook.dll”

    Change “LoadAppInit_DLLs” to 1

    Change “RequireSignedAppInit_DLLs” to 0

     

    Run Setup.exe of Nokia PC Suite.

     

    After finish installation:

     

    Change “RequireSignedAppInit_DLLs” to 1

    Change “LoadAppInit_DLLs” to 0

    Change “AppInit_DLLs” to “” (Blank)

     

    Delete “C:\Windows\SysWOW64\ APIHook.dll” file.

     

    The Nokia PC Suite should work fine.

    You can use Bluetooth to sync the phone device also.

     

    All Done.

     

    Friday, October 16, 2009 10:43 AM
  • Now, if I only trick the WIDCOMM installer (http://www.broadcom.com/support/bluetooth/update.php) with that APIHook.dll, my setup would be perfect...


    Anthony King
    Tuesday, October 20, 2009 4:32 AM
  • Great progress. Anyone figure out how to fix the need to bypass signed drivers for this fix? I've tried a couple of Win7 (Dell) BT driver sets, but can't get past the unsupported OS message.
    Thanks again,
    Mw
    Wednesday, October 28, 2009 3:56 PM
  • There is a signed Broadcom driver floating around on some Chinese forum sites that might work. (If you trust it). Please note that the solution above does not fix pairing so there is no support for actual Bluetooth mice or keyboard, etc. The earlier posters are confused because a bluetooth mouse or keyboard using a dongle actually uses a USB driver and needs no Bluetooth driver or stack.

    I must say I am very disappointed that Microsoft failed to enable Bluetooth support as an option in Windows Server 2008 R2 after the problems people had with WS2K8.
    Thursday, October 29, 2009 9:35 PM
  • Also dissapointed. MS should understand that most serious developers needs a proper server OS on their laptops.
    Tuesday, November 03, 2009 9:24 AM
  • Followed all these instructions but get a device error dialog appearing when I attempt to add a bluetooth device.

    It says "Windows cannot complete the current operation. The following error code occurred [8007002]."

    Any suggestions?

    Thanks,

    Andy.
    • Proposed as answer by [N] Monday, November 16, 2009 9:53 AM
    Tuesday, November 10, 2009 12:49 PM
  • I can offer a slight workaround for some. I have a Dell Inspiron 1720 with Dell 355 BT (Broadcom BCM2045) running Windows Server 2008 R2. Apparently, the Broadcom BT emulates a standard USB/PS2 mouse and does connect to my  Logitech BT mouse, yet I can't get it to connect to my Microsoft BT mouse. I can't find anything on this behavior, but I haven't installed in BT drivers and the BT devices are showing unknown in Device Manager. There must be a way to bind BT mice to this if one knows the setting required, but I haven'been able to determine this yet.
    Thanks,
    MW61
    Tuesday, November 10, 2009 1:55 PM
  • Well, after removing everything and starting again I can now get all the Bluetooth components installed, I've used the Dell 360 Bluetooth drivers for vista 64, however I can't seem to detect any bluetooth devices?

    I don't get the error messages any more, but can't seem to see any devices when attempting to pair.

    Could if be because I'm using the vista 64 driver for the bluetooth module in my D830?

    Anybody got any other suggestion on driver?

    I've tried the "Generic Bluetooth" driver and I get the same issues...

    What a mare this is !

    I wish Server O/S would support bluetooth out-a the box !
    Tuesday, November 10, 2009 3:31 PM
  • I followed all instructions but get a device error when I attempt to add a Bluetooth device.

    "Windows cannot complete the current operation. The following error code occurred [8007002]."

    Please please please start to ship Bluetooth components OOTB with any Server O/S.  I've wasted my entire day tinkering with these options and am not even sure I can run Server 2008 R2 now because of this painful shortcoming.

    Andy - Did you ever get yours working?   Thanks in advance!  jeffmjones [at] gmail.com
    Friday, November 13, 2009 3:18 AM
  • Followed all these instructions but get a device error dialog appearing when I attempt to add a bluetooth device.

    It says "Windows cannot complete the current operation. The following error code occurred [8007002]."

    Any suggestions?

    Thanks,

    Andy.

    Hi Andy !

    I am new around here !

    I figured out the mistake !

    You must do following

    In Registry Editor (regedit.exe), open following key: (very important or you will get error code) !!!

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Function Discovery\Categories\Layered\Microsoft.Devices.FunctionEnumerators\Bluetooth]

    Open “Permissions…” dialog box by right mouse click on this key in left panel; change the ownership to “Administrators” group and then make “Administrators” group full control permission.

    Run “Registry \bth.reg”
    Run “Registry \bthserv.reg

    and then check again :

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Function Discovery\Categories\Layered\Microsoft.Devices.FunctionEnumerators\Bluetooth]

    for this entry :

    "00000000"="<categoryMetadata name=\"Bluetooth Device Function enumerator\" ><queryDefinition><category identity=\"Provider\\Microsoft.Devices.Bluetooth\" /><queryConstraint name=\"PairingState\" value=\"Paired\" /></queryDefinition></categoryMetadata>"

    If it's not there you must renew the operation.

    It worked for me.

    Let me know.

    Regards,

    Neige

    win7vista.com Beta Tester
    Monday, November 16, 2009 9:57 AM
  • Hi Andy,

     

    The installation procedure of BlueTooth Device is very tricky.

     

    1.       You must select  “Disable Driver Signature Enforcement” when you boot up Windows Server 2008 R2 by hit F8.

     

    2.       You must have administrator privilege.

     

    3.       You must follow step 2 exactly.

                 The BlueTooth driver cannot be installed from other directory.

                 But if you did it and failed, it was very difficult to fix the problem.

     

    Anyway, when you fail to install driver, please check:

     

    C:\Windows\inf\setupapi.dev.log

    or

    C:\Windows\inf\setupapi.dev.YYYYMMDD_SomeNumber.log

     

    It has very detail information about the installation procedure and the reason of failure.

     

    If you did try install driver from other than "C:\Windows\Inf" folder, it will have driver information in " C:\Windows\System32\DriverStore\FileRepository" folder, and this will fail to install new driver.

     

    In this case, you must use pnputil.exe to remove OEMxx.inf driver manually in order to install a new one.

     

     

    Hi neige_w7v,

     

    Yes, you are right, you must verify every step, make sure all the registry file is import successfully.

     

     

     

    Wednesday, November 18, 2009 3:02 PM
  • Thanx BridgeMan0721 !

    Great explanations !

    I will add to my post on win7vista.com the extra information on the drivers installation.

    I also would like to point out that credits to your great work have been mentionned in my post on all this with details and howto.

    Thank you from all of us who use R2 everyday !

    If you need anything to be tried out let me know.

    I have always have an R2 release ready for testing.

    Regards,

    Neige



    Friday, November 20, 2009 6:03 PM
  • I've been away on business for the last week or so, thanks for all the feedback guys, i'll take a look at what you've written and have another attempt at getting it all working.

    I'll feed back my results soon.

    Thanks for the advice.

    Monday, November 23, 2009 1:08 PM
  • Workaround? here..

    I have two BT dongles, one Motorola and one Surecom. The Moto never worked, even trying to modify the drivers... and this Surecome (and no other PN or SN) worked like a charm with... TOSHIBA's drivers, v. 7.00.10, for XP/Vista/7 x64, which I have download from here
    The installation requires you to reboot your server and after the restart you have a 100% BT enabled server.

    Cristian

    Tuesday, November 24, 2009 8:34 PM
  • Thanx RCristian !

    Nice information share.

    I will try it out !

    Regards,

    Neige

    :) :)
    Tuesday, November 24, 2009 10:09 PM
  • Hello, Bridgeman0721.

    I'm really appreciated your effort.

    I did what you've written.

    but, there are some problems.

    1. When clicking "Add a device" through bluetooth stack icon on the tray, error code occured [80070002].

    2. When clicking "Open devices and printers", doesn't seem to show anything.


    I really want to fix it.

    so.. please help me out.

    thanks in advance.
    Thursday, December 03, 2009 8:16 AM
  • Hi ssrrres !

    Do following :

    I am new around here !

    I figured out the mistake !

    You must do following

    In Registry Editor (regedit.exe), open following key: (very important or you will get error code) !!!

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Function Discovery\Categories\Layered\Microsoft.Devices.FunctionEnumerators\Bluetooth]

    Open “Permissions…” dialog box by right mouse click on this key in left panel; change the ownership to “Administrators” group and then make “Administrators” group full control permission.

    Run “Registry \bth.reg”
    Run “Registry \bthserv.reg

    and then check again :

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Function Discovery\Categories\Layered\Microsoft.Devices.FunctionEnumerators\Bluetooth]

    for this entry :

    "00000000"="<categoryMetadata name=\"Bluetooth Device Function enumerator\" ><queryDefinition><category identity=\"Provider\\Microsoft.Devices.Bluetooth\" /><queryConstraint name=\"PairingState\" value=\"Paired\" /></queryDefinition></categoryMetadata>"

    If it's not there you must renew the operation.

    It worked for me.

    Let me know.

    Regards,

    Neige

    win7vista.com Beta Tester

    Thursday, December 03, 2009 8:40 AM
  • Thank you neige_w7v for your reply speed like a thunder.
    It's fastest ever I've got..

    Nway.. Sorry.. That wasn't the solution.

    Actually I did that the first time doing this.

    thanks anyway. neige_w7v
    Thursday, December 03, 2009 11:19 AM
  • Hi there,

    At first thanks Bridgeman0721 for the great clues and progress.

    Using procmon and digging into Windows 7 x64 registry I found the following registry entries are missing in 2008 R2 (in addition to what Bridgeman0721 provides)

    After importing these in 2008 R2 I finaly got the full MS bluetooth stack working, including device pairing ("Add new device") and "Bluetooth Devices" in Control Panel.

    Here is it:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{1C5221CB-C1F6-4999-8936-501C2023E4CD}]
    @="Bluetooth FD Provider"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{1C5221CB-C1F6-4999-8936-501C2023E4CD}\InprocServer32]
    @="C:\\Windows\\System32\\fdBth.dll"
    "ThreadingModel"="Free"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{1C5221CB-C1F6-4999-8936-501C2023E4CD}]
    @="Bluetooth FD Provider"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{1C5221CB-C1F6-4999-8936-501C2023E4CD}\InprocServer32]
    @="C:\\Windows\\SysWOW64\\fdBth.dll"
    "ThreadingModel"="Free"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}]
    @="Infrared"
    "System.Software.TasksFileUrl"="Internal"
    "InfoTip"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
      6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
      00,69,00,72,00,70,00,72,00,6f,00,70,00,73,00,2e,00,63,00,70,00,6c,00,2c,00,\
      2d,00,32,00,00,00
    "LocalizedString"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,\
      6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
      00,5c,00,69,00,72,00,70,00,72,00,6f,00,70,00,73,00,2e,00,63,00,70,00,6c,00,\
      2c,00,2d,00,31,00,00,00
    "System.ApplicationName"="Microsoft.Infrared"
    "System.ControlPanel.Category"="2,3"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\DefaultIcon]
    @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
      00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,00,72,00,\
      70,00,72,00,6f,00,70,00,73,00,2e,00,63,00,70,00,6c,00,2c,00,2d,00,31,00,32,\
      00,39,00,00,00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\Shell]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\Shell\Open]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\Shell\Open\Command]
    @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
      00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
      6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,25,00,53,\
      00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,00,5c,00,53,00,\
      79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,00,68,00,65,00,6c,00,6c,\
      00,33,00,32,00,2e,00,64,00,6c,00,6c,00,2c,00,43,00,6f,00,6e,00,74,00,72,00,\
      6f,00,6c,00,5f,00,52,00,75,00,6e,00,44,00,4c,00,4c,00,20,00,25,00,53,00,79,\
      00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,\
      73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,00,72,00,70,00,72,00,6f,00,70,\
      00,73,00,2e,00,63,00,70,00,6c,00,00,00


    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}]
    @="Infrared"
    "System.Software.TasksFileUrl"="Internal"
    "InfoTip"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
      6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
      00,69,00,72,00,70,00,72,00,6f,00,70,00,73,00,2e,00,63,00,70,00,6c,00,2c,00,\
      2d,00,32,00,00,00
    "LocalizedString"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,\
      6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
      00,5c,00,69,00,72,00,70,00,72,00,6f,00,70,00,73,00,2e,00,63,00,70,00,6c,00,\
      2c,00,2d,00,31,00,00,00
    "System.ApplicationName"="Microsoft.Infrared"
    "System.ControlPanel.Category"="2,3"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\DefaultIcon]
    @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
      00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,00,72,00,\
      70,00,72,00,6f,00,70,00,73,00,2e,00,63,00,70,00,6c,00,2c,00,2d,00,31,00,32,\
      00,39,00,00,00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\Shell]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\Shell\Open]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}\Shell\Open\Command]
    @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
      00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\
      6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,25,00,53,\
      00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,00,5c,00,53,00,\
      79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,00,68,00,65,00,6c,00,6c,\
      00,33,00,32,00,2e,00,64,00,6c,00,6c,00,2c,00,43,00,6f,00,6e,00,74,00,72,00,\
      6f,00,6c,00,5f,00,52,00,75,00,6e,00,44,00,4c,00,4c,00,20,00,25,00,53,00,79,\
      00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,\
      73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,00,72,00,70,00,72,00,6f,00,70,\
      00,73,00,2e,00,63,00,70,00,6c,00,00,00


    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Function Discovery\Categories\Provider\Microsoft.Devices.Bluetooth]
    "00000000"="<provider type=\"{1C5221CB-C1F6-4999-8936-501C2023E4CD}\" />"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Function Discovery\Categories\Provider\Microsoft.Devices.Bluetooth]
    "00000000"="<provider type=\"{1C5221CB-C1F6-4999-8936-501C2023E4CD}\" />"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}]
    @="Infrared"


    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ControlPanel\NameSpace\{A0275511-0E86-4ECA-97C2-ECD8F1221D08}]
    @="Infrared"


    Cheers,
    Vlad

    Thursday, December 03, 2009 12:25 PM
  • We're getting close...
    Do you still need to Disable Driver Signature Enforcement at boot up? Has anyone packaged this up into single instructions?
    Thanks,
    MW61
    Saturday, December 12, 2009 9:50 PM
  • Hi MW61 !

    Well there is a solution !

    It would be to configure R2 to be able to run unsigned drivers.

    Of course you get the Watermark that you can remove with "appropriate tools".

    I tried it out and no need to strike F8.

    Also you can install 3rd party drivers for other hardware such as printers,...

    Regards,

    Neige


    • Edited by [N] Saturday, December 12, 2009 10:29 PM type mistake
    Saturday, December 12, 2009 10:28 PM
  • Great work!
    Almost all main features works great, but the PAN support doesn't work (PAN pairing Control Panel seems to be mising) and also there is impossible to remove COM ports after adding them in BT Settings. Hope we'll be able to fix it soon!
    Monday, December 14, 2009 11:50 AM
  • You can use this app to automatically disable Driver Signature Enforcement during boot.
    Monday, December 14, 2009 11:54 AM
  • Hi AsciiWolf !

    I'm a great fan of your work along with JonusC !!!!

    I tried the above app and it doesn' give correct results on all PC's, but !

    On your website in Workstation section there is an app that was written by fear55 that does work.

    I tried it out and integrated it too. Of course watermark comes out.

    What dou you think about it ?

    I am not familiar with how you can give links out on here so I did not post any.

    By the way, I mentionned you both in my posts and links to your site for my r2 workstation releases.

    If you wish to have a link to download them just mail me.

    Once again thank you for your and JonusC contribution to get r2 to wokrstation converted.

    Regards,

    Neige
    W7V Beta Tester


    • Edited by [N] Monday, December 14, 2009 8:45 PM type mistake
    Monday, December 14, 2009 8:43 PM
  • I used to use ReadDriver Plus v1.1 under Vista x64 and Server 2008, but I use this method now which to me is a bit cleaner:

    Solving 64-Bit Windows' "I Only Want Signed Drivers!" Tantrums

    And I use this to remove the watermark when you have Windows set to run in 'test' mode.

    You can also use this, it's an app that does the above for you, it may be a little easier for most people. If it doesn't work, just do it manually with the instructions above:
    Driver Signature Enforcement Overrider 1.3b

    I haven't tried getting BT working under my Win2k8 R2 workstation yet, but I do plan on it sometime, hopefully after someone irons out all the details and perhaps makes an easier to follow walkthrough on here :)
    Tuesday, December 15, 2009 12:15 AM
  • Thanx trafsta !

    I am going to take a look at it.

    Very nice !

    Regards,

    Neige

    Tuesday, December 15, 2009 10:43 PM
  • Hello, I got MS Bluetooth stack from Windows 7 completely working on Windows Server 2008 R2!
    Here is an installer for it. Enjoy! ;-)
    • Proposed as answer by AsciiWolf Sunday, December 27, 2009 3:49 PM
    • Edited by AsciiWolf Saturday, January 23, 2010 4:39 PM
    Sunday, December 27, 2009 1:54 PM
  • Thanx AsciiWolf !

    What a nice X-mas present !!!

    Thank you very much.

    I am going to try it out ASAP.

    All the best for 2010 my friend and to all around here.

    Regards,

    Neige


    ;-)

    Sunday, December 27, 2009 3:13 PM
  • Unfortunately, I tried running the install.cmd from blootooth.7z from AsciiWolf, and no joy. Nothing seems to have changed, i.e. device manager, control panel, etc for BT icons. I do see the BT file transfer utility which installed at reboot, but nothing else. Am I doing something wrong?
    Thanks,
    MW61
    Monday, December 28, 2009 10:23 PM
  • I think, your Bluetooth hardware isn't supported by Windows 7 generic Bluetooth drivers. :-/
    What Bluetooth HW do you have?
    Tuesday, December 29, 2009 8:11 AM
  • Broadcom BCM2045 which when I boot Win7 on same laptop, it works. Any thoughts?
    Thanks,
    MW61
    Tuesday, December 29, 2009 2:22 PM
  • I started this thread and finally resolved my BT problem on my Dell 1720 laptop running W2K8R2. And it was the first thing I tried that failed in RC of Windows Server 2008 R2, but now works. I installed the Vista64 drivers from Dell of in my case, the Broaccomm BCM2045 or in Dell terms, Bluetooth 355. Trick to getting the driver to install was to install the *.MSI directly, and not run setup.exe. After installing the drivers, nothing changed until I went into device manager and updated the drivers on the BCM2045 unknown device. Now, I've got full BT support and all the BT apps.  One question though is I did execute the instructions by AsciWolf a day before w/ no luck. I didn't remove these changes, so that could be part of the solution. Gee, this only took four months...I hope this helps others.
    Thanks all,
    MW61

    Tuesday, December 29, 2009 11:04 PM
  • Well, here's my new bluetooth-related project.
    Official Broadcom drivers (with some special features like using mobile phone as an headset, obex file browser, etc) patched to support Windows Server 2008 R2.
    Download: Here .
    Info: Just unpack the archive using 7zip and follow instructions in readme.txt file.
    Note: You must have my Bluetooth stack patch installed before installing this!
    Enjoy!
    ps. I'm a student so I don't have a much free time. I'm doing this work in my free time, so, if you like my "Bluetooth for Windows Server 2008 R2" work, please consider a donation .
    • Proposed as answer by networkted Sunday, May 30, 2010 1:49 AM
    • Edited by AsciiWolf Sunday, June 27, 2010 1:18 PM updated download link with new version of drivers
    Saturday, February 27, 2010 5:19 PM
  • AsciiWolf:

    When I attempt to run setup.exe in Windows Server 2008 R2, I receive a message:

    "Setup has detected an incompatible version of Windows"


    Sunday, March 07, 2010 3:20 PM
  • same trouble: "Setup has detected an incompatible version of Windows"
    Thursday, April 29, 2010 12:17 PM
  • Hi Ascii!

    I love your the broadcom patch for windows server 2008 R2, fixed lots of missing profiles and drivers that weren't avaliable from the initial Microsoft bluetooth stack patch. Unfortunately, I still have some drivers/profiles missing for these hardware IDs. I think they are probably some BT profiles related to my Nokia E55.

    Hardware IDs:

    1. BTHENUM\{00000004-0000-1000-8000-0002ee000002}_VID&00010001_PID&0096
    2. BTHENUM\{00005601-0000-1000-8000-0002ee000001}_VID&00010001_PID&0096
    3. BTHENUM\{00005557-0000-1000-8000-0002ee000001}_VID&00010001_PID&0096
    4. BTHENUM\{00005005-0000-1000-8000-0002ee000001}_VID&00010001_PID&0096
    Saturday, May 29, 2010 6:11 PM