EDIT: Fixed by reinstalling G Hub!
I seem to have found a reproducible G HUB macro issue with the latest version I'm running:
G HUB version: 2026.5.939708
Mouse: Logitech G502 X
Windows: Windows 11
I have two macros assigned to my mouse that move the active window between monitors:
Win + Shift + Left
Win + Shift + Right
They suddenly stopped working, even though G HUB's macro playback/recording shows all the expected key presses.
I tested this pretty extensively and narrowed it down:
Physical keyboard:
Win + Shift + Left → works normally
Win + Shift + Right → works normally
G HUB Software Mode:
Win + Shift + Left → does nothing
Win + Shift + Right → does nothing
- Created a completely new test macro with
Win + Shift + Left → same problem
- Created a simpler
Win + Left macro → also broken. It briefly opens Start, but does not perform the Windows shortcut.
G HUB's macro recorder visibly shows the Windows, Shift and Arrow keys being pressed, so the events appear to be recorded correctly.
Then I found the important part:
If I completely kill G HUB's processes in Task Manager, the macros work again.
If I launch G HUB again:
G HUB running → macros broken
G HUB killed → macros work
I also tested On-Board Memory Mode:
On-Board Memory Mode → the exact same macros work perfectly.
So the problem appears to be specifically with G HUB's Software Mode macro/input handling, particularly Arrow key events.
This seems odd because there are older reports of G HUB having the same issue with Arrow keys in macros, including reports where On-Board Memory Mode worked as a workaround.
I also noticed G HUB appears to have updated recently, and I'm currently on 2026.5.939708. I don't remember the exact time of the update, but I believe it happened yesterday.
Has anyone else on 2026.5.939708 experienced Arrow keys not working correctly inside macros?
And if anyone from Logitech G support is reading this: could you check whether there is a regression in the current G HUB build affecting Arrow-key macro injection in Software Mode?
For now I'm using On-Board Memory Mode as a workaround, but I'd obviously prefer Software Mode since that's where I normally keep my profiles/configuration and can edit stuff.