Bluetooth stack установить на windows server 2008 r2

This article includes modified files ready for the installation of Microsoft Bluetooth Stack on both x86 (32-bit) and x64 (64-bit) editions of Windows Server 2008.

The know-hows of installing Microsoft Bluetooth Stack on Windows Server 2008 64-bit (and 32-bit) edition, in case of using it as a workstation, is spread on blogs everywhere, and Gil is behind the whole story.

The problem is System File Repository (C:WindowsSystem32DriverStoreFileRepository) doesn’t always contain all the files needed, like Broadcom (Widcomm) driver files for instance (filenames starting with btw), and gurus also forgot to mention a few files in their listings (btwavdt.inf, btwrchid.inf, and bthprint.sys to mention a few.)

Note: Broadcom (Widcomm) files are not included in a fresh Windows’ File Repository. People who luckily find them in the Repository have definitely installed OEM BT drivers. For example, Lenovo Y710 OEM drivers include the latest Broadcom (Widcomm) Bluetooth driver version 6.0.1.5500 (08/31/2007), where Dell XPS M1330 OEM drivers include the older Broadcom (Widcomm) Bluetooth driver version 6.0.1.3100 (11/03/2006).

Microsoft Bluetooth Stack for Windows Server 2008 x86 and Windows Server 2008 x64

I’ve collected all the files needed for both x86 and x64 systems separately, modified all the NTx86…1, NTia64…1, and NTamd64…1 sections into NTx86, NTia64, and NTamd64 in all INFs, and cabbed them into separate archives for both 32-bit and 64-bit editions.

CAUTION! I double-checked, sometimes triple-checked everything, but please practice safe driver upgrade. Creating a System Restore Point (image backup is even safer) is highly recommended. Remember, at the end, you’re doing it at your own risk!

Download Links

• Download Microsoft Bluetooth Stack for Windows Server 2008 x86 (32-bit) modified by Komeil Bahmanpour
• Download Microsoft Bluetooth Stack for Windows Server 2008 x64 (64-bit) modified by Komeil Bahmanpour

Both the 32-bit and 64-bit stack drivers include:

• Microsoft Bluetooth Stack driver version 6.0.6001.18000 (06/21/2006)
• Broadcom (Widcomm) Bluetooth driver version 6.0.1.5500 (08/31/2007)

Note: Files starting with “btw” belong to Broadcom (Widcomm) and the others are Microsoft’s:

• btwaudio.cat, btwaudio.inf, btwaudio.sys: WDM audio (PortCls) Bluetooth Audio Driver
• btwavdt.cat, btwavdt.inf, btwavdt.sys: Broadcom Bluetooth AVDT Service Installation
• btwrchid.cat, btwrchid.inf, btwrchid.sys: Remote Control HID Minidriver Installation

CAB File Listing

Supported Hardware Brands

Infrared (IR) Support

To support infrared (IR), both CABs contain modified versions of Windows / SigmaTel drivers:

• circlass.inf, circlass.sys: Microsoft Consumer IR Devices (CIR Class enumerator driver)
• netirda.inf: Microsoft IrDA transport
• irstusb.inf, irstusb.sys: SigmaTel NDIS 5.0 USB Infra-Red Driver

Bluetooth Headsets ^{[Updated May 20, 2009]}

Due to the fact that both Windows Vista / Windows Server 2008 don’t support Bluetooth headset profile, if you want to use a Bluetooth headset with your adapter, you’ll need to add the headset profile to the default Microsoft stack. Visit my headset blog entry to know more about installing and enabling Bluetooth headset profile in Windows Vista / Windows Server 2008.

Install and Enable Bluetooth on MacBook Pro Operating Windows Server 2008

The CAB files are for normal Windows users running an IBM-PC-compatible machine, however some came to their senses and produced Macs that are not Macs anymore. The CABs could gladly help these users too:

• Install Boot Camp drivers. The driver will be installed, but it won’t be associated with the appropriate hardware.
• Open Device Manager, right click the Bluetooth USB Host Controller, and click Update Driver Software… menu item.
• Choose Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
• Choose Bluetooth Radios, then click Next.
• Uncheck Show compatible hardware, in the left select Apple Inc. and in the right Apple Built-in Bluetooth, then click Next.
• Answer Yes to the popped Update Driver Warning dialog.
• Wait for the driver to install and display Windows has successfully updated your driver software, and then click Close.
• Cancel all of the Found New Hardware dialogs. The Bluetooth icon will show up in the notification area.
• Apple Built-in Bluetooth is now listed under Bluetooth Radios, three Unknown devices under Other devices.
• Download and extract Microsoft Bluetooth Stack for Windows Server 2008 (x86/x64) CAB file in a specific folder, e.g. C:BT.
• Right click the first Unknown device and click Update Driver Software… menu item.
• Choose Browse my computer for driver software and enter the path to the CAB extraction folder and click Next.
• Choose Install this driver software anyway in the Windows Security dialog shown.
• Wait for the driver to install, and then click Close.
• Do the same routine to install the other Unknown devices.
• Upon completion, Microsoft Bluetooth Enumerator will show up under Bluetooth Radios, along with new Network adapters.
• Installing Microsoft IntelliPoint, it will prompt you to insert the transceiver, click Cancel.
• Pair the mouse using Bluetooth control panel, and a new device shows up in Device Manager. Update the driver using the same methods you’ve done before, so it’s recognized as Bluetooth HID Device.
• Enable your Wireless Notebook Presenter and click the presentation mode button.
• If everything is fine, delete the temporary driver extraction folder. You’re done.

A note of caution: Screwing around with device drivers and INF files is a good way to utterly hose your system and possibly render it unusable. Be sure you have a current backup of your entire system AND THAT YOU CAN RESTORE AN UNBOOTABLE SYSTEM FROM IT. The steps I describe here worked on my laptop, with the versions of Windows Server 2008 and drivers that I happened to have; it may or may not work on yours. I make no guarantees about the workability of any of this. You are taking your life into your own hands. Don’t come crying to me if it doesn’t work. If it doesn’t work, restore from your backup, and you’re no worse off than before. Read the Vista DDK docs regarding INF files first; they are really helpful in understanding what you are doing. Good luck.

0. Install Windows Server 2008 x64 (full, not Server Core) on your laptop. I used Standard but I suspect that Enterprise will work too.

1. Load all the appropriate Vista x64 drivers for your laptop. Obviously, everybody’s system is different, and there will probably be some cases where the Vista x64 drivers won’t install on WS08. In the case of the HP 8710p, all of the Vista x64 drivers installed and seemed to worked properly.

2. Create a temporary subdirectory to hold the edited INF files and related drivers and executables. I’ll use C:BT in this post.

3. Copy the following files from their respective subdirectories in C:WindowsSystem32DriverStoreFileRepository to C:BT.

bth.inf
bthenum.sys
bthmodem.sys
bthpan.inf
bthpan.sys
bthport.sys
bthprint.inf
bthspp.inf
bthusb.sys
btwaudio.inf
btwaudio.sys
btwavdt.sys
btwrchid.sys
fsquirt.exe
hidbth.inf
hidbth.sys
hidclass.sys
hidparse.sys
hidusb.sys
input.inf
mdmbtmdm.inf
netirda.inf
rfcomm.sys
tdibth.inf

4. Copy modemui.dll from C:WindowsSystem32 to C:BT

The basic editing operation on all of the INF files is to change the string «NTamd64…1» to «NTamd64…3» where it relates to a Microsoft Bluetooth component. The «amd64» tells the driver installer to evaluate the section for x64 class systems, and the «1» indicates that it should process the section only for workstation class OS’s. When you change the «1» to a «3», the driver installer evaluates the INF section only on server class systems, e.g. Windows Server 2008. You could presumably just remove the dots and the number entirely with the same effect, but I haven’t tried that.

5. Edit C:BTbth.inf

Change line 47 from %Microsoft%=Microsoft, NTamd64…1 to %Microsoft%=Microsoft, NTamd64…3
Change line 132 from [Microsoft.NTamd64…1] to [Microsoft.NTamd64…3]

6. Edit C:BTbthpan.inf

Change line 29 from %MfgName%        = Msft,NTamd64…1 to %MfgName%        = Msft,NTamd64…3
Change line 31 from [Msft.NTamd64…1] to [Msft.NTamd64…3]

7. Edit C:BTbthprint.inf

Change line 19 from %MSFT%=Microsoft,NTamd64…1 to %MSFT%=Microsoft,NTamd64…3
Change line 21 from [Microsoft.NTamd64…1] to [Microsoft.NTamd64…3]

8. Edit C:BTbthspp.inf

Change line 12 from %MSFT%     = Standard,NTamd64…1 to %MSFT%     = Standard,NTamd64…3
Change line 14 from [Standard.NTamd64…1] to [Standard.NTamd64…3]

9. Edit C:BThidbth.inf

Change line 29 from %MSMfg%=MicrosoftHid,NTamd64…1 to %MSMfg%=MicrosoftHid,NTamd64…3
Change line 34 from [MicrosoftHid.NTamd64…1] to [MicrosoftHid.NTamd64…3]

10. Edit C:BTmdmbtmdm.inf

Change line 19 from %Standard%     = Standard,NTamd64…1 to %Standard%     = Standard,NTamd64…3
Change line 27 from [Standard.NTamd64…1] to [Standard.NTamd64…3]

11. Edit C:BTtdibth.inf

Change line 15 from %MfgName% = Msft,NTamd64…1 to %MfgName% = Msft,NTamd64…3
Change line 17 from [Msft.NTamd64…1] to [Msft.NTamd64…3]

12. Turn on the Bluetooth transceiver. You should get the «Found New Hardware» dialog for each missing Bluetooth device. Cancel each of the dialogs.

13. Start Device Manager (from Server Manager/Diagnostics, or Computer/Properties)

14. Find the unknown Bluetooth devices. They should show up under «Other devices» with a yellow warning icon. You can identity the specific devices by right-clicking each unknown device, and looking at Details/Hardware IDs. The Bluetooth devices all start with «BTH».

15. Find the unknown device with Hardware ID «BTMS_BTHBRB», right-click on it, select Update Driver Software, select Browse my computer for driver software, and enter C:BT (or whatever subdirectory you used above). You will get a dialog box that Windows can’t verify the publisher because the INF file has no signature. Select Install this driver software anyway.

16. Find the unknown device with Hardware ID «BTMS_BTHPAN» and do the same thing.

17. Find the unknown device with Hardware ID «BTRFCOMM» and do the same thing.

18. Start the Bluetooth applet from Control Panel, go to the devices tab and select Add.

19. Make your device discoverable and click Next in the Bluetooth applet. Your device should appear.

20. If the Found New Hardware dialog appears, click Don’t search online, and then click Show me other options. In the next dialog, select Browse my computer for driver software (advanced), and select C:BT (or whatever subdirectory you used). You will get a dialog box that Windows can’t verify the publisher because the INF file has no signature. Select Install this driver software anyway.

21. Lather. Rinse. Repeat.

To get your particular piece of hardware to work, you may have to enable other sections of the INF files in the C:BT subdirectory by changing the platform designator from amd64…1 to amd64…3. What I describe here worked for me to pair two different mice (Logitech and Microsoft) and two headsets (Koss, and a no-name-o brand I got as a gift). It also seems to pair up with other PCs. I have not tried a Bluetooth modem, such as a cell phone yet.

It really bugs me sometimes that Microsoft imposes artificial limitations on Windows versions because they think features are out of scope. Case in point is Windows Server 2008. Now, there is no earthly reason why WS2008 can’t support Bluetooth right out of the box. An yet, because someone on the Server team decided that servers don’t use Bluetooth, if you’re one of the thousands of people who use WS2008 as a workstation, you’re SOL. Think just installing your Bluetooth drivers, or enabling the “Wireless LAN Services” feature will do it? Think again.

Gil Kirkpatrick posted a solution a couple of weeks ago, and it works like a charm. It involves modifying the INF files from the default WS2008 installation to install the Microsoft Bluetooth Stack on WS2008.

Since it’s kind of a time consuming process, I’ve taken the liberty of completing the required steps, and dumping them in a Zip file, albeit only for WS2008 x64. All you need to do is:

• install your BT drivers as normal,
• unzip the folder to C:BT
• open up Device Manager
• right click any items that still say “Unknown Device” and select “Update Drivers”
• Select the bottom menu option and browse to the C:BT folder
• “Lather, rinse, repeat” for any other Unknown Devices

You can find the zip file here. Hopefully that will keep you from beating your head against the wall, as I did, over my #$%^&* Bluetooth mouse.