Hi everyone!

I've been struggeling with trying to pre-install the "Bluetooth by HP" (Widcomm) drivers for my Laptop-users for a while.
The original problem is that the Bluetooth interface isn't detected/installed during deployment of the ÔS on the computer, the hardware appears when the user pushes the Wireless button or starts the preinstalled Bluetooth-software for the first time.

Since this is a locked down environment, the users does not have the administrative rights needed to install the device at this time.

The drivers are unsigned, (BTWUSB.SYS, BTWUSB.INF and BTWUSB.CAT), hence the catalogfile just contains the note "This catalog file should be replace with a real digital signature from Microsoft".

So, I tried to pre-install the driver with DPINST 2.01, using the legacy (LM-switch). After commenting out the reference to the catalogfile from the INF, it seemed to succeed.

But when I log on as a user and active the bluetooth-interface for the first time, I still get faced with the message;

"You must be a member of the admin group on this computer to install this hardware; Bluetooth by HP".

The Unsigned driver installation behaviour policy is set to "silently succeed" on the machines, but this does not seem to do any difference here.

Is there anything I could do, or am I completely of the track here?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


The driver must be signed otherwise will the user need to have administrative privileges.
Try use signability tool to create a CAT file for the driver
Answered 05/29/2006 by: AngelD
Red Belt

Please log in to comment
I see, but then I really don't understand the point in pre-installing unsigned drivers in legacy mode at all?
Why did they implement this option?

Answered 05/30/2006 by: beekey
Senior Yellow Belt

Please log in to comment
I don't know, maybe for local administrators

DpInst was in the beginning a tool for developers to test their drivers.
Answered 06/01/2006 by: AngelD
Red Belt

Please log in to comment