Desktop cant find drivers but laptop can.  

Run DevManView with Logitech plugged in.

?* EDIT */
And please zip both devmanviewe and setupapi.dev.log files on the laptop and upload

Here are the requested files

Also, I wouldn't think it should make a difference, but also try connecting the transceiver on the Desktop to a USB 3 port. And let's verify USB 3 drivers installed correctly

• Click the Start Orb, type msinfo32 in the search box. Hit Enter
• Click the + sign next to Components to expand it
• Click Problem Devices. Anything appear?
• If yes, click on it, Ctrl-A to select all, Ctrl-C to copy it, Ctrl-V to paste into next post
• On the other hand, if no devices are listed, tell me so

Going on from ComputerGeeks comments.
In your registry posting for the device its showing as USB3.
Compare that key to your lappy version, it WILL be different.
you could import/change the PC's regkey to usb2 only
(can see from the device pics its only USB2).

Roy

IMHO avoid mucking with the registry if at all possible. There too many things need changing to backdoor force the devices in....

I've done some more digging... Learned and found some interesting stuff.

I checked the Asus B150M-C D3 USB3 drivers for your Desktop. And, sure enough, the USB3 compatible IDs shown by the transceiver when connected to the Desktop ARE defined in those drivers. So question becomes: why isn't windows finding the USB3 hub driver when it goes searching??

Start by uninstalling and reinstalling the USB3 drivers. I see 2 versions on the support site. Be sure to choose the latest version. Connect the transceiver. Still same problem?

Coz its identifying it as 3 in that registry key.
which is the basis for its search in the driver store.

Roy

Edit Should read
MIS-indentifying

torchwood said:

Coz its identifying it as 3 in that registry key.
which is the basis for its search in the driver store.

Roy

Edit Should read
MIS-indentifying

Another thing i learned from digging. I was wrong. Apparently the Compatible IDs may get tweaked based on the hardware.

fyi... Windows searches through driver folders as well as the driver store looking for string matches on the IDs. It's the string match that's important. Changing 2/3 in the registry won't have an affect on string matching

ComputerGeek said:

I'm very confused by results. I'll explain so you can help double check on your end. Perhaps I'm misunderstanding the files you sent me

Every Plug and Play device (incl your Logitech receiver) has a set of IDs burned into its firmware by the vendor. These IDs include
> Hardware IDs and
> Compatible IDs.

You can verify the IDs assigned using Device Manager. Right click the device->Properties->Details tab. Then use the pull down menu and select Hardware IDs. Likewise, select Compatible IDs. Windows uses these IDs to find a driver for the device. In general, Windows prefers using a driver that can support a Hardware ID. But if none found, it looks for a driver that can support a compatible ID

To best of my knowledge, I'm under the impression the IDs retrieved from the device should be the same whether from a Desktop or Laptop running Win 7, Win 10 or even Linux!! The IDs are burned into device firmware so are independent of external device or OS retrieving them. BUT, in your case, when i look at the setupapi.dev.log files the compatible IDs I see for the device on the laptop are different then the Desktop! (I don't understand why or if maybe i'm looking at two different devices)

• On the laptop, the compatible IDs i see are for a USB 2 hub. Windows installs the USB 2 hub drivers.
• But on the Desktop, the compatible IDs are for a USB 3 hub!?? For whatever reason, the USB 3 hub drivers aren't found.

1. Can you manually check the IDs using Device Manager on both Desktop and Laptop and print screen shots or can even just copy/paste the IDs displayed. Insert the device, open Device Manager and use Properties->Details to display each set of IDs
2. The DevManView for the laptop. Was the device inserted? Under DeviceInstanceID column i expected to see one that starts with the hardware ID of your transceiver usb\vid_046d&pid_0b06

/* EDIT3*/But I didn't see it there. If you insert the transceiver, can you check it yourself? I'm guessing you'll see it listed as a USB2 hub. Based on setupapilog appears this transceiver installs itself as a hub, not a composite device/* end EDIT3 */

Setupapi.dev.log on the Desktop: note compatible ID strings start iusb3

Code:

>>>  [Device Install (Hardware initiated) - USB\VID_046D&PID_0B06\5&20c67efd&0&6]
>>>  Section start 2016/10/23 06:29:15.592
     ump: Creating Install Process: DrvInst.exe 06:29:15.602
     ndv: Retrieving device info...
     ndv: Setting device parameters...
     ndv: Searching just Driver Store...
     dvi: {Build Driver List} 06:29:15.702
     dvi:      Searching for hardware ID(s):
     dvi:           usb\vid_046d&pid_0b06&rev_0100
     dvi:      Searching for compatible ID(s):
     dvi:           iusb3\class_09&subclass_00&prot_00
     dvi:           iusb3\class_09&subclass_00
     dvi:           iusb3\class_09

Yet Setupapi.dev.log on laptop show something different. Compatible ID strings that start usb\

Code:

>>>  [Device Install (Hardware initiated) - USB\VID_046D&PID_0B06\5&6c72b18&0&2]
>>>  Section start 2016/10/21 19:11:15.611
     ump: Creating Install Process: DrvInst.exe 19:11:15.611
     ndv: Retrieving device info...
     ndv: Setting device parameters...
     ndv: Searching just Driver Store...
     dvi: {Build Driver List} 19:11:15.954
     dvi:      Searching for hardware ID(s):
     dvi:           usb\vid_046d&pid_0b06&rev_0101
     dvi:           usb\vid_046d&pid_0b06
     dvi:      Searching for compatible ID(s):
     dvi:           usb\class_09&subclass_00&prot_00
     dvi:           usb\class_09&subclass_00
     dvi:           usb\class_09

Desktop Under Other in Device Manager with yellow ! - It says Logitech BT mini reciever

Desktop Harware ID: USB\VID_046D&PID_0B06&REV_0100

Desktop Compatible ID: IUSB3\Class_09&SubClass_00&Prot_00
IUSB3\Class_09&SubClass_00
IUSB3\Class_09


On the Laptop I have 2 instances of USB Input Device under HID as in the following screenshot:

Same item, Same serial but different product id. (SOMETHING VERY IMPORTANT I SHOULD MENTION ---> I have 2 of these things. WHen the 1st one stopped working I opened the new one to test to make sure it wasn't the stick itself. So I could have plugged the old one into the laptop before I'm not sure but the old one is put away now and the new dongle is guaranteed from here on.)

In the laptop In USBDveiw the last part of the instance id for the new one which we are working with is C0367 and the old logitech was F203 something. I uninstalled the old logitech with F203 and now only have the new one that is C0367 to deal with.

I did install the driver in the laptop for the old stick when I set up that laptop a long time ago.

Now whats left on the Laptop is
Laptop Hardware ID: USB\VID_046D&PID_C71B&REV_0100
USB\VID_046D&PID_C71B

Laptop Compatible ID: USB\Class_03&SubClass_01&Prot_01
USB\Class_03&SubClass_01
USB\Class_03
The other says

Laptop Hardware ID USB\VID_046D&PID_C71C&REV_0100
USB\VID_046D&PID_C71C

Laptop Compatible ID USB\Class_03&SubClass_01&Prot_02
USB\Class_03&SubClass_01
USB\Class_03

ComputerGeek said:

Also, I wouldn't think it should make a difference, but also try connecting the transceiver on the Desktop to a USB 3 port. And let's verify USB 3 drivers installed correctly

• Click the Start Orb, type msinfo32 in the search box. Hit Enter
• Click the + sign next to Components to expand it
• Click Problem Devices. Anything appear?
• If yes, click on it, Ctrl-A to select all, Ctrl-C to copy it, Ctrl-V to paste into next post
• On the other hand, if no devices are listed, tell me so

This is the result of plugging it into a blue 3.0 port on the back of the desktop motherboard