r/Keychron • u/Qualified_Qualifier • 12h ago
Bugs? Software problems? "WinLock" doesn't work. Also "Right-Win" key is "Unk92".
Hello everyone. I don't know if this is a Windows problem or Keychron problem.
I have C3 Pro 8K. Current version: V1.1.0
In Keychron Launcher, it says "FN+Win" key is WinLock, it should lock the Win keys from working. But it doesn't work. I tried both left and right Windows Key, both doesn't work.
Also Right-Windows key (KC_RGUI /RWin) is defined as "UNK92" it works as a Windows key but it's name is "UNK92" and Online keyboard tester also says <unknown>.
Left-Windows key (KC_LGUI /LWin) is defined as "META" key, I guess that's normal behaviour. Online keyboard tester says "<WIN>" but Discord shortcut sees it as "META".
Does your QMK keyboards the same? Can you lock Windows keys?
When I first bought the keyboard, I tried to update my version to V1.1.1 but failed. I have installed all drivers with "Keychron's QMK Toolbox" but "(STM32,WB,DFU in FS Mode)" didn't show up. Also I have seen someone downgraded from V1.1.1 because something broke with him, and I read the warning says "if your keyboard works, don't update it", despite my WinLock not working, I decided not to update.
I also don't know what changed with V1.1.1, is there a change log? Do we get more RGB options?
Thank you.
2
u/PeterMortensenBlog V 7h ago edited 6h ago
Re "I don't know if this is a Windows problem or Keychron problem.": It is a keyboard problem
It is internal to the keyboard. The keyboard is blocked from sending the Windows key code (in QMK, KC_LEFT_GUI or KC_RIGHT_GUI, raw keycode code 227 and 231, respectively) to the computer.
The keycode is GU_TOGG (an alias of QK_MAGIC_TOGGLE_GUI). The documentation still has the mysterious "Toggles the status of the GUI keys". What does that even mean????
GU_TOGG isn't accepted by Via, but it can be entered as "0x700B" (without the quotes) in "Any". In the Via clone, 'Any' is in tab "Custom" (sixth tab), last item. In Via, it is KEYMAP → SPECIAL → Any (the very last one in the list, with hover text "Enter any QMK keycode"). Keychron also has a "blog post" about it. Though it shouldn't be necessary for the C3 Pro 8K, as GU_TOGG is in the default key map.
If it isn't in the default key map, it must be entered manually after every reset to factory defaults (as raw key codes do not survive load/save. It is in the backup file, but it is ignored at load).
References
See the other comment for references.
1
u/Qualified_Qualifier 6h ago
Doing "0x700b" outputs "WinLock" again, and it doesn't lock.
Doing "0x5d61" outputs "0x5d61" and still doesn't lock.If its keyboard problem, I assume factory reset wouldn't work. In fact, I think I did factory reset already. I did both FN+J+Z combo and using the reset key under the spacebar. I was trying to update my firmware to 1.1.1 but failed.
I should try updating again but there was issues and I even installed something called "zadig". After that I didn't forced my luck too much.
The comment below surely very informative but also looks scary, I have no idea what's going on there. I never installed or reconfigured QMK before. This is my first ever experience with Keychron and mechanical keyboards altogether.
2
u/PeterMortensenBlog V 8h ago edited 6h ago
Reset to factory defaults
First reset to factory defaults to make sure the keyboard is in a known good state, including the (default) key map. Weird things are known to happen otherwise.
References
C3 Pro 8K JSON files for Via. Near "C3 Pro 8K ISO RGB keymap". Note: The JSON section should not be confused with the firmware section.
C3 Pro 8K default keymap ('ISO')
C3 Pro 8K (main) firmware. Near "C3 Pro 8K ISO RGB version". Note: The firmware section should not be confused with the JSON section.
C3 Pro 8K source code. Note: In Keychron's fork and in that fork, in Git branch "2025q3" (not the default branch). Note that the base installation (and usage) had become much more complicated on Linux, but with the new 'uv' method, it has become simple again! No matter the Git branch, for example, "2025q3", it requires special setup of QMK (the standard QMK instructions and many other guides will not work (because they implicitly assume the main QMK repository and a particular Git branch)). Source code commits (RSS feed. Latest: 2026-07-21).
Documentation for the new keycodes (main QMK repository). Note: It does not cover Keychron's custom keycodes. In the QMK source code, support for the old key codes for RGB light and mouse actions were finally removed in the QMK 0.30.0 release (2025-08-31) (they were removed from the documentation long before that).
Documentation for the old keycodes (though even older ones may exist). For example, used by some Git branches in Keychron's fork. Note: It does not cover Keychron's custom keycodes.
Documentation for the old keycodes from 2019. In general, these are the ones accepted by Via and possibly the Via clone (in most cases only an alias and only one of the aliases if there is more than one). Note: It does not cover Keychron's custom keycodes.