Desktop cant find drivers but laptop can.  

Trying to install LOGITECH mini BT receiver for MX 5000 keyboard but Windows 7 cannot find drivers. I spent all day yesterday installing & uninstalling different versions of setpoint, installing/uninstalling drivers. THe only way I can get it to leave "other devices" in device manager is to manually install random logitech drivers that are already in windows but it says it cannot start with an error 10.

Decided to try the reciever in my laptop and it read and installed perfectly as shown by the last picture. No CD no nothing.

Any ideas of how I could get this thing going on the desktop again? I am at the point where I'm about to bulldoze through the registry and delete anything that says logitech but figured I'd check here for other ideas first.

If I use DevManView and open the registry location it goes directly to the location that shown in the registry screen shot (but of course/obviously there are way more logitech items in there than that. Thats just where it goes when I say open registry location.

The model # of this reveiver is C-UV35.

A USB transceiver installs as a "USB Composite device". I believe what you highlighted on the laptop are the two downstream devices (the mouse and keyboard) that get installed after the transceiver installed as a USB Composite Device on the laptop.

My best guess is the USB Composite driver on the Desktop is corrupt. Check and tell me if each of these files exist:
> C:\Windows\inf\usb.inf
> C:\Windows\inf\usb.pnf
> C:\Windows\system32\drivers\usbccgp.sys

Yes all three of those files exist. I should also mention for the time being until I get this logitech one working I am using an IOGEAR Bluetooth 4.0 USB Micro Adapter (GBU521) so I have a keyboard to use. Should I unplug the IOGEAR first? My mouse is corded.

You can keep the BT device connected. Let's have a look at the Device Manager installation log files if any clues

1. Follow instructions to Show Known File Type Extensions
2. Rename C:\WINDOWS\inf\setupapi.dev.log to C:\WINDOWS\inf\setupapi.dev.log.old
3. Connect the Logitech Transceiver. Wait till the error message pops up
4. Windows will have created a new C:\WINDOWS\inf\setupapi.dev.log file. Zip the new and old ones together and attach to next post

"3. Connect the Logitech Transceiver. Wait till the error message pops up"

-Plug in
-No error message came up
-Uninstall from other devices in device manager
-Unplug Logitech device
-Delete setuppapi.dev.log that was just created 30 seconds ago
-Re-plug in and another new file was created
-Error pops up this time "Logitech BT Mini-Receiver (Red X) No driver found"
-Made new folder on desktop and copied new file and .old file to new desktop folder to prepare to zip.



Here are the files

After posting I am going to put the check mark back in the hide file types area and delete the new file I just put into the ZIP file and remove .old from the original file to make it the working file again.

Hi SUN,
you might find this thread of use to you.
http://answers.microsoft.com/en-us/w...5-6e1caac8542d

note that Motherboard has special requirement for W7 did you follow those instructions.

Roy

As to the second last reply on the 1st page of that link, I do have a few close matches to that on my machine

The installation log files aren't straight forward reading. But what I can tell from first read, it looks like the transceiver device firmware is causing Windows to install it as a USB 3 device - as a USB3 hub!?? Does the laptop support USB 3 but the desktop only support USB 2?

Let's dig deeper and see if i've got the info right
> Run DevManView on the laptop, click Ctl-A to select all, then Ctl-S to save. BEFORE you save, use the pull down menu and change file Save As type to "Tab Delimited Text"
> Now zip the DevManView file on the laptop along with the setupapi.dev.log file on the laptop too and attach to next post

(EDIT: Further to my last post here is a Zip file of bcbtumsLD.inf from the bcbtumsld folder. **NOTE THE SLD AFTER BCBTUMS - ITS THE ONLY FOLDER WITH SLD** -- In that bcbtumsLD file as per the 2nd screenshot there is a Dell part. Elsewhere I have seen this Logitech dongle referred to as a Dell and sure enough in that bcbtumsLD file there is something called Dell 2.0 EDR)

ComputerGeek said:

The installation log files aren't straight forward reading. But what I can tell from first read, it looks like the transceiver device firmware is causing Windows to install it as a USB 3 device - as a USB3 hub!?? Does the laptop support USB 3 but the desktop only support USB 2?

Let's dig deeper and see if i've got the info right
> Run DevManView on the laptop, click Ctl-A to select all, then Ctl-S to save. BEFORE you save, use the pull down menu and change file Save As type to "Tab Delimited Text"
> Now zip the DevManView file on the laptop along with the setupapi.dev.log file on the laptop too and attach to next post

Laptop is 2.0 only and Desktop is freshly upgraded and now has 3.0 but its only plugged into a 2.0 USB.

EDIT: On laptop do I run DevManView with Logitech in or out?