How to uninstall Logitech G HUB on Windows
Save any device profiles and settings you need before removing G HUB. This check covered Logitech G HUB 2026.6.981214, installed per machine through elevated winget; device pairing and settings recovery were not tested.
Remove G HUB
Quit G HUB and its agent and tray processes in Task Manager. Use Settings › Apps › Installed apps › Logitech G HUB › Uninstall. The registered vendor command opens its own interface. Keep Save my current settings at the vendor default, press Uninstall, then Quit on the success page. Its temporary self-copy remains active until Quit is pressed.
winget uninstall --id Logitech.GHUB --exact delegates to the vendor command. This check used that command through Mole, not a separate winget removal. Do not assume it is a silent NSIS uninstaller.
Observed locations
| Location | What Mole offers |
|---|---|
%ProgramFiles%\LGHUB |
Program files, selected by default |
%ProgramData%\LGHUB |
Application data, unchecked review |
%ProgramData%\LGHUBData\applications |
Application database, unchecked review |
%ProgramData%\Logi\GHUB\Logs |
Installer logs, selected by default |
%LOCALAPPDATA%\LGHUB |
Application data, unchecked review |
%APPDATA%\lghub |
Application data, unchecked review |
%APPDATA%\G HUB |
Application data, unchecked review |
Public Start Menu and Desktop Logitech G HUB shortcuts |
Owned shortcuts, selected by default |
HKCU\SOFTWARE\Classes\lghubapp |
Owned user protocol, selected by default |
HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\LGHUB |
Owned startup value, selected by default |
Keep %APPDATA%\LGHUB_BKP, which the vendor created with Save my current settings selected, and HKCU\SOFTWARE\Logitech\LGHUB\Data. The backup contained six files totallingafter this retake; recovery was not tested. Shared Logi and Logitech namespaces, Trueforce, wheel_sdk, Direct Input Force Feedback and Logishrd components remain. They were empty in this VM; that does not establish they are disposable on another PC. Unproven Sentry namespaces and machine configuration keys are also retained.
Check the result
Get-Process 'lghub','lghub_agent','lghub_system_tray','lghub_updater' -ErrorAction SilentlyContinue
Test-Path "$env:ProgramFiles\LGHUB" -ErrorAction Stop
Test-Path "$env:ProgramData\LGHUB" -ErrorAction Stop
Test-Path "$env:ProgramData\LGHUBData\applications" -ErrorAction Stop
Test-Path "$env:ProgramData\Logi\GHUB\Logs" -ErrorAction Stop
Test-Path "$env:LOCALAPPDATA\LGHUB" -ErrorAction Stop
Test-Path "$env:APPDATA\lghub" -ErrorAction Stop
Test-Path "$env:APPDATA\G HUB" -ErrorAction Stop
Test-Path 'HKCU:\SOFTWARE\Classes\lghubapp' -ErrorAction Stop
(Get-Item 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run' -ErrorAction Stop).GetValueNames() -contains 'LGHUB'
Get-CimInstance Win32_Service -ErrorAction Stop | Where-Object DisplayName -eq 'LGHUB Updater Service'
winget list --id Logitech.GHUB --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. The startup expression is True when LGHUB remains registered. All seven selected folders, the protocol, startup value and exact uninstall registration were absent, and no owned process or updater service remained.
What Mole lists
The table accounts for eleven rows because the two shortcuts are separate. Usage records are a twelfth selected row. Five data rows start unchecked. This test explicitly selected application data, and all twelve outcomes were Removed or Missing. Files are recycled and selected registry targets are backed up before removal. Another installed copy keeps 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.
