Keychron Windows Key Not Working: How to Fix the OS Mode Switch and Remap in VIA

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Keyboards

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester

Your Keychron Windows key is not working because the physical OS toggle switch on the side or back of the board is set to Mac mode, which remaps the Super key to Command and disables standard Windows behavior at the firmware level. This is not a driver issue, a Windows update regression, or a USB problem. The switch physically instructs the onboard controller to load an alternate key matrix layer, so no amount of software intervention fixes it until the switch is moved. On boards running QMK-compatible firmware like the Keychron K2, K8, K6, and Q-series, a secondary cause is a VIA or QMK remap that has overwritten KC_LGUI on Layer 0.

Identify Which Switch or Layer Is Causing the Problem

Before opening VIA or touching any software, physically locate the mode switch. On the Keychron K2 and K8 the switch is a three-position slider on the left side of the board when viewed from above. The positions are labeled: Mac, Win/Android, and iOS (some early K2 Rev A units label it Mac and Win only). If the slider sits on Mac, the firmware substitutes KC_LGUI behavior with a Command-equivalent scancode that Windows does not interpret as the Win key. Slide it firmly to Win/Android. You will feel a small detent click.

On the Keychron Q1, Q2, Q3, and Q5, there is no physical switch. Those boards ship with pure QMK and you control everything through VIA or QMK Configurator. If you are on a Q-series and the Windows key is dead, skip directly to the VIA remap section below.

After moving the switch, use the Keyboard Test tool to confirm the key registers. Press the Windows key and watch for the keycode to appear in the test interface. If it lights up, you are done. If it does not, continue below.

OS Mode Switch Positions by Model

Model Switch Location Mac Position Windows Position Firmware Type
K2 Rev A / Rev B Left side slider Leftmost Middle (Win/Android) Proprietary + optional QMK
K8 / K8 Pro Left side slider Leftmost Middle (Win/Android) Proprietary / QMK (Pro)
K6 / K6 Pro Left side slider Leftmost Middle Proprietary / QMK (Pro)
Q1 / Q2 / Q3 / Q5 No physical switch N/A VIA Layer 0 only QMK
V1 / V6 No physical switch N/A VIA Layer 0 only QMK

The K8 Pro and K6 Pro ship with QMK pre-flashed and support VIA out of the box. The standard K8 and K2 use Keychron's proprietary firmware unless you have manually flashed QMK via QMK Toolbox.

Fix a Remapped Windows Key in VIA

If the physical switch is in the correct position and the key still does not register, open VIA. VIA runs in Chrome or Edge at the via.app web address. Do not use third-party VIA mirrors. Connect your keyboard over USB, not Bluetooth, because VIA requires a stable HID connection to read and write the EEPROM.

  1. In VIA, select the Configure tab at the top left.
  2. Your board should appear automatically. If it does not, go to Settings, enable Show Design Tab, then load the board's JSON definition file from Keychron's GitHub repository for your specific model.
  3. Click Layer 0 in the layer selector. This is the base layer that runs when no other layer is active.
  4. Click the key position that corresponds to your Windows key. On a standard 75-percent layout like the K2, this is the key immediately left of the spacebar.
  5. In the keycode picker at the bottom, navigate to Basic, then find KC_LGUI (Left GUI). Click it to assign it.
  6. If the key was previously set to KC_NO (no output) or KC_TRNS (transparent, which passes through to a lower layer that may also be empty), that explains the dead key.

After assigning KC_LGUI, VIA writes to the keyboard's EEPROM immediately. No save button is needed. Disconnect and reconnect the board, then retest with the Keyboard Test to confirm the scancode is coming through.

Bluetooth Mode and Windows Key Behavior

Keychron's Bluetooth implementation on the K2, K8, and K6 uses a separate wireless MCU that mirrors the wired layer logic. If you are connected over Bluetooth and the Windows key is dead, the OS mode switch still applies. There is no separate Bluetooth-specific key mapping on non-Pro models. On Pro models with QMK, the Bluetooth layer is Layer 0 by default, same as wired.

One Bluetooth-specific failure mode: if the board was previously paired to a Mac and the pairing data was not cleared before pairing to Windows, some users report the board sending Mac scancodes regardless of the switch position. Clear the pairing by holding Fn plus the relevant Bluetooth channel key for three seconds until the LED flashes rapidly, then re-pair from scratch on Windows.

To verify your keyboard is sending the correct scancodes over Bluetooth, use the Keyboard Test in your browser on the Windows machine after re-pairing. If the Windows key now registers, the stale pairing was the cause.

Windows System-Level Blocks on the Win Key

If the keyboard is confirmed sending KC_LGUI but Windows still does not open the Start menu, the block is on the OS side, not the keyboard. Check these in order:

If you want to confirm the keyboard hardware is fully functional beyond just the Windows key, run a full matrix check with the Mac Keyboard Test if you are also using this board on macOS, or stick with the standard keyboard test on Windows.

Frequently Asked Questions

Why is the Keychron K2 Windows key not working even after moving the switch?

On the K2 Rev A specifically, the side switch contacts wear out after extended use and the board can misread the switch position. Try toggling the switch back and forth five times quickly, then settle it firmly into the Win/Android position. If that does not help, the switch contact may need cleaning with isopropyl alcohol applied with a thin tool, or the board needs a QMK flash so you can control the OS mode in firmware rather than relying on the physical switch.

Why is the Keychron K8 Windows key not working on the K8 Pro but the K8 standard works fine?

The K8 Pro ships with QMK and VIA enabled. If someone previously opened VIA and remapped Layer 0 on the Pro, that remap persists in EEPROM even after unplugging. The standard K8 uses proprietary firmware that cannot be remapped through VIA, so it is less vulnerable to accidental remaps. Open VIA on the K8 Pro and verify KC_LGUI is assigned on Layer 0 as described in the fix section above.

Does the Keychron Command key not working on Mac mean the same hardware is broken?

No. If the Command key stops working on Mac, the board is likely in Win/Android mode. The same slider that fixes the Windows key problem causes the Command key problem on Mac. The switch position is the single variable controlling which key acts as the GUI modifier on both operating systems.

Can I make the Windows key work on both Mac and Windows without moving the switch?

On QMK-capable boards, yes. In QMK Configurator or VIA, assign KC_LGUI to the key on Layer 0 and keep that assignment regardless of OS. On Mac, KC_LGUI is interpreted as Command. On Windows it is the Win key. The physical switch on non-QMK boards is not bypassable in software.

Will flashing QMK firmware void my Keychron warranty?

Keychron's published position is that flashing QMK on supported boards does not void the warranty, and they provide the QMK source files officially on their GitHub. Boards that do not have official QMK support listed on Keychron's site are a different matter. Check the QMK firmware repository for your exact model before flashing anything.

My Windows key works but Win plus other shortcuts do not. Is that the same problem?

That is a different issue. If Win alone opens the Start menu but Win plus D, Win plus E, or Win plus R do nothing, the keyboard is functioning correctly and the shortcuts are being suppressed by a Group Policy setting or a gaming mode in third-party software. Follow the Group Policy and registry steps in the Windows system-level section above.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester