Generally USB drivers are supplied as part of the Windows 10 Operating System, sometimes, your PC manufacturer will supply specific USB hub drivers. Open Device Manager (accessible by right. The latest AMD Radeon Windows 10 driver is the AMD Adrenalin 20.45 Suite (Released 2021-02-01). These drivers are also called the AMD Catalyst Drivers, and they include everything you need for your AMD/ATI video card to work in Windows 10.
-->Starting with Windows Vista, the driver store is a trusted collection of inbox and third-party driver packages. The operating system maintains this collection in a secure location on the local hard disk. Only the driver packages in the driver store can be installed for a device.
When a driver package is copied to the driver store, all of its files are copied. This includes the INF file and all files that are referenced by the INF file. All files that are in the driver package are considered critical to the device installation. The INF file must reference all of the required files for device installation so that they are present in the driver store. If the INF file references a file that is not included in the driver package, the driver package is not copied to the store.
The process of copying a driver package to the driver store is called staging. A driver package must be staged to the driver store before the package can be used to install any devices. As a result, driver staging and device installation are separate operations.
A driver package is staged to the driver store by being verified and validated.
Verifying the driver package integrity
Software integrity has become a top priority for Independent Hardware Vendors (IHVs) and Original Equipment Manufacturers (OEMs). Concerned by the increase in malicious software on the Internet, these customers want to be sure that their software has not been tampered with or corrupted.
Before a driver package is copied to the driver store, the operating system first verifies that the digital signature is correct. For more information about digital signatures, see Driver Signing.
Validating the driver package
The operating system validates the driver package in the following ways:
- The current user must have permission to install the driver package.
- The INF file of the driver package is syntactically correct, and all files referenced by the INF files are present in the driver package.
After a driver package has passed integrity and syntax checks, it is copied to the driver store. Afterwards, the operating system uses the driver package to automatically install new devices without requiring user interaction.
Once files are staged to the driver store, they should not be removed or modified in any way. Additionally, new files should not be added to the driver store outside of the staging process. This includes files being added, removed, or modified directly through programmatic calls, or indirectly through INF directives that will be processed at a later time.
-->Important
This topic is for programmers. If you are a customer experiencing Bluetooth device installation issues see Pair a Bluetooth device in Windows
There are two installation types for Bluetooth profile drivers:
Client-side installation for remote devices where the remote device advertises its services and the computer connects to it. Examples include: mouse devices, keyboards, and printers.
Server-side installation where the computer advertises services and remote devices can connect to the computer to use those services. For example, a vendor could author a server-side installation to enable a PDA to print to a printer attached to the computer.
These two installation types require different installation procedures.
Installing a Client-side Profile Driver
A user that wants to use a Bluetooth-enabled device will bring the device within range of the computer and initiate a connection from the computer to the remote device using the following installation sequence for a client-side profile driver.
Launch Bluetooth Devices in Control Panel to find all devices within range of the computer.
Select the device to pair with.
Pair (or bond) the device with the local radio. This may or may not involve a PIN exchange.
The local radio issues an SDP inquiry to identify the services supported on the remote device.
The Found New Hardware Wizard searches for appropriate drivers on the local hard disk drive, and/or on Windows Update.
If the Found New Hardware Wizard does not find an appropriate driver for the device, it prompts the user to insert the profile driver installation media that contains the profile driver's device setup information file (INF file).
Installing a Server-side Profile Driver
The Bluetooth driver stack supports service GUIDs as defined by the Bluetooth SIG, as well as custom GUIDs (that is, GUIDs that are not defined by the Bluetooth SIG).
Note
The Guidgen.exe tool provided with the Microsoft Windows SDK can be used to create custom GUIDs.
A user-mode installation application must be written to expose computer functionality that remote Bluetooth devices can use.
The installation application must communicate with the Bluetooth driver stack to create a service GUID for the functionality to expose. Vendors specify the service GUID in the application and in their device installation INF file.
The installation application must call the user-mode API BluetoothSetLocalServiceInfo. Before the application can call this API the application must have the SE_LOAD_DRIVER_NAME security privilege. The following code example demonstrates how to obtain this privilege. Note that the example does not demonstrate error handling.
Profile Driver INF file
A profile driver's INF file contains information about a Bluetooth device for client-side installation. For a server-side installation, the INF file specifies a device ID that corresponds to the service GUID created by the installation application. All Bluetooth devices are members of the Bluetooth class. The Bluetooth class installer (Bthci.dll) assists in installing profile drivers.
For more information about creating and distributing INF files and installing drivers, see Creating an INF File and INF File Sections and Directives.
Plug and Play IDs
The Bluetooth driver stack generates hardware IDs according to the following templates:
BTHENUM{ ServiceGUID}_VID& nnnnnnnn
BTHENUM{ ServiceGUID}_VID& nnnnnnnn_PID& nnnn
BTHENUM{ ServiceGUID}_LOCALMFG& nnnn
The Bluetooth driver stack generates compatible IDs according to the following template:
- BTHENUM{ ServiceGUID}
Free Microsoft Drivers Windows 10
ServiceGUID is a 16-bit GUID expanded into a 128-bit GUID, as defined by the Bluetooth specification. For example, {00001124-0000-1000-8000-00805F9B34FB} corresponds to an HID device.
The 8 digits following VID& correspond to the vendor ID code.
The 4 digits following PID& correspond to the product ID code.
The 4 digits following LOCALMFG& correspond to the manufacturer of the local Bluetooth radio.
The VID/PID and LOCALMFG tags are independent of each other.
The most generic device ID is a ServiceGUID by itself. For example:
BTHENUM{00001124-0000-1000-8000-00805F9B34FB}
The Bluetooth driver stack can be restricted to load your profile driver and software to run only on a specific release of a remote device by using Plug and Play IDs in both the remote device and the INF file. Note that the Bluetooth driver stack generates a VID/PID pair only if the device publishes a Plug and Play ID that the stack can detect using SDP. For example:
BTHENUM{00001124-0000-1000-8000-00805F9B34FB}_VID& nnnnnnnn_PID& nnnn
The Bluetooth driver stack can be restricted to load profile driver and software to run only on a specific local Bluetooth radio by specifying the LOCALMFG tag in the device ID in your INF file. For example:
Microsoft Drivers For Windows 7
BTHENUM{00001124-0000-1000-8000-00805F9B34FB}_LOCALMFG& nnnn
Comments are closed.