I’ve found a couple of threads on the Logitech discussion boards and Reddit that discusses this dialog. Most consumers would be unaware and not care in the slightest about this unwanted data collection, had it not been for the crash dialog on startup. I do find it worrying that there isn’t an easily available privacy policy that explains what the Analytics Client does and what type of data it collects. It could be a key-/mouse-click logger for all I know. However, I’ve been unable to find a privacy policy that covers the data collected by Logi Analytics Client. The Logi Analytics Client is clearly some sort of feedback collection service that’s supposed to run in the background to gather feedback on how I use the mouse and its configuration. Even before the Windows shell is displayed, I got a problem report from Windows saying that “Logi Analytics Client (UNICODE) has stopped working”. When I installed the Logitech Gaming Software I got an unwanted additional component that caused problems every time I logged in to Windows. Notably, this is the only option that has to be applied anew if you plug the G403 into another USB port on your computer. It took a little while, but I eventually found an option called “Device Startup Effects”. Regardless, this option was not to blame. Despite being presented as a on-board memory configuration option, the lighting sleep timer only works on Windows with Logitech Gaming Software installed. This feature would turn off the lights after a configurable amount of inactivity. I found an option called “Lighting Sleep Timer” in the Lighting section in the Gaming Software center.
I also noticed a firmware update for the mouse (!), but applying this didn’t resolve the problem but did instead introduce new issues (!) which I’ll get back to later. But the problem would reappear after a reboot. Notably, the lighting effects also came on again after opening Logitech Gaming Software. I opened Logitech Gaming Software again, and every lighting setting appeared to be correct.
The mouse has some internal memory for storing configuration, so I assumed the configuration must have been changed during the software installation. The problems persisted even when I plugged the mouse into different computers running Linux or MacOS. The same would happen again just before the Windows boot sequence finished (which causes the internal USB hub to power cycle.) The LEDs on the mouse would flash a couple of times and then turn off right after powering on the system. I noticed some new issues even before the system had rebooted. This seems more than a little excessive just to support a mouse but I went ahead and rebooted anyway. I was prompted to reboot the system after installing Logitech Gaming Software. Stopped working after installing Logitech Gaming Software
The basic operations of the mouse worked fine as well that’s until I installed Logitech’s management software. The factory default lighting effects on the G-logo and the scroll wheel worked fine out of the box on MacOS 10.12, Linux (Fedora 27), and Windows 10. This specific model seems to have a multitude of issues, so rather than a review I’ll just detail the issues I’ve encountered and you can make up your mind about the quality of the G403. The Logitech G403 wired (also available wireless) is a ‘gaming mouse,’ which means it’s high-sensitivity, is more expensive, and is decorated with pulsating and colorful LEDs.
But it does have pretty pulsating colored lighting effects at least until you install their the Logitech Gaming Software. The Logi G403 gaming mouse has issues with everything from hardware design to its firmware and software.