Mouse Jump Activation Issue

[sunilkumarba]

Microsoft PowerToys version

0.71.0

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

Mouse Utilities

Steps to reproduce

1. Press Mouse Jump activation shortcut

My setup is:

• I've dual monitor setup (Laptop screen and an external monitor) in Extend mode.
• I've set the Mouse Jump activation shortcut to Win+Q. Same issue if I use the default key combination (Win+Shift+D).

✔️ Expected Behavior

On pressing the Mouse Jump activation shortcut, UI should be displayed immediately.

❌ Actual Behavior

On pressing the Mouse Jump activation shortcut, nothing happens.

I've to press the activation shortcut few more times, then UI is displayed. There is lot of delay.

This happens when activating for the first time after boot or activating after long gap between activations.

Other Software

No response

[amiranjom]

I closed a ticket I opened on July 14th, 2024 as it relates to this. After some trial and error, I was able to resolve this problem by updating my PowerToys to version v0.81.1. I thought I was running the PowerToys as an admin, but in the general tab of the PowerToys the button "Restart PowerToys as administrator" was clickable which gave me the hint that its not running as an admin. After updating and running it as an Admin the issue was resolved for me

[mikeclayton]

@sunilkumarba - Apologies for the delayed response - to help narrow down the cause, could you look in the "PowerToys Runner" log file and see if it's detecting the activation keypress?

On my machine the logs are in C:\Users\<username>\AppData\Local\Microsoft\PowerToys\RunnerLogs\runner-log_yyyy-mm-dd.txt and every time I press the Mouse Jump activation keys I see an entry like this logged:

[2024-07-17 20:53:33.224263] [p-12708] [t-12712] [trace] MouseJump hotkey is invoked from Centralized keyboard hook

If that is being logged with the appropriate timestamp for when you pressed the combination it means something might be wrong in the Mouse Jump utility.

If it isn't being logged it means the problem might be something happening in the PowerToys Runner, which is what handles the activation keys for all the PowerToys utilities...