Share via

Windows 11 Windows logo key + number keyboard shortcut issues, causes blank black/gray pop up

Anonymous
2023-06-28T18:35:45+00:00

I am a developer and keep a list of common applications pinned to my taskbar so that I can use the WinKey+number keyboard shortcut to switch between apps quickly when working (Win+1=Chrome, Win+3=Outlook, Win+4=SQL Server, Win+5=Visual Studio, etc.). I have been using these shortcuts for years, but since our company upgraded to Windows 11 these keyboard shortcuts often have issues. When an app has multiple windows open where if you press the Win+1 (or other number) keyboard shortcut quickly then it pops up a blank gray/black box instead of displaying the app windows and will not allow you to switch to the app using the shortcut. The gray box won't go away if you repeat the keyboard shortcut for the same app (Win+3, get the gray box, press Win+3 again), but it will go away if you click on the taskbar with your mouse, or if you switch to another app via the keyboard shortcut and then back to the original app pressing the keyboard shortcut very slowly.

Repro: this only happens when:

  1. you have multiple windows open for an app. For example: if I have Outlook plus a meeting reminder or email open, or if I have Chrome and Chrome Incognito windows open, or multiple Visual Studio solutions open.
  2. and you press the Win+number keyboard shortcut quickly. If you hold the Windows key down for longer and keep it help down for a bit after you press the number then it works, but that is a very difficult muscle memory to retrain if you are used to using quick keyboard shortcuts.

What is the best avenue to report this to Microsoft?

Currently using a new laptop with Windows 11 Enterprise 22H2, HP zBook Fury 16 G9 with latest drivers, 12th Gen Intel(R) Core(TM) i7-12800HX 2.00 GHz (12 physical cores / 24 hyperthreaded), 32GB RAM, so it shouldn't be a hardware resource issue.

I've seen this same issue mentioned in other places online, and I've reproduced the issue on several other fresh Windows 11 installations on different PC models.

Related issues reported other places:

https://answers.microsoft.com/en-us/windows/forum/all/windows-11-ui-lag-breaks-basic-keyboard-shortcut/840e256e-1330-4dc6-8c93-e4e9c636e432 https://superuser.com/questions/1770585/windows-11-broke-win0-win1-etc-style-shortcuts

Screenshot of the gray box:

Windows for home | Windows 11 | Input and language

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

25 answers

Sort by: Most helpful
  1. Anonymous
    2024-01-12T20:33:23+00:00

    Here is a dead simple AutoHotKey script to fix the problem. The trick in preventing this issue is to always release the number key before releasing the windows key. This script handles that case, and emulates pressing them in the right order.

    ; Register Win + 0-9 with our custom handler to add key delay.
    
    LWin & 1::WinNumber(1)
    
    LWin & 2::WinNumber(2)
    
    LWin & 3::WinNumber(3)
    
    LWin & 4::WinNumber(4)
    
    LWin & 5::WinNumber(5)
    
    LWin & 6::WinNumber(6)
    
    LWin & 7::WinNumber(7)
    
    LWin & 8::WinNumber(8)
    
    LWin & 9::WinNumber(9)
    
    LWin & 0::WinNumber(0)
    
    ; Custom handler
    
    WinNumber(numberKey) {
    
        ; Wait until the user has released the number key. This allows us to emulate
    
        ; standard windows behavior of "cycling" through the multiple open windows
    
        ; in taskbar position of the number key.
    
        KeyWait, %numberKey%
    
        ; If the Win key is still pressed, windows will not bug out and create
    
        ; the grey box window. Just press the number key here to select the window
    
        ; from the taskbar.
    
        if GetKeyState("LWin", "P")
    
            Send, {Blind}%numberKey%
    
        ; If the user has already released the windows key before releasing the
    
        ; number key, press the windows key back down along with the number key.
    
        else
    
        {
    
            ; Manually press down on the Win key without releasing, then press the
    
            ; number key. 
    
            Send, {Blind}{LWin down}%numberKey%
    
            ; Wait 1/10th of a second before releasing the windows key.
    
            ; This is what prevents the bugged window from popping up. Without a
    
            ; delay, the bugged window occurs. I tested a delay of 50 ms instead
    
            ; of 100 here, but the bug still ocurred. 100 is reliable.
    
            Sleep, 100
    
            Send, {Blind}{LWin up}
    
        }
    
        return
    
    }
    
    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-10-12T21:49:53+00:00

    This registry tweak only works if "Combine taskbar buttons and hide labels" is set to "Never". With labels showing, the LastActiveClick does not immediately toggle between open windows when using the Win+# keyboard shortcut, the window thumbnails/previews are still shown. This is still a very easily reproduceable bug, ever since Windows 10.

    The key to reproducing this issue is pressing the shortcut quickly / fast.

    10 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-10-05T13:32:08+00:00

    Oddly, SanderJoon'srecommendation of enabling always use LastActiveClick via the registry does seem to resolve this for me.

    1. In Registry Editor, in HKEY_CURRENT_USER > Software > Microsoft > Windows > CurrentVersion > Explorer create a new Registry entry by right-clicking Advanced within the Explorer key and selecting New > DWORD (32-bit) Value.
    2. A new entry will appear on the right side. Name it LastActiveClick.
    3. Double-click this entry you just added and change Value data from 0 to 1.
    4. Reboot the computer.

    I've only been using it for a couple of hours after enabling and it seems like it has resolved it for me. Based on the description of what LastActiveClick does I did not suspect it would have any impact. However, I noticed enabling LastActiveClick via holding down the Ctrl key when using Winkey-# did not seem to exhibit the same symptoms, so I tried it, and so far so good.

    Sometimes the content of the thumbnail is blank, but to me that's irrelevant. I can at least switch windows and applications.

    Here's an example of how they're different after enabling LastActiveClick

    9 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-09-05T10:36:41+00:00

    I have been experiencing the exact same issue. My specs are also very decent (5600X, 16GB of Ram, 6800XT) so it might not even related to Intel or AMD. This costs me tons of time and annoys me to the extent that I was considering switch back to Windows 10.

    8 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-01-12T07:50:01+00:00

    Simple patch for this bug.

    https://github.com/wuutae/fix-win-num-popup/releases/tag/v1.0

    Hope this helps.

    6 people found this answer helpful.
    0 comments No comments