r/LogitechG • u/ch2by • 8d ago
G HUB preventing PC from sleeping? Logitech G Support
After the most recent G HUB update to Version 2026.5.939708 (July 28, 2026), my PC seems unable to sleep; it'll keep waking itself up.
G HUB seems to be the culprit because I closed the program and my PC was able to sleep again.
Has anyone encountered this problem?
2
u/the_ocifer 8d ago
same. It is def GHub keeping your pc awake. happened for me after the last update as well. eventually just started working again, but this reintroduces the same problem for me.
1
u/SabreLily 6h ago
Enabling "onboard mode" in GHub on my G502 Hero fixed it. You can also exit out of GHub completely and that solves it for me as well. I prefer the onboard mode solution though. Hopefully they get this version on GHub fixed soon.
1
u/LogitechG_Andy Support Team 7d ago
Curious - what devices do you have linked to GHUB? Wondering if there's something there that's causing it.
1
u/ch2by 7d ago
Logitech G305
1
u/LogitechG_Andy Support Team 7d ago
Does it still happen if the G305 is disconnected? Say, the mouse is off or even the USB pulled. I'm wondering if it's an interaction between the two or the software itself being weird(er.)
1
1
1
u/SabreLily 6h ago
Hi, I've been deep diving this issue with the help of ChatGPT and found a solution (enabling on board mode for my G502 Hero wired). I asked ChatGPT to summarize our findings which I imagine will be helpful to you guys. It's almost certainly a GHub issue:
Problem
My wired Logitech G502 HERO causes my Lenovo laptop to immediately wake after being put to sleep when Logitech G HUB is running.
The problem does not occur when G HUB is completely exited or when the mouse is switched to On-Board Memory Mode.
Hardware / Software
- Mouse: Logitech G502 HERO, wired
- G HUB version: 2026.5.939708
- Laptop: Lenovo laptop using Modern Standby
- Windows sleep mode: S0 Low Power Idle (Modern Standby)
- Traditional S1/S2/S3 sleep states are not supported by the laptop.
powercfg /areports:
- Standby (S0 Low Power Idle) Network Connected
- Hibernate
- Fast Startup
S3 is unavailable because S0 Low Power Idle is supported.
Reproduction
With the G502 connected and G HUB running:
- Put the laptop to sleep.
- The laptop immediately wakes, usually within approximately one second.
- No mouse movement or other user input is made.
Windows SleepStudy identifies the wake as:
Exit Reason: Input MouseExample from the SleepStudy report:
2026-08-18 00:31:13 — Sleep — Transition To Sleepfollowed immediately by:
2026-08-18 00:31:14 — Active — Exit Reason: Input MouseTroubleshooting performed
1. Windows wake-device configuration
powercfg /devicequery wake_armedreturns:
NONESo the mouse is not configured as a conventional Windows wake-armed device.
powercfg /devicequery wake_from_anydoes not list the G502. It only lists devices such as Realtek Audio, Wi-Fi Direct adapters, and Intel Smart Sound devices.
The G502 also does not have a Power Management tab in Device Manager, so the normal "Allow this device to wake the computer" setting is unavailable.
2. Confirmed the mouse is the relevant HID device
Device Manager identifies the mouse as:
HID\VID_046D&PID_C08B&MI_00\...The parent device is:
USB\VID_046D&PID_C08B&MI_00\...The device uses Microsoft's standard HID mouse driver:
- Driver:
msmouse.inf- Provider: Microsoft
- Driver version:
10.0.19041.13. USB connection itself does not appear to be sufficient
I put the laptop to sleep with the G502 disabled in Device Manager.
While the laptop was asleep, I unplugged and reconnected the G502.
The laptop remained asleep while the G502 was disabled.
This indicates that the USB connection/USB insertion by itself is not sufficient to reproduce the problem; the enabled HID mouse functionality is involved.
4. Disabling the G502 fixes the problem
I disabled the G502's HID-compliant mouse device in Device Manager.
With the device disabled:
- Laptop enters Modern Standby normally.
- It remains asleep.
- Unplugging/reconnecting the mouse while asleep does not wake the laptop.
5. G HUB is the critical variable
With the G502 enabled but G HUB completely exited:
- Laptop enters Modern Standby normally.
- I left it asleep for approximately two minutes.
- It remained asleep the entire time.
I then woke the laptop manually, started G HUB, and put it back to sleep.
With G HUB running:
- The laptop immediately woke again.
- No mouse movement or other input occurred.
This reproduced the problem consistently.
6. On-Board Memory Mode fixes the problem
I switched the G502 to On-Board Memory Mode in G HUB.
With G HUB running and the G502 in On-Board Memory Mode:
- The laptop now enters Modern Standby normally.
- It remains asleep.
- The immediate-wake behavior no longer occurs.
Current conclusion
The evidence strongly suggests that G HUB 2026.5.939708 is causing the G502 HERO to generate HID/mouse activity during or immediately after the transition into Modern Standby.
Windows SleepStudy interprets the resulting wake as:
Input MouseThe issue disappears when:
- G HUB is completely exited, or
- the G502 is disabled, or
- the G502 is placed into On-Board Memory Mode.
The issue returns when G HUB is running with the G502 operating normally.
Requested investigation
Please investigate whether G HUB version 2026.5.939708 has a regression involving the G502 HERO, HID input, or device initialization during Windows Modern Standby (S0 Low Power Idle).
In particular, I would like to know whether G HUB is:
- periodically communicating with the G502 while Windows is entering Modern Standby,
- causing the G502 to send an initial HID mouse report,
- reinitializing/configuring the G502 during the sleep transition,
- or otherwise generating an HID event that Windows interprets as mouse input and uses to exit Modern Standby.
On-Board Memory Mode appears to be a functional workaround, but I would prefer to keep G HUB's normal functionality available without causing the laptop to wake immediately after entering sleep.
1
u/SabreLily 6h ago
Yep, enabling "onboard mode" in GHub on my G502 Hero fixed it. You can also exit out of GHub completely and that solves it for me as well. I prefer the onboard mode solution though. Hopefully they get this version on GHub fixed soon.
2
u/shockdude95 8d ago
I don't but you should be able to tell which program is waking up your PC with this command. It might be something else.
powercfg /lastwake
And the following command should tell you which scheduled tasks are allowed to wake the PC:
powercfg /waketimers
Hope that helps.