Keychron K2 Windows Key Not Working: The Two Switches Most People Never Check
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard TesterYour Keychron K2 Windows key is blocked by a physical toggle switch on the side of the board and a secondary lock combination that overrides it in firmware โ fix those two things and the key works immediately. The K2 ships with a hardware mode switch that reassigns the bottom-row modifier layout between macOS and Windows, and a separate Win/Mac lock function tied to Fn+X+L that disables the Windows key entirely when active. Neither of these is a driver issue, a Windows registry problem, or a defective switch under the keycap.
The Side Switch: What It Actually Controls
On the left side of the Keychron K2 (and the K2 HE hot-swap variant), there is a three-position slider switch labeled Windows/Android and Mac/iOS. This is a physical DPDT-style signal switch routed directly to the onboard microcontroller โ on the K2 HE it feeds into the hall-sensor polling logic on the main PCB. When this slider sits in the Mac/iOS position, the firmware remaps the Alt key to Command and the Windows key to Option. The Windows key keycap is still physically present and its Gateron, Keychron-branded Gateron, or hall-effect sensor (on the K2 HE) still registers a signal, but that signal is sent to the host as the macOS Option keycode rather than the Windows Super keycode.
Slide the switch fully toward the Windows/Android label. You will feel a distinct detent. Do not leave it in the middle position โ the microcontroller reads that as an undefined state and behavior becomes inconsistent across Bluetooth and USB modes.
After moving the switch, unplug and replug the USB-C cable, or toggle Bluetooth off and back on. The K2's onboard controller does not re-read the switch state mid-session on all firmware versions. Confirm the key is working using the Keyboard Test tool โ press the Windows key and verify the correct keycode appears in the output field.
The Firmware Lock: Fn+X+L
Keychron added a Windows key lock combination starting with K2 firmware revision 0.1.5 and it carries through to the current K2 HE firmware. Pressing Fn+X+L simultaneously toggles a flag in the keyboard's onboard EEPROM that suppresses the Windows key output regardless of the side switch position. The top-right indicator LED blinks three times when you activate it and three times when you deactivate it โ if you hit that combination accidentally, you will not notice anything visually permanent on the board.
To clear it: hold Fn, then press X and L at the same time. Release all three. The LED blinks three times. Test immediately with the Keyboard Test. If the Windows key now registers, the lock was the culprit. This is the most common cause for users who report the keychron k2 windows key not working after the keyboard has been working fine for weeks โ someone hit that combination during a game or a shortcut sequence.
Side Switch vs. Firmware Lock: How to Tell Them Apart
The symptom is the same โ Windows key produces no output or the wrong keycode โ but the cause is different. Use this table to narrow it down before touching anything.
| Symptom | Side Switch (Mac mode) | Fn+X+L Lock Active |
|---|---|---|
| Windows key sends no keycode at all | No | Yes |
| Windows key sends Option/Alt keycode instead | Yes | No |
| Left Alt key also behaves unexpectedly | Yes โ sends Command | No โ Alt works normally |
| Affects Bluetooth and USB equally | Yes | Yes |
| Persists after cable unplug/replug | Yes | Yes โ stored in EEPROM |
| Cleared by firmware flash | No โ hardware switch | Yes โ resets EEPROM flags |
If you are on the K2 HE specifically and the Windows key registers intermittently rather than not at all, the hall-effect sensor under that position is not the problem โ hall sensors do not degrade the way mechanical switches do. Intermittent output on the K2 HE points to a loose USB-C connection or a Bluetooth interference issue, not a hardware fault at the key itself.
Full Reset Procedure If Both Fixes Fail
If you have confirmed the side switch is in Windows/Android mode and you have toggled Fn+X+L to clear the lock and the keychron k2 he windows key not working issue persists, do a full factory reset before assuming PCB failure.
- Unplug the USB-C cable.
- Move the side switch to Mac/iOS, wait five seconds, then move it back to Windows/Android.
- Hold Fn+J+Z simultaneously for five seconds while plugged in via USB-C. The top-right LED flashes rapidly, then goes solid. This resets all EEPROM-stored key remaps and lock states.
- On the Keychron firmware download page, download the correct .bin for your K2 revision (v1 and v2 have different PCBs and different firmware files โ check the sticker on the bottom of the board). Flash using QMK Toolbox with the Auto-Flash checkbox enabled. Set MCU to atmega32u4 for non-HE models.
- After flashing, re-test every modifier key with the Keyboard Test before reassembling anything.
If you also want to verify that other keys around the Windows key are not affected, the Mac Keyboard Test is useful for checking the Alt/Option cluster behavior side by side when switching the board between modes.
Frequently Asked Questions
Why does my Keychron K2 Windows key work on USB but not Bluetooth?
The side switch state is read at connection time. If you moved the switch while the Bluetooth connection was already active, the controller did not re-read it. Disconnect from Bluetooth on your PC (Settings > Bluetooth > your K2 > Remove device), then reconnect from scratch. The switch state will be read correctly on the new connection handshake.
My Windows key sends the wrong character, not just nothing. What is that?
That is the Mac/iOS mode active on the side switch. In that mode the Windows key position outputs the macOS Option keycode (0xE6 in HID usage tables). Windows interprets that as Right Alt in most cases, which is why you might see special characters triggered instead of the Start menu. Slide the switch to Windows/Android and reconnect.
Does the Fn+X+L lock affect the keychron k2 command key not working on Mac too?
Yes. The lock flag suppresses that physical key position entirely regardless of which mode the board is in. If you use the K2 on both a Mac and a PC and the Command key stops working on the Mac side, clear the lock with Fn+X+L and retest.
Will flashing new firmware delete my remapped keys?
Yes. A full firmware flash wipes the EEPROM, which stores any per-key remaps you set through QMK or VIA. Export your keymap JSON from VIA before flashing. The default keymap is restored and you will need to re-import your layout file afterward.
The Windows key physically feels different from other keys. Is the switch failing?
On standard K2 models with Gateron switches, the Windows key uses the same Gateron Red, Brown, or Blue switch as every other key โ there is nothing mechanically unique about that position. If the key feels mushy or scratchy compared to neighbors, the switch itself may need lubing or replacement, but that is a feel issue, not an output issue. A failing switch would produce no registration, not a wrong keycode. Confirm output behavior first with the Keyboard Test before pulling the keycap.
Does this apply to the Keychron K2 Pro?
The K2 Pro uses the same side switch logic and the same Fn+X+L lock combination. The Pro adds QMK/VIA support out of the box, which means a third possible cause: a custom layer in VIA may have the Windows key position mapped to a different keycode or set to transparent on Layer 1. Open VIA, select Layer 0, and confirm the Windows key position shows KC_LGUI. If it shows KC_NO or any other code, that is your problem and it is unrelated to the side switch.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard Tester