So, I’m a gamer.
And I’ve sort of settled on the Logitech series of gaming gear, C920, G213, G602. Running their gaming software (except for the overwolf overlay, I don’t need it, don’t stream).
Something that has kind of been nagging me, on the lower end of reality, is that when I set my mouse DPI, or notification preferences, post-reboot, they all disappeared. So at 5 am this morning I decided to find out why.
The answer is, for some reason, part of the tools installed by Logitech, namely LCore.exe in “C:\Program Files\Logitech Gaming Software”, does not run elevated by default. Why doesn’t it? I don’t know. Why does it need Administrator right? That’s actually a good question. I found tons of ACCESS DENIED events when I reproduced setting the check boxes as I preferred in the
To fix this do the following:
- press the Windows Key + X
- Select File Explorer
- paste C:\Program Files\Logitech Gaming Software in the address bar and hit enter
- Right click on LCore.exe and select Properties
- Click the tab Compatibility
- Check the box for Run As Administrator and click OK
- Close File Explorer. Reboot.
Now you should have a system that saves your settings you want, like mouse DPI scaling, or button preferences, or not getting a notification Every Single Time you run a game that has a profile!
Proof in the pudding
I checked the rights assignment. I tried changing rights on the regkey from the default, but the issue persisted. It probably has other keys it is trying to use, that are not located in HK_Local_Machine, but it’s 6:13 AM and I’m doing this pro bono, so maybe Logitech can noodle the specifics out and make a better installer for next rev.
Here’s what the registry rights were:
- What up? Nadda, you?
- Why did you get lazy and not figure all this out and document it for Logitech? I’m kinda tired right now, might edit after I sleep again.
- What is the security impact of running LCore as administrator? It runs as administrator so it can screw stuff up if it gets exploited, etc. This is a design flaw of some kind in how they either 1) packaged the installer or program; or 2) a poorly tested solution. Well, or 3) both.
I personally had this issue, but it’s well documented at many places as a problem;