Uninstalling Logitech G Hub software

I initially used it to re-program my Logitech mouse, but it’s causing my Mac to run hot with unchecked processes that are consuming a lot of CPU for some reason.

I found this Reddit post:

https://www.reddit.com/r/LogitechG/comments/drbl7y/how_do_i_uninstall_logitech_g_hub/

which led to this website:

https://support.logi.com/hc/en-us/articles/360023192454-G-HUB-Install-Uninstall-Update-Troubleshooting

Loosely followed the instructions for Mac, except that the directories are “Logi” instead of “LGHUB”.

Windows

Option 1 is to try to reinstall from a fresh installer. If you already have it installed and try to install again, the installer will ask to reinstall.

Option 2: Manual Removal & Reinstall

Use this method when the automatic option fails:

  1. Terminate All G HUB Processes
    1. Press Ctrl + Alt + Del → Select “Task Manager”
    2. End these processes (if present):
    3. LGHUB.exe → Right-click → “End task”
    4. lghub_agent.exe → Right-click → “End task”
    5. lghub_updater.exe → Right-click → “End task”
  2. Remove User Data
    1. Navigate to: C:\Users\[YourUsername]\AppData\Roaming
    2. Locate and delete the “LGHUB” folder
    3. Confirm deletion when prompted
  3. Remove Program Data
    1. Navigate to: C:\ProgramData
    2. Locate and delete the “LGHUB” folder
    3. Confirm deletion when prompted
    4. Locate and delete the “old.LGHUB” folder if it exists
    5. Confirm deletion when prompted
  4. System Restart
    1. Save any open work
    2. Restart your computer
  5. Fresh Installation
    1. Download the latest G HUB installer from the official link
    2. Run the installer
    3. Follow the installation prompts
    4. Launch G HUB and verify functionality

Troubleshooting Tips: Common Issues & Solutions

  • “Access Denied” errors: Ensure you’re running as Administrator
  • Folders won’t delete: Restart computer and try again
  • Installation fails: Temporarily disable antivirus during installation
  • Missing AppData folder: Type the full path in File Explorer address bar

If issues persist: Advanced Support Options

  • Check Windows Updates: Ensure your system is fully updated
  • Contact Support: If all options fail, contact Logitech support with:
    • Your specific error messages
    • Windows version information
    • Steps you’ve already attempted

Prevention Tips

  • Regular Updates: Keep G HUB updated through the built-in updater
  • Clean updates: Never exit or force exit G HUB while an update is in progress
  • Clean Shutdowns: Always quit G HUB properly before system shutdown

MacOS

Solution Options (Try in Order)

Option 1:

  1. Drag the G HUB icon to the trash to uninstall the software
  2. If this does not work, wait a few seconds and then try to uninstall again

Option 2:

  1. Quit all G HUB processes
    1. Right-click the G HUB icon in your menu bar (top-right corner of screen)
    2. Select “Quit G HUB” from the dropdown menu
    3. Alternative: Press Cmd + Q while G HUB is active
    4. Verify closure: Ensure all G HUB windows are completely closed
  2. Remove G HUB data
    1. Navigate to: /Applications
    2. Locate and delete the “lghub.app” folder
    3. Navigate to: /Users/shared/
    4. Locate and delete the “LGHUB” folder
    5. Navigate to: /Library/Application Support/
    6. Locate and delete the “LGHUB” folder
    7. Navigate to: /Library/LaunchAgents
    8. Locate and delete the “com.logi.ghub.plist” file
    9. Navigate to: /Library/LaunchDaemons
    10. Locate and delete the “com.logi.ghub.updater.plist” file
  3. System Restart
    1. Save any open work
    2. Restart your computer
  4. Fresh Installation
    1. Download the latest G HUB installer from the official link
    2. Run the installer
    3. Follow the installation prompts
    4. Launch G HUB and verify functionality

If issues persist

Contact Support: If all options fail, contact Logitech support with:

  • Your specific error messages
  • MacOS version information
  • Steps you’ve already attempted

Prevention Tips

  • Regular Updates: Keep G HUB updated through the built-in updater
  • Clean Updates: Never exit or force exit G HUB while an update is in progress
  • Clean Shutdowns: Always quit G HUB properly before system shutdown

Git: Rename local and remote branches

# Source - https://stackoverflow.com/a/30590238
# Posted by CodeWizard, modified by community.
# See post 'Timeline' for change history
# Retrieved 2026-01-29, License - CC BY-SA 4.0

# Names of things - allows you to copy/paste commands
old_name=feature/old
new_name=feature/new
remote=origin

# Rename the local branch to the new name
git branch -m $old_name $new_name

# Delete the old branch on remote
git push $remote --delete $old_name

# Or shorter way to delete remote branch [:]
git push $remote :$old_name

# Prevent git from using the old name when pushing in the next step.
# Otherwise, git will use the old upstream name instead of $new_name.
# Ethan's edit: I'm wondering if `$new_name` should be `$old_name`; at least it
# makes more sense to me.
git branch --unset-upstream $new_name

# Push the new branch to remote
git push $remote $new_name

# Reset the upstream branch for the new_name local branch
git push $remote -u $new_name

Git: How do I update or sync a forked repository on GitHub?

# Source - https://stackoverflow.com/a
# Posted by Mark Longair, modified by community.
# See post 'Timeline' for change history
# Retrieved 2026-01-29, License - CC BY-SA 4.0

In your local clone of your forked repository, you can add the original GitHub repository as a “remote”. (“Remotes” are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

# Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

# Fetch all the branches of that remote into remote-tracking branches

git fetch upstream

# Make sure that you're on your main branch:

git checkout main

# Rewrite your main branch so that any commits of yours that
# aren't already in upstream/main are replayed on top of that
# other branch:

git rebase upstream/main

If you don’t want to rewrite the history of your main branch, (for example because other people may have cloned it) then you should replace the last command with git merge upstream/main. However, for making further pull requests that are as clean as possible, it’s probably better to rebase.

If you’ve rebased your branch onto upstream/main you may need to force the push in order to push it to your own forked repository on GitHub. You’d do that with:

git push -f origin main

You only need to use the -f the first time after you’ve rebased.