Note: This update took a while to install even on my 3900X/NVMe system. After updating and doing another check for updates, there was another small update that installed, bumping to version 205. Working perfect with G502 Lightspeed, Powerplay, G810, G935, G560 and C922. This is a design flaw of some kind in how they either 1) packaged the installer or program or 2) a poorly tested solution. 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.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.Here’s what the registry rights were: registry rights (unmodified) 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.
I tried changing rights on the regkey from the default, but the issue persisted. Procmon showing LCore can’t access/write to its own key structure. 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
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. Running their gaming software (except for the overwolf overlay, I don’t need it, don’t stream). And I’ve sort of settled on the Logitech series of gaming gear, C920, G213, G602.
0 kommentar(er)
