Keyboard plugin and Win10 GameDVR

[noroom]

On Windows 10 (10586.11), the Keyboard plugin causes issues with the G key.

As long as the Keyboard plugin is in use, pressing G after using the Windows key will have the same effect as pressing Win+G, and it will trigger the game bar of the Game DVR feature in the Xbox app. The LL hook appears to be interfering with Windows, making it think that the Win key is being held down.

[Kev1000000]

Yep, I am also gettin this error with the latest update on Win10. Super annoying =(

[blackwind]

Confirmed, but the Keyboard plugin is, for all intents and purposes, abandoned, so don't expect a fix any time soon. Your best bet will probably be to disable the game bar.

[Kev1000000]

Disabling the game bar doesn't solve it for me, actually. Still happens.

For those who do run into the issue though, a quick press of Win+G resolves the issue temporarily.

[NibblyPig]

Is there an alternative plugin that can be used?

I had this issue and was forced to reinstall windows 8 because it interfered with too many things.

Any workaround would be appreciated.

[blackwind]

My plugin, Keyboard+, doesn't exhibit this issue (or any of the others Keyboard is notorious for), but it doesn't play well with the crazy old version of wxPython we still bundle and will, thus, crash EventGhost from time to time.

Until someone with the requisite know-how steps up and begins upgrading the bundled libraries to ones from this decade (which won't happen until someone with the requisite know-how steps up and finishes migrating us to GitHub), unfortunately, this is a no-win situation -- you can either use a great plugin that crashes through no fault of its own, or you can use an awful one that doesn't.

[syndac]

you can either use a great plugin that crashes through no fault of its own, or you can use an awful one that doesn't.

How often would you say it crashes? I'm having this problem as well and would love to remedy it.

[Silverhawk]

Also having this issue, thought my g-key was broken for a second till I figured out EventGhost was the culprit. Really don't wanna stop using the keyboard plugin or revert to windows 7 so hope a fix can be found.

[blackwind]

How often would you say it crashes?

If you follow the instructions in the thread and create macros to disable the plugin while EventGhost is focused, maybe once a day if you're unlucky? Otherwise, pretty much every time you open EventGhost.

[syndac]

If you follow the instructions in the thread and create macros to disable the plugin while EventGhost is focused, maybe once a day if you're unlucky? Otherwise, pretty much every time you open EventGhost

That seems to have helped quite a bit!

FYI, I didn't see the instructions in this thread, so here they are for anybody else:

Make sure you have the plugin, Task Create/Switch Events
Create a macro so that when Task.Created.EventGhost comes up, it disables the Keyboard plugin
Then, when Task.ClosedWindow.EventGhost comes up, enable the keyboard plugin

Note: I misunderstood blackwind's post and applied the "disable plugin" method to the stock Keyboard plugin, not Keyboard+. Will try with Keyboard+ as well

[Jhoni Mikn]

Yep, I am also gettin this error with the latest update on Win10. Super annoying =(

Kev I am also experiencing this issue any update

[_RIGHT_H]

i had the same problem with this windows update , running EG as administrator fixed it for me.

[luma]

i had the same problem with this windows update , running EG as administrator fixed it for me.

I was hopin this would work but as you miht ather from my post, it hasn't.

[luma]

I've come to the conclusion that there isn't a good, native EG solution. One kills my G key, the other crashes constantly. Neither is acceptable.

I'll be digging into AutoHotKey and start migrating keyboard-dependent automations off of EG as it doesn't look like a solution is on the horizon here.

[dreamcat4]

I'll be digging into AutoHotKey and start migrating keyboard-dependent automations off of EG as it doesn't look like a solution is on the horizon here.

Maybe AHK could just listen for all key events, and pass them to EG through another plugin (like network broadcast packet, COM signal etc). Then maybe we could make a modified version the Keyboard+ plugin to listen those AHK events and not to depend on certain other new library(ies) ?

For time being I've just gone with the Keyboard+, and disabled it when EG is active with the task macro... but finding it a bit difficult to understand the reasons nobody can have fixed Keyboard+ issues for such a long time (18 months?).

If the freezing issue is todo with library mismatch in host application, then why could not just statically dump those parts of the new lib's code which it's using directly into the Keyboard+ plugin itself (and rename those lib function not to conflict with host lib)? Then if EG ever gets newer lib upgraded, can revert back to original 'clean' version of the plugin.

Of course maybe these suggestions aren't feasible / appropriate. But perhaps someone else here knows more and can look into them a bit more? In particular the 2nd option.