Pinpointing which release elements have changed KeyboardHook sufficiently I haven't discovered. There were two updates this week, other than a Defender update.
I've tried the obvious things, shutdown and restart, restarting the app, unhooking the keyboard in settings and reapplying.
The DesktopView is also very slow to come up if chosen from the shortcuts menu. The code is still running and monitoring which is the active desktop, the icon changes as you cycle through the desktops with Ctrl-Win-LftArrow.
After a number of reinstalls the KeyboardHook installation stuck and works, the DesktopView, which I hardly ever use still seems slow to come up and slow to return to a desktop. Closing this.
Pinpointing which release elements have changed KeyboardHook sufficiently I haven't discovered. There were two updates this week, other than a Defender update.
An update to .NET 3.1 Core https://github.com/dotnet/core/blob/main/release-notes/3.1/3.1.16/3.1.16.md (I had a couple of .NET exceptions 1 in Evernote, 1 that could have been keyboard related but I didn't capture it).
The cumulative update for Windows 10 21H1 https://support.microsoft.com/en-us/topic/june-8-2021-kb5003637-os-builds-19041-1052-19042-1052-and-19043-1052-fd782405-7736-478e-b8d0-b08f735f7e54
I've tried the obvious things, shutdown and restart, restarting the app, unhooking the keyboard in settings and reapplying. The DesktopView is also very slow to come up if chosen from the shortcuts menu. The code is still running and monitoring which is the active desktop, the icon changes as you cycle through the desktops with Ctrl-Win-LftArrow.