Years ago I wrote about the Logitech’s LVUSBSta.sys driver that corrupted the USB and audio stack when installed. For a long time, I no longer bought Logitech because even if the hardware is mostly good, software was not. For a while I bought Microsoft devices, which usually worked without issues. Now Microsoft got out from that business, so I returned to Logitech, especially because the new MX Creative Console looked interesting. Wrong move, it looks.
When I connected an MX keyboard, it installed its Logi Options+ software as well. Now, that “utility” consumers 12-15% of CPU continuously, and makes some application less responsive.
On my eight core machine it means more or less something keeping a single core 100% busy. And look at the call stack of the thread:
ntdll.dll!memset+0x2f4e
ntdll.dll!RtlFreeHeap+0x51
ucrtbase.dll!free_base+0x1b
logioptionsplus_agent.exe!logi::LoupedeckConnector::isGetUserInfoDelegateRegistered+0x725dc5
logioptionsplus_agent.exe!logi::LoupedeckConnector::isGetUserInfoDelegateRegistered+0x725b09
logioptionsplus_agent.exe!logi::LoupedeckConnector::isGetUserInfoDelegateRegistered+0x72530e
ucrtbase.dll!configthreadlocale+0x92
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21It looks the acquisition of Loupedeck by Logitech brought some merging issues. And what “GetUserInfo” call it is attempting and why? And why it doesn’t accept a “no” answer and stops there? Probably, if software tried less to track users, it would work better and use less resources.
Moreover, there is no way to file a bug report to Logitech easily. Probably they worry to be submerged by tons of them. It looks this one is not the first version with such issues, there are several reports in the past years too. Someone has to remember Logitech that “errare humanum est, perserverare autem diabolicum”. Just like the eccessive use of lame, cheap developers and lack of proper testing.