Ctrl+shift+0 in windows 10

I play a video game in which Ctrl+Shift+0 is mapped to a specific action.

In prior versions of Windows, I was able to receive Ctrl+Shift+0 keypresses in-game by getting rid of the Windows keyboard shortcut for switching input languages.

In Windows 10, that is no longer sufficient.  My game can't receive Ctrl+Shift+0 keypresses at all, even with the keyboard shortcut for input-language switching set to None.

Is there a way to get Ctrl+Shift+0 to work again in Windows 10?

 

Question Info


Last updated August 18, 2019 Views 466 Applies to:

Hi Roger,

Thank you for posting your query in Microsoft Community.

I understand that the keyboard shortcut Ctrl+shift+0 fails to work while playing a video game in Windows 10. I will certainly help you.

In order to assist you better, please reply to the following questions.

1. May I know the name of the game?
2. Is the game compatible on Windows 10?

 

I suggest you to check keyboard settings of the game and see whether Ctrl+Shift+0 is assigned for appropriate action.

Please post back with above information and we will be glad to assist you further.

Thank you.


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

The game is World of Warcraft.  Ctrl+Shift+0 was bound to a specific action back when I was running under Windows 7.  When I upgraded to Windows 10, it stopped working, but the game's key-binding menu showed that Ctrl+Shift+0 was still bound to the action.

I tried adding Ctrl+Shift+0 as an action for something else, and this is where it gets interesting.  You add a key mapping by clicking on one of the items in the Key Bindings screen, and then pressing the key combination you want to use.  The game doesn't even think any keys are being pressed when I try to do this!  In other words, Ctrl+Shift+0 is being intercepted at the O/S level before the game even sees it.

Note: By Ctrl+Shift+0, I mean holding down Ctrl and Shift, and pressing the 0 key on the main keyboard, not the 0 key on the numeric keypad.  In other words, it's the 0 key with the ) printed above the 0.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hey Roger,

Late reply, but I am seeing this issue too.  I've done a bit of digging around and it appears that the KeyDown event is not getting through in some cases for Ctrl+Shift+0, but the KeyUp event is.  WOW must be listening for the KeyDown events when doing the binding which is likely causing the error that you're seeing.

Interestingly enough, if you use AutoHotkey (which has a keyboard event spy), you can see that it is properly receiving all of the KeyDown events (repeated if you hold down 0), so they must be receiving events differently from how WOW is.

FWIW, my scenario is using the C# Console.ReadKey API, which internally calls the Kernel32.dll ReadConsoleInput API.  I'm going to try and see if I can determine how autohotkey listens for events, but it's possible it's just using the normal windows event pump.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.