Logitech Receiver not working

Hello all, I feel a bit sheepish coming here with such a common "novice" issue however, it seems it is a fairly extensive, less user-error oriented problem than I was hoping for.

I have 5 logitech devices I am trying to connect to my machine. (Well, actually only 3 but 2 kb/mouse combos) and, I have had this setup before, many times however cannot get it to work.

The receiver that came with my Logitech 650 deluxe keyboard just WILL NOT work in Windows. I can use my keyboard in the BIOS, I can use it on my iBook, I can even use it on another windows 7 Pro x64 machine but it just won't work with the machine I am stuck using primarily.

The Devices I have are:
2 Logitech wireless Keyboards
-650 Deluxe
-EX110
2 Logitech wireless mice
1 Logitech M510 w/ unifying receiver
1 Logitech C-BT44 Receiver (came with 650 deluxe)
1 Logitech receiver unknown (had to fix this bad boy...previous owner cut the cord to deter others from using it)

The unknown receiver works with either keyboard/mouse (not the m510 obviously) which, seeings as they all share the same frequency (RF 2.4GHz) is obviouse why they work together. BUT, NONE of the keyboards work on my primary box with the C-BT44 receiver within windows. Again, I can use that receiver in the BIOS, Both normal lights are on (F and Num lock) along with my 650 deluxe but, it just doesn't work in windows. It USED to work in windows. I originally had one keyboard on my desk (650) and the other (connected to the unknown receiver) keyboard (110) on my coffee table half-way across the room. This worked wonderfully. Well, not anymore. Obviously I can't have both keyboards connected to the same receiver as they are apparently made to only work with one keyboard and mouse at the same time so, I am stuck with just the one working keyboard on the less desirable receiver.

My thoughts are, is there a way to uninstall/remove all the PnP USB device history/drivers so that windows will automagically find/install the drivers on next boot? I know there was a sweet little app that did exactly that (among many other things) for XP but those days are past. The receiver that is NOT working in windows works perfectly wither in the BIOS or on other machines, just not the one I currently have to use...

Any insight would be great!! I almost traced the issue back to when I installed the M510 mouse/drivers/unifying software but only almost.

Thanks all! Hopefully we have some ideas here.

Well...7 restarts later, still having the same problem. I took both Britton30's and pooch's advice and it's a no go...BUT, The function light and Num-lock light on the Logitech receiver are both on now! (Before it was only the Function light) This isn't solving anything within windows, just a development. My hunch is that something went awry when I installed my Logitech M510 mouse. I had both keyboards working fine with the computer prior to getting the mouse and had the mouse connected to a different computer and used synergy to KM switch with it. Both keyboards and M510 worked on THAT computer though. Also, If I remove the M510 receiver, uninstall everything from it (Drivers, software, etc...) the non-functional receiver STILL doesn't work so it doesn't seem an issue with too many receivers.

I'm planning to *sigh* reinstall Windows this weekend and solve this, amongst other small issues I've been having. I'll try a repair install first and if a few of the small quirks are fixed, be content with that but if my computer is still acting not-quite right, may just break down and fresh install. (Err...possibly re-image it if I can find an image on location. Currently away from my backups though...soo much good their doing now :P) This is BY FAR my weakest computer that I rely on so I expect more than the usual amount of problems with it but it is nice when things just work.

Thanks for the input, if anyone knows any other possible solutions, I would LOVE to give them a try and avoid a wipe but I suppose I will prepare for the worst.

(Note: The receiver in question STILL works on my iBook, Win 7 x64 laptop, THIS machines and BIOS along with the other receiver/keyboard combo. Apparently something just got a bit too mingled somewhere in the mix within THIS win install)

No luck. Ended up reinstalling Windows 7 and works just fine. I followed everything posted here and no luck as well as other ways of deleting/clearing USB device history and drivers. Not sure what the problem was but it's taken care of now I suppose. This is marked as the best answer because it states how the problem was worked around, not necessarily the ONLY way to fix it though.

I realize that this is an old thread, but I wanted to post the solution to this problem just in case someone came across the thread via a web search. I had this problem and like everyone else I wanted to hit my head against the wall. Then by pure happenstance I came across the solution (kinda like discovering penicillin). I testing this on 3 different machines all running Windows 7 64-bit (these were the three machines where I ran into this problem) and had success each and every time.

The solution is this: install SetPoint first.

So if you already have the unifying software installed, uninstall it. I use IObit Uninstaller because once the app/program is uninstalled it will perform what it calls a "Powerful Scan". Basically, IObit Uniinstaller will search for any thing lingering behind that the 'uninstall' process didn't delete (ie. registry keys). Once the 'powerful scan' is complete IObit Uninstaller will display a results window where you'll have the opportunity to pick and choose or to 'select all' before any of the lingering remnants are actually deleted.

After I uninstalled the Unifying software I rebooted. After the reboot I installed SetPoint (I preferred to use the full installer and not the Smart Installer). Once SetPoint was installed I proceeded with installed the Unifying Software. After installed both I performed another reboot (just for good measure).

At that point the Logitech Unifying Software should be working properly and the unifying dongle should have been found and installed during the installation of the unifying software.

I hope this works as pain-free for everyone else as it was for me.

paulnozicka said:

I realize that this is an old thread, but I wanted to post the solution to this problem just in case someone came across the thread via a web search

[ . . . ]
[ . . . ]
[ . . . ]

I hope this works as pain-free for everyone else as it was for me.

Dayum. I was hoping this would do it, but no such luck. 'S ok though, gives me a good excuse to throw out this piece of crap finally        I like that you posted it despite the time lapse though, because you're right, people do come across old threads via their Google search results, all the time in fact.