- WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION INSTALL
- WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION DRIVERS
- WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION DRIVER
- WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION BLUETOOTH
Tdibth.inf and tdibth.pnf = SI and PSI for RFCOMM transport.
WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION BLUETOOTH
Hidbth.inf and hidbth.pnf = SI and PSI for bluetooth HID. This is the one that you modify in order to have Windows reinstall its own stack.īthpan.inf and bthpan.pnf = SI and PSI for bluetooth PAN driver.īthprint.inf and bthprint.pnf = SI and PSI for bluetooth printer driver.īthspp.inf and bthsp.pnf = SI and PSI for bluetooth modem driver. You will probably also have the following setup files in %windir%\inf, associated with the support files (but in my case, there were a few setup files that did not have SYS or DLL matches):īth.inf and bth.pnf = setup info and precompiled setup info for Windows bluetooth driver. Wshbth.dll = windows sockets helper DLL for bluetooth.
WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION DRIVER
Hidbth.sys = bluetooth miniport driver for human interface devices. Like the main files, most of these support files are also located in %windir%\system32 or %windir%\system32\drivers:īthmodem.sys = bluetooth communications driver.īthprops.cpl = bluetooth control panel applet. You will probably also have the following support files. The first three files are in %windir%\system32\drivers, and the fourth file is in %windir%\system32. The main files in Microsoft's bluetooth stack, according to System Control Panel's Device Manager entry (now that I've installed the M$ BT stack) are:īthenum.sys = bluetooth bus extender (Microsoft bluetooth enumerator).īthusb.sys = bluetooth miniport driver (USB interface).įsquirt.exe = bluetooth file transfer wizard. I could just cut to the chase and tell you to delete BTKRNL.SYS, but first let me explain how that solution came to me. So what do you do? After struggling with this question for several days and reading other posts, I think I found a brute-force solution. If you can't uninstall the Broadcom enumerator and you reboot, Windows will see the Broadcom enumerator and will keep reinstalling the associated Broadcom bluetooth driver with Enhanced Data Rate II. When you right click on that entry, there is no uninstall option. Unfortunately (if your ThinkPad is anything like mine), the bluetooth enumerator entry cannot be uninstalled.
WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION INSTALL
Now uninstall your two Broadcom entries under Bluetooth Radios in System Control Panel's Device Manager, and when you reboot, Windows should autodetect the bluetooth radio hardware and install its own bluetooth stack. I'm not sure what the second "Rev_0399" entry was for, so I didn't include that in the INF file. In my case, I typed:īroadcom bluetooth radio inside ThinkPad= BthUsb, USB\VID_0A5C&PID_2145 You can call the device whatever you like. My BlueTooth Device = BthUsb, USB\VID_xxxx&PID_XXXX For example, on my ThinkPad T400, the hardware IDs wereĪdd a line to your BTH.INF file under the manufacturer of your bluetooth radio, which in this case, is Broadcom.
WIDCOMM BLUETOOTH SOFTWARE FAILED TO COMPLETE INSTALLATION DRIVERS
When sending or receiving files, the progress bar would either freeze up when sending PC to phone, or reach 100% when sending phone to PC, but would send the file into a black hole, never to be found on the PC.) As you probably know from reading other posts, if you want to use Desktop Manager with bluetooth, or want to be able to send and receive files using bluetooth, you should uninstall the Broadcom drivers and return to the original Windows XP SP2 bluetooth drivers.īefore uninstalling, find the hardware IDs for your bluetooth radio in the System Control Panel (click on the Details tab, then select Hardware IDs). (In my experience, the Broadcom stack NEVER worked for OPP. The ThinkPad T400, and probably many other ThinkPads, come preinstalled with Broadcom (Widcomm) bluetooth drivers, which Desktop Manager does not support, and which don't always work when trying to do OPP file transfers.
0 kommentar(er)
