Logitech M171 Drivers

[Rebecca Donnelly]

Ihave a Logitech m525 mouse that I use at work (Win 7 32-bit). For the first little while, I would take the mouse home with me which meant unplugging the Unifying receiver. After a few times doing this however, I noticed that if I plugged the Unifying receiver back into a previously installed port, it wouldn't work. Over time, I've actually run out of ports to plug this device into. I get the following "USB Device Not Recognized" error:

This is typical behavior of a broken/worn down unifying receiver. The only way to fix this is to purchase another. However, you'll have to setup your old devices to the new receiver using Logitech's software.

This may have to be done with each new computer you use the mouse/new unifying receiver with. Although after a fresh install of Windows 8, my receiver picked up the mouse just fine without any of the Logitech software.

If the Receiver isn't being recognized it is not necessarily broken. I plugged my t600 receiver into my pc (win 7 64bit) and i am having these same problems. I move over to my laptop (windows 8) with the same receiver and i can use the mouse with no difficulty. There is something about windows 7 64 bit that is having issues with this. Test your receiver on a different device before claiming its broken. or returning your product. Chances are you may be able to make this work.

This seems to have affected not just logitech unifying receivers, but all USB Composite Devices.My Android tablet is also affected, as well as my Microsoft Xbox 360 USB Controller receiver, since it has two 360 pads sync'd to it, but my wired PowerA Minix360 is not affected. My microsoft wired keyboard 600 and logitech V220 are also not affected, as they are not 'USB Composite Device', but 'USB Human Interface Device'.

USB Composite Device is used to wrap up multiple child Devices in a single parent Device, such as two USB Human Interface Device endpoints (One for keyboard, one for mouse) like the Logitech Unifying Receiver does.

My Logitech USB receiver had similar problems to those above. Drivers were not available or couldn't be found. I tried everything. Turned out it was a problem with the last Windows Update 2/13/2018. The link below shows you how to go into the Device Manager and command prompt to uninstall the last update. Not sure if it only uninstalled it or if it uninstalled and then re-installed with a fix, but my mouse and keyboard are working again. See link and explanation below.

After installing this update, some USB devices and onboard devices, such as a built-in laptop camera, keyboard or mouse, may stop working. This may occur when the windows update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.Microsoft is working on a resolution and will provide an update in an upcoming release.Workaround steps are available in KB4091240.

This issue occurs when the Windows Update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance. Resolution

I opened my 2 Logitech receivers (as suggested in the youtube video) and the four copper pads appeared highly corroded with a great deal of black oxidation on the leads. I could not get them to work by stuffing a piece of paper between the circuit board and USB housing, as suggested in the video, but I was able to hold the USB receiver inside the laptop USB port with my hand and it was recognized. However a few moments later and I probably quivered and lost electrical contact, and it said, "USB port not recognized" after having formerly recognized it.

You probably need a new receiver, or you can follow the youtube video, take apart the nub, and try to put it together so it will work. I must say, you may not have good luck, the manufacturing quality of this USB transceiver is horrible, Logitech, shame on you!

In my case, the copper line (path, whatever) was broken. You need to connect it by soldering. It will work. I attached a photo with a possible broken line (see photo). It was #3 in my case. First, open it with pliers than pull out the logic board and fixsee the logic board and possible broken line place.Hope it helps!

I had a similar issue. In my case I found the USB receiver actually pushed slightly too far in to the port. It somehow detected as an HID Mouse but did not install properly. If I pulled it back out just a millimeter it would kick in and work just fine.

Solaar is a Linux manager for many Logitech keyboards, mice, and trackpadsthat connect wirelessly to a USB Unifying, Bolt, Lightspeed, or Nano receiver;connect directly via a USB cable; or connect via Bluetooth.Solaar does not work with peripherals from other companies.

Documentation here is for the current version of Solaar.Some Linux distributions distribute old versions of Solaar.If you are using an old version and something described here does not work you should upgradeusing one of the methods described below.

Solaar runs as a regular user process, albeit with direct access to the Linux interfacethat lets it directly communicate with the Logitech devices it manages using specialLogitech-proprietary (HID++) commands.Each Logitech device implements a different subset of these commands.Solaar is thus only able to make the changes to devices that devices implement.

Solaar is not a device driver and does not process normal input from devices.It is thus unable to fix problems that arise from incorrect handling ofmouse movements or keycodes by Linux drivers or other software.

Solaar can be used as a GUI application, the usual case, or via its command-line interface.The Solaar GUI is meant to run continuously in the background,monitoring devices, making changes to them, and responding to some messages they emit.To this end, it is useful to have Solaar start at user login so thatchanges made to devices by Solaar are applied at login and throughout the user's session.

Both Solaar interfaces are able to list the connected devices andshow information about each device, often including battery status.Solaar is able to pair and unpair devices withreceivers as supported by the device and receiver.Solaar can also control some changeable settings of devices,such as scroll wheel direction and function key behavior.Solaar keeps track of most of these settings on a per-computer basis,because devices forget most settings when powered down,and the GUI application restores them whenever a device connects.For more information on how to use Solaar seethe usage page,and for more information on its capabilities seethe capabilities page.

Solaar's GUI normally uses an icon in the system tray and starts with its main window visible.This aspect of Solaar depends on having an active system tray, which is not the defaultsituation for recent versions of Gnome. For information on to set up a system tray under Gnome seethe capabilities page.

Solaar has progressed past version 1.1. Problems with earlier versions shouldnot be reported as bugs. Instead, upgrade to a recent version or manually installthe current version from GitHub.Some capabilities of Solaar have been developed by observing the behavior ofLogitech receivers and devices and generalizing from these observations.If your Logitech receiver or device behaves strangely this may be caused byan incorrect behavior generalization.Please report such experiences by creating an issue inthe Solaar repository.

Solaar will detect all devices paired with supported Unifying, Bolt, Lightspeed, or Nanoreceivers, and at the very least display some basic information about them.Solaar will detect many Logitech devices that connect via a USB cable or Bluetooth.

Solaar can pair and unpair a Logitech device showing the Unifying logo(Solaar's version of the logo)with any Unifying receiver,and pair and unpair a Logitech device showing the Bolt logowith any Bolt receiver,andcan pair and unpair Lightspeed devices with Lightspeed receivers for the same model.Solaar can pair some Logitech devices with Logitech Nano receivers, but not all Logitechdevices can be paired with Nano receivers.Logitech devices without a Unifying or Bolt logogenerally cannot be paired with Unifying or Bolt receivers.

Up-to-date prebuilt packages are available for some Linux distros(e.g., Fedora 33+) in their standard repositories.If a recent version of Solaar is notavailable from the standard repositories for your distribution, you can tryone of these packages.

Bluez 5.73 does not remove Bluetooth devices when they disconnect. Solaar 1.1.12 processes the DBus disconnection and connection messages from Bluez and does re-initialize devices when they reconnect. The HID++ driver does not re-initialize devices, which causes problems with smooth scrolling. Until the problem is resolved having Scroll Wheel Resolution set to true (and not ignored) may be helpful.

The Linux HID++ driver modifies the Scroll Wheel Resolution setting to implement smooth scrolling. If Solaar changes this setting, scrolling can be either very fast or very slow. To fix this problem click on the icon at the right edge of the setting to set it to "Ignore this setting", which is the default for new devices. The mouse has to be reset (e.g., by turning it off and on again) before this fix will take effect.

The driver also sets the scrolling direction to its normal setting when implementing smooth scrolling. This can interfere with the Scroll Wheel Direction setting, requiring flipping this setting back and forth to restore reversed scrolling.

The driver sends messages to devices that do not conform with the Logitech HID++ specification resulting in responses being sent back that look like other messages. For some devices this causes Solaar to report incorrect battery levels.

Solaar normally uses icon names for its icons, which in some system tray implementations results in missing or wrong-sized icons. The --tray-icon-size option forces Solaar to use icon files of appropriate size for tray icons instead, which produces better results in some system tray implementations. To use icon files close to 32 pixels in size use --tray-icon-size=32.

3a8082e126