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 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. There is a signed Broadcom driver floating around on some Chinese forum sites that might work. (If you trust it). Driver Bluetooth Pour Hp Pavilion Dv7. Please note that the solution above does not fix pairing so there is no support for actual Bluetooth mice or keyboard, etc.

ATI 32/64bit display driver 8.24.50.5-090623a-083721C-Dell for Microsoft Windows Vista, Windows 7 and Windows Server 2008 R2. 32bit WHQL signature applies only to.

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. 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. 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! 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. 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'=' If it's not there you must renew the operation. It worked for me. Regards, Neige win7vista. Denon Rc 1075 Manual Dexterity here. com Beta Tester. Hi Andy, The installation procedure of BlueTooth Device is very tricky. You must select “Disable Driver Signature Enforcement” when you boot up Windows Server 2008 R2 by hit F8. You must have administrator privilege.

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. 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'=' If it's not there you must renew the operation. It worked for me. Regards, Neige win7vista.com Beta Tester. 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. 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: And I use 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: 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:). 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. Well, here's my new bluetooth-related project.

Official (with some special features like using mobile phone as an headset, obex file browser, etc) patched to support Windows Server 2008 R2. Info: Just unpack the archive using 7zip and follow instructions in readme.txt file. Note: You must have my installed before installing this!

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.

I have a big problem with my wireless card TP-Link WN951N (Atheros AR922X) on Windows 10 64 bits. The network adapter stops randomly and disconnect me from Internet. The available networks disappear. Sometimes, in the devices manager, there is a warning before the wireless card, explaining that Windows can't start the adaptater (code 10). Sometimes, desactivate/activate the adaptater solves the problem but it arrives that the adaptater can't be activated until restarting the computer. The1 BIOS is up to date.

The driver provided by Microsoft for this card dates from the 12th March 2015. TP-Link says me that Windows doesn't validate any driver version for this version of Windows. On the Internet, I discover this strange unofficial website, with more recent drivers (and empty forums): Qualcomm explains officially he decided to stop giving generic drivers on its website since February 2015. What do you think should I do?