Include Bluetooth driver in WinPE

Hello,

Perform an analysis of your hardware, and you will surely find the Bluetooth driver to install.

https://www.driverscloud.com/fr

It may be possible to find the driver directly in a folder

(Files like .sys .inf .cat)

Or it may be possible to extract it using 7-Zip

https://www.7-zip.org/download.html

Or it may be located in (Do a Search) %LocalAppData%\Temp (Upon execution)

You can include it in AOMEI PE Builder during creation.

Practice this driverscloud! I have therefore performed a detection and it gave me the following link:

https://www.driverscloud.com/fr/configuration/s406dydwgkd-1/resume-asustek-computer-inc-z87-pro-rev-1xx

But which drivers to include so that my Bluetooth keyboard and mouse are recognized by WinPE does not seem easy to identify; there are several possible candidates:

Probably the:

"Driver 3" which is called "Bluetooth HMI Device" and corresponding to "hidbth.inf"

"Driver 73": Bluetooth Device and corresponding to "tdibth.inf"

"Driver 74": Bluetooth Device and corresponding to "bthpan.inf"

"Driver 80": Keyboard K380, which is indeed my current keyboard and corresponding to "bth.inf"

"Driver 89": BT 5.1 Mouse, and corresponding to "btheenum.inf"

"Driver 114": Qualcomm Atheros AR9462 and corresponding to "oem64.inf"

"Driver 167": HMI Mouse and corresponding to "msmouse.inf"

In short, I would like to know which ones to include in my bootable WinPE USB...!!

Thank you

Probably the first, but it also offers to download.

But downloading is probably for updates, while what I'm interested in is knowing which drivers to add to WinPE from AOMEI PE Builder.

If I add them all, I assume there are no contraindications, right?

Moreover, the Qualcomm Atheros driver seems essential to me since it's the Bluetooth chip of the card, and it contains a lot of files according to the Device Manager. When we check "driver details," it displays all the following files:

Qualcomm Atheros AR9642 Bluetooth 4.0 + HS adapter

C:\Windows\system32\btcoinst.dll

C:\Windows\system32\BtContectMenu.dll

C:\Windows\system32\BtContectMenu.dll.muien-US

C:\Windows\system32\DRIVERS\AtherosBT.bin

C:\Windows\system32\DRIVERS\AthrBT_0x01020200.dfu

C:\Windows\system32\DRIVERS\AthrBT_0x01020201.dfu

C:\Windows\system32\DRIVERS\AthrBT_0x011020000.dfu

C:\Windows\system32\DRIVERS\AthrBT_0x011020100.dfu

C:\Windows\system32\DRIVERS\AthrBT_0x031010000.dfu

C:\Windows\system32\DRIVERS\AthrBT_0x031010000_ss01.dfu

C:\Windows\system32\DRIVERS\AthrBT_0x031010100.dfu

C:\Windows\system32\DRIVERS\btfilter.sys

C:\Windows\system32\DRIVERS\bthport.sys

C:\Windows\system32\DRIVERS\BTHUSB.sys

C:\Windows\system32\DRIVERS\ramps_0x01020200_26.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020200_26_0x01.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020200_40.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020200_40_0x01.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020200_40_0x02.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020200_40_0x03.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020200_40_0x04.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020201_26.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020201_26_0x01.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020201_40.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020201_40_0x01.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020201_40_0x02.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020201_40_0x03.dfu

C:\Windows\system32\DRIVERS\ramps_0x01020201_40_0x04.dfu

C:\Windows\system32\DRIVERS\ramps_0x011020000_40.dfu

C:\Windows\system32\DRIVERS\ramps_0x011020100_40.dfu

C:\Windows\system32\DRIVERS\ramps_0x011020100_40_nf01.dfu

C:\Windows\system32\DRIVERS\ramps_0x011020100_40_SS01.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_0x01.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_0x11.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_0x12.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_0x21.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_0x22.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_0xf0.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_0xf1.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_LV01.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010000_40_SS01.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010100_40.dfu

C:\Windows\system32\DRIVERS\ramps_0x31010100_40_0x01.dfu

So we are far from a single ".inf" file: do I need to add them all to WinPE, right?

Moreover, when we click "add driver" from AOMEI PE Builder, it only offers the ".inf" files and not the ".sys" files, for example: should I add them using the "add files" option in AOMEI PE Builder?

This puts them in a "My Tools" folder and therefore will not be considered as drivers to load: so no keyboard or mouse at boot....

There are .sys drivers

But no .inf installation file

How did you extract that?

If you run it, do you have anything else in %LocalAppData%\Temp?

There are .sys drivers

But no .inf installation file

Exactly: there are also ".dfu" files.

I simply looked via "Device Manager" --> "Properties" --> "View Driver Details": and no ".inf" file.

If you run it, do you have anything else in %LocalAppData%\Temp?

I don't want to run it a 2nd time because it's already installed: it would mess things up... What is certain is that when we unzip the archive, there is an "install.exe" to launch, and maybe it's the one that generates an ".inf", but why wouldn't it appear when we check "driver details"??

In doubt, I opted for a more radical solution at €8: I bought a budget wired mouse (!) and secured an old wired keyboard: both will help me restore in case of problems.

I'm sure there won't be a driver to prevent me from recovering my system.

I don't like "approximate" situations on somewhat sensitive topics: especially since in 2022, integrating Bluetooth drivers into a boot medium should be the norm, it seems to me...

In any case, thank you for trying to help me!