Bluetooth Software for Win10x64

[JMurfe]

Has anyone been able to find working Bluetooth driver/software?

HardwareID:  USB\VID_8087&PID_07DA&REV_7869

Thank you.

[Paul_Tikkanen]

Hi:

Did you try the W10 bluetooth driver directly from Intel?

That would be the only suggestion I can offer.

https://downloadcenter.intel.com/download/25206/Intel-PROSet-Wireless-Software-for-Bluetooth-technol...

[JMurfe]

Hi Paul.

I hadn't done that, but I just tried.  The software is showing that it installed, but the unknown device in the device manager is still not updated.

I then went and ran the Intel Driver detection tool.  It found the exact same driver and wanted me to install it.  Using this tool, it was showing the installation process failed.  I am trying to find out where the log is for this tool.

Lastly I extracted the BlueTooth.msi and ran an MSIExec /i command and did verbose logging and it was showing this:

MSI (s) (E0:C8) [10:44:45:013]: Executing op: ActionStart(Name=Install_RFKill,,)
MSI (s) (E0:C8) [10:44:45:014]: Executing op: CustomActionSchedule(Action=Install_RFKill,ActionType=3137,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Program Files (x86)\Intel\Bluetooth\utilities\rfkillsetup.bat" "C:\Program Files (x86)\Intel\Bluetooth\utilities\" install)
MSI (s) (E0:0C) [10:44:45:039]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI23FD.tmp, Entrypoint: CAQuietExec
CAQuietExec:  Error 0x80070002: Command failed to execute.
CAQuietExec:  Error 0x80070002: CAQuietExec Failed
MSI (s) (E0:C8) [10:44:45:048]: Executing op: ActionStart(Name=CA_CreateUSBPCIRegKeys,,)
CustomAction Install_RFKill returned actual error code 1603 but will be translated to success due to continue marking
MSI (s) (E0:C8) [10:44:45:048]: Executing op: CustomActionSchedule(Action=CA_CreateUSBPCIRegKeys,ActionType=3073,Source=BinaryData,Target=CreateUSBPCIRegKeys,)
MSI (s) (E0:D8) [10:44:45:073]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI241E.tmp, Entrypoint: CreateUSBPCIRegKeys
MSI (s) (E0:C8) [10:44:45:081]: Executing op: ActionStart(Name=CA_RuniBTMgrQueryRestart,,)
CustomActions:  CA_win - CreateUSBPCIRegKeys leaving
MSI (s) (E0:C8) [10:44:45:081]: Executing op: CustomActionSchedule(Action=CA_RuniBTMgrQueryRestart,ActionType=3073,Source=BinaryData,Target=RuniBTMgrQueryRestart,)
MSI (s) (E0:FC) [10:44:45:105]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI243E.tmp, Entrypoint: RuniBTMgrQueryRestart
CustomActions:  CA_win - EnumerateWlanInterfaces - WlanOpenHandle is opened
CustomActions:  CA_win - EnumerateWlanInterfaces - Enumerate Wlan interfaces: 1
CustomActions:  CA_win - EnumerateWlanInterfaces - No 7260 interface found
CustomActions:  CA_win - RuniBTMgrRestart - Failed to perform Control operation on BT Radio
MSI (s) (E0:C8) [10:44:45:114]: Executing op: ActionStart(Name=WriteRegistryValues,Description=Writing system registry values,Template=Key: [1], Name: [2], Value: [3])
CustomActions:  CA_win - RuniBTMgrRestart leaving

In the end, still a "no-go"

[Paul_Tikkanen]

Sorry that didn't work for you.

I tried to break the driver down into a driver folder by using 7-zip but unfortunately, it does not break it down to where the actual driver setup information file is located.

So, I cannot determine if the hardware ID you posted is supported by the driver, though Intel seems to indicate that driver should have worked.