How to uninstall Logi Options+ on Windows
Save any device settings you need before removing Logi Options+. This check covered version 2.8.981479, installed per machine through elevated winget; device pairing and settings recovery were not tested.
Remove Logi Options+
Quit Logi Options+ and its agent in Task Manager. Use Settings › Apps › Installed apps › Logi Options+ › Uninstall. The registered command is logioptionsplus_updater.exe --uninstall --full --shadow. It made a temporary self-copy during this check and completed without a confirmation window requiring input. No additional silent-installer switches were inferred.
winget uninstall --id Logitech.OptionsPlus --exact delegates to the vendor command. This check called it through Mole, not a separate winget removal.
Observed locations
| Location | What Mole offers |
|---|---|
%ProgramFiles%\LogiOptionsPlus |
Program files, selected by default |
%ProgramData%\LogiOptionsPlus |
Application data, unchecked review |
%LOCALAPPDATA%\LogiOptionsPlus |
Application data, unchecked review |
%APPDATA%\logioptionsplus |
Application data, unchecked review |
%ProgramData%\Logi\LogiOptionsPlus\Logs |
Measured installer and updater logs, selected by default |
%APPDATA%\logioptionsplus\{Cache,Code Cache,DawnGraphiteCache,DawnWebGPUCache,GPUCache} |
Five separate cache rows, selected by default |
Public Start Menu and Desktop Logi Options+ shortcuts |
Two owned shortcuts, selected by default |
HKCU\SOFTWARE\Classes\loplusapp |
Owned user protocol, selected by default |
The brace list describes five child folders, not a path to enter literally. Keep the shared Logi namespace and the empty Logi\LogiOptionsPlus parent after its Logs child is removed. ProgramData\Logi\LogiPluginService contained an empty package directory; Local\Logi\LogiPluginService contained plugin custom-action logs, including Loupedeck actions. Exclusive Options+ ownership was not established, so these component namespaces remain. A Sentry hash directory containing only a 36-byte installation identity also remains. G HUB's existing settings backup and empty shared hardware components were independently preserved.
Check the result
Get-Process 'logioptionsplus','logioptionsplus_agent','logioptionsplus_appbroker','logioptionsplus_updater' -ErrorAction SilentlyContinue
Test-Path "$env:ProgramFiles\LogiOptionsPlus" -ErrorAction Stop
Test-Path "$env:ProgramData\LogiOptionsPlus" -ErrorAction Stop
Test-Path "$env:ProgramData\Logi\LogiOptionsPlus\Logs" -ErrorAction Stop
Test-Path "$env:LOCALAPPDATA\LogiOptionsPlus" -ErrorAction Stop
Test-Path "$env:APPDATA\logioptionsplus" -ErrorAction Stop
Test-Path 'HKCU:\SOFTWARE\Classes\loplusapp' -ErrorAction Stop
Get-CimInstance Win32_Service -ErrorAction Stop | Where-Object { $_.PathName -like '*\LogiOptionsPlus\*' }
winget list --id Logitech.OptionsPlus --exact
A returned process, service or app row means it remains. Each completed Test-Path returns True for a surviving path and False for an absent path; an error leaves that check unresolved. All five selected roots and the user protocol were absent, as was the exact uninstall registration. No owned process or updater service remained.
What Mole lists
The table accounts for thirteen rows, with two shortcuts and five cache children counted separately. Usage records are a fourteenth selected row. The three data roots start unchecked, while the measured logs and regenerable cache children start selected. This test explicitly selected application data; all fourteen outcomes were Removed or Missing. Files are recycled and selected registry targets are backed up before removal. Another installed copy protects the measured data paths.
What this test covered
Tested on October 5, 2026, in a Windows 11 ARM64 VM with a Mole development build, covering first launch and uninstall. Device pairing or settings recovery, other installation channels and the released download were not verified. Automatic detection after an external uninstall was not verified.