Keyboard shortcuts not working in Windows 11 — Win+D doesn’t show the desktop, Alt+Tab does nothing, Print Screen stops working, or game-specific shortcuts break unexpectedly — has a specific set of causes depending on which shortcuts are affected. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Before investigating Windows settings: confirm the keyboard hardware itself is fine. Open Notepad and type some regular text — if letters and numbers work but shortcuts don’t: software is the issue. If regular typing also has problems: start with the keyboard hardware guide first.
Which shortcuts stopped working?
The fix depends on which category of shortcuts is broken:
- Windows key shortcuts (Win+D, Win+E, Win+Tab, etc.): Windows key may be locked, or Windows shell crashed
- Function key shortcuts (F1-F12, brightness, volume, media): Fn lock active, or keyboard software remapped them
- Application-specific shortcuts (Ctrl+Z, Ctrl+C in a specific app): another application is intercepting the shortcut
- All shortcuts suddenly stopped: Shell crash, Filter Keys enabled, or Sticky Keys interference
Fix 1: Windows key disabled by gaming software or lock
Many gaming keyboards have a “Windows key lock” button that disables the Windows key to prevent accidental Start menu openings mid-game. If Win+anything does nothing: look for a Windows lock indicator on the keyboard (often a key with a padlock + Windows logo), or check the keyboard’s software (Logitech G Hub, Razer Synapse, Corsair iCUE) for a Windows key lock setting. Toggle it off.
Gaming mode in Windows 11 also disables the Windows key: Settings → Gaming → Game Mode — if enabled: Win+G shortcuts still work but Win+D, Win+E, etc., may behave differently.
Fix 2: Filter Keys and accessibility features
Filter Keys (an accessibility feature that ignores brief or repeated keystrokes) can make shortcuts feel like they’re not working — especially shortcuts that require holding two keys simultaneously. Settings → Accessibility → Keyboard → Filter Keys → Off. Also check Sticky Keys (Off) and Toggle Keys (Off) in the same section.
Filter Keys activates accidentally by holding the right Shift key for 8 seconds — a mistake that’s easy to make when trying to select text and being frustrated with a selection problem. The symptom: keyboard feels slow or unresponsive, shortcuts require holding keys longer than usual.
Fix 3: Restart Windows Explorer
Many Windows key shortcuts (Win+D, Win+Tab, Win+E, Win+Ctrl+Arrow for desktops) are handled by Windows Explorer’s shell. When Explorer gets into a bad state: these shortcuts stop working even though the keyboard is fine. Ctrl+Shift+Esc → Task Manager → right-click “Windows Explorer” → Restart. After the shell restarts (2 seconds): test the shortcuts. This is the most common fix for a batch of Windows key shortcuts that all stopped working simultaneously.
Fix 4: Application intercepting shortcuts
Some applications register global hotkeys that intercept keyboard shortcuts system-wide. A game running in the background, a productivity tool with global shortcuts, or a screen recording application can capture Ctrl+Shift+S, PrtScn, or other combinations before Windows sees them.
Test: close or minimise all other applications → try the shortcuts. If they work with everything closed: reopen applications one at a time until the conflict reappears. The application causing the conflict is often not the one you’re actively using — background applications like Discord, OBS, or screen capture tools are common culprits.
Fix 5: Fn lock for function keys
Laptop keyboards have Fn lock — a toggle that switches F1-F12 between their secondary function (brightness, volume, media) and the standard F-key functions. If F keys suddenly started controlling hardware instead of acting as F1-F12 (or vice versa): Fn lock was toggled. The key combination to toggle it varies: Fn+Esc, Fn+F1, or a dedicated lock key depending on the laptop model. The laptop manual or manufacturer’s support page specifies the exact combination.
Fix 6: Print Screen specifically
Print Screen (PrtScn) has multiple variations in Windows 11:
- PrtScn alone: copies screenshot to clipboard (no visible feedback)
- Win+PrtScn: saves screenshot to PicturesScreenshots folder and briefly dims the screen
- Win+Shift+S: opens Snipping Tool overlay
- Alt+PrtScn: captures active window only
If Win+Shift+S opens Snipping Tool instead of PrtScn saving to a file: Settings → System → Clipboard → check “Print Screen shortcut” setting. This controls what the standalone PrtScn key does. Some keyboard software also remaps PrtScn to “screenshot to file” or “open screenshot tool” — check the keyboard’s software for any PrtScn remapping.
Fix 7: Third-party keyboard software remapping
Applications like AutoHotkey, SharpKeys, PowerToys Keyboard Manager, or keyboard manufacturer software can remap keys system-wide. If a shortcut stopped working or does something unexpected: check whether any remapping software is active and has a rule affecting those keys. PowerToys → Keyboard Manager → Remap Keys / Remap Shortcuts — shows all active remaps. Disabling or deleting the rule for the affected shortcut restores default behaviour.
Our guide on keyboard input troubleshooting covers the layout and language settings that affect key output more broadly. For the shell crash that disables Win+D and Task View shortcuts, our virtual desktop guide covers the Explorer restart in the context of multitasking features. Microsoft’s keyboard shortcut reference is the definitive list of all Windows 11 shortcuts, which is useful for confirming whether a shortcut has changed in a recent Windows update versus not working at all.
Group Policy restrictions on shortcuts
In enterprise environments: Group Policy can disable specific keyboard shortcuts. Common restrictions include disabling Win+L (lock screen) for kiosk setups, or disabling hotkeys that access system tools (Win+R for Run, Win+E for Explorer) on restricted machines. If shortcuts are unavailable on a managed machine that they work on personally: check with IT or verify through gpedit.msc → User Configuration → Administrative Templates → Windows Components → various policy areas that reference “hotkeys” or “keyboard shortcuts.”
Registry check for hotkey restrictions
Certain applications and group policies write hotkey restrictions directly to the registry. Win+R → regedit → navigate to:
HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer
Look for “NoWinKeys” value — if set to 1: all Windows key shortcuts are disabled. Delete or set to 0. Also check: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorer for the same value. Setting “NoWinKeys” to 0 in both locations restores Windows key shortcuts that are disabled through registry policies rather than Group Policy.
HID keyboard driver
USB and Bluetooth keyboards use the Windows HID (Human Interface Device) driver. When this driver has issues: modifier keys (Ctrl, Alt, Shift, Windows key) may fail to register correctly, causing all shortcuts that use modifiers to stop working. Device Manager → Keyboards → right-click the keyboard → Uninstall device → disconnect the keyboard → reconnect. Windows reinstalls the HID driver automatically. For Bluetooth keyboards: this may require unpairing and re-pairing as well.
Specific shortcut reference table
| Shortcut not working | Most likely cause | Quick fix |
| Win+D (show desktop) | Explorer shell crash or Win key locked | Restart Explorer; check gaming keyboard Win lock |
| Alt+Tab | Explorer crash or third-party app intercepting | Restart Explorer; close background apps |
| Win+Tab (Task View) | Task View component crashed | Restart Explorer |
| Ctrl+Shift+Esc (Task Manager) | Task Manager policy disabled or intercepted | Check Group Policy; close conflicting apps |
| PrtScn (screenshot) | Setting changed, app intercepting | Check Print Screen setting in System settings |
| F1-F12 doing hardware functions | Fn lock active | Toggle Fn lock (Fn+Esc or manufacturer key) |
| All shortcuts suddenly broken | Filter Keys or Sticky Keys activated | Settings → Accessibility → Keyboard → disable both |
Keyboard shortcut combinations new to Windows 11
Windows 11 introduced new shortcuts that didn’t exist in Windows 10. Some users encounter shortcuts they know from Windows 10 no longer working because Windows 11 changed the action:
- Win+A now opens Quick Settings (used to open Action Center)
- Win+N opens Notification Center (separate from Action Center in Windows 11)
- Win+Z opens Snap Layouts (new in Windows 11)
- Win+W opens Widgets (new in Windows 11)
If a “familiar” shortcut does something unexpected: it may have been changed in Windows 11 rather than being broken. Microsoft’s current keyboard shortcut reference confirms the current behaviour for each combination.
Keyboard shortcut conflicts with applications
Certain applications are known to globally intercept specific shortcuts:
- Discord: frequently uses Ctrl+Alt+combinations and can intercept Win+Shift+S
- OBS Studio: hotkeys set in OBS apply globally when OBS is running
- Virtual machines (VMware, VirtualBox, Hyper-V): when a VM window has focus, keyboard shortcuts go to the VM, not Windows
- Remote Desktop: keyboard shortcuts in an RDP session apply to the remote machine unless explicitly configured otherwise
For applications with their own shortcut systems: configure the application to avoid conflicts with Windows shortcuts you use frequently. Discord’s keybind settings and OBS’s hotkey settings both allow changing the assigned combinations.
Testing shortcuts systematically
If unsure which shortcuts work and which don’t: test systematically. Open a text editor → try Win+D (should show desktop) → Win+Tab (should show Task View) → Alt+Tab (should switch windows) → Ctrl+Z (undo in the text editor). This quick sequence tests three different shortcut categories: Win key shortcuts (shell), Alt key shortcuts (system), and application shortcuts (Ctrl). Knowing exactly which category is broken directs the investigation correctly.
Keyboard remapping with PowerToys
Microsoft’s free PowerToys application (downloadable from GitHub or Microsoft Store) includes a Keyboard Manager that allows remapping individual keys and key combinations system-wide. If a shortcut does nothing: check whether PowerToys has that combination remapped to “None” or another action. PowerToys → Keyboard Manager → “Remap a shortcut” → look for the shortcut in the list.
PowerToys is also useful for creating custom shortcuts: remapping an unused key combination to a frequently-needed action (like a specific application launch). But if PowerToys is installed and shortcuts are misbehaving: its Keyboard Manager is the first place to check before investigating Windows settings.
The most effective approach for “all shortcuts suddenly stopped working” is sequential: Filter Keys off → Explorer restart → Win key lock check → application conflict test. These four steps cover the majority of sudden-onset shortcut failures in under 5 minutes. The registry and Group Policy investigation applies to the minority of cases — usually on managed machines or after installing specific software — where those quick fixes don’t resolve it.
A useful habit for anyone who works extensively with keyboard shortcuts: keeping a shortcut reference open in a browser tab for the current session. When a shortcut stops working unexpectedly: checking whether it was recently changed in a Windows update (by looking at the current official list) immediately distinguishes “shortcut broken” from “shortcut reassigned.” Microsoft updates keyboard shortcuts with Windows feature releases, and occasionally a shortcut you’ve relied on for years gets a new function or gets reassigned.
Input Method Editors and shortcuts
IMEs (Input Method Editors) for languages like Chinese, Japanese, and Korean intercept certain key combinations for character input. When an IME is active: Ctrl+Space (switch input mode), Ctrl+Shift combinations, and occasionally Shift+Space are captured by the IME before Windows sees them. If shortcuts involving these modifiers stopped working after adding a language: the IME for that language may be intercepting them.
Settings → Time and language → Language and region → your language → Options → Keyboard → check the installed input methods and their keyboard shortcuts. Each IME has its own shortcut settings that can be changed to avoid conflicts. If you don’t need the IME: removing the keyboard input method for that language (while keeping the language display) prevents the IME from intercepting shortcuts.
Keyboard shortcuts in elevated processes
Windows applies different trust levels to keyboard input for processes running at different privilege levels. Shortcuts registered by a standard user process can’t capture input directed to an elevated (administrator-level) process. This explains why some shortcuts work in most applications but fail when a UAC (User Account Control) dialog is active or when focus is on an elevated application — the shortcut handlers don’t have permission to intercept input at the elevated level.
For shortcuts that need to work across privilege levels (like global media controls while using an admin application): the shortcut application itself needs to run at the same or higher privilege level. Running the keyboard shortcut manager as administrator (or using Windows’ built-in shortcuts which operate at kernel level) bypasses this restriction.
For laptop users specifically: it’s worth knowing that some laptop models ship with Fn lock enabled by default (especially business laptops where F keys are used more in business applications than for media). If you just got a new laptop and the media/brightness keys are acting as F1-F12 without pressing Fn: the Fn lock default matches business use. Check the laptop’s quick start guide for the Fn lock toggle combination specific to that model — it’s usually documented prominently because it’s a common point of confusion on first setup.
In summary: keyboard shortcut failures in Windows 11 are almost always caused by one of five things — accessibility features (Filter Keys/Sticky Keys), the Windows key being locked, the Explorer shell being in a bad state, a third-party application intercepting the shortcut, or a remapping tool changing the key assignment. Checking these in order, starting with the accessibility features and Explorer restart, resolves the issue for the vast majority of users without needing to dig into registry values or Group Policy settings. See also Windows 11 Volume Not Working for a related case.
