Royal Kludge Rk61 Number Keys Not Working

Your Royal Kludge Rk61 number keys are not working, and you're probably not in the mood for guesswork. That's fair. This keyboard is simple, but its layered shortcuts confuse a lot of people.

The good news is that most causes are software settings, not broken hardware.

The RK61 is a 60% keyboard, so it has only 61 keys and no dedicated numpad. That means the number row doubles as the F1 through F12 row. As of 2026, the board's default Fn layer triggers this behavior, and it's responsible for most reports.

Let's fix it step by step.

Image source: Bing (Web (fair-use with source credit))

Quick Answer: Try Fn + Space Before Anything Else

Try pressing Fn + Space first. That toggles the Fn lock on the RK61. If the number row still types F1 through F12, check the Windows/Mac mode.

Then re-pair Bluetooth and test on another device. Most causes are settings, not hardware.

Why the RK61 Number Row Acts Up: Fn Locks, OS Modes, and Input Lag

Here's what's happening under the keycaps. The RK61 uses a 60% layout. To keep things compact, the number row pulls double duty as the function key row.

When the Fn layer is active, pressing 1 outputs F1, pressing 2 outputs F2, and so on. That's a handy shortcut, but it feels like a bug when you expect digits.

Image source: Bing (Web (fair-use with source credit))

The Fn lock is controlled by Fn + Space. Tap it once and the Fn layer stays active. Tap it again and it releases.

Many users enable this accidentally while gaming or typing. In our research with troubleshooting threads and buyer feedback, Fn lock confusion accounts for the majority of "numbers not working" reports.

Another layer is the operating system mode. The RK61 has a Windows mode and a Mac mode. You toggle them with Fn + W and Fn + M.

If the board sits in Mac mode on a Windows PC, some keys report incorrect scancodes. The numbers can act as special characters or nothing at all. That's easy to miss because nothing looks wrong on the keyboard itself.

Connection mode also plays a role. In Bluetooth, the keyboard sleeps after a few idle minutes. The first keystroke after wake-up can drop entirely.

That feels like a dead key, but it's just the radio reconnecting. For the most reliable input, use the USB-C cable and test the row in wired mode. Manufacturer specs confirm the RK61 supports USB-C, Bluetooth, and 2.4GHz depending on the version, so we're dealing with a board built for flexibility.

There's also input lag to consider. Poor Bluetooth placement can cause dropped packets. A metal desk, a crowded 2.4GHz band, or a laptop sitting behind a monitor can all interfere.

Wired mode eliminates that variable instantly. If you need a quick reference, the official Royal Kludge support page has the full manual and firmware downloads.

Use This Diagnostic Flow to Pinpoint the Problem

Don't try fixes at random. Follow this simple flow to find the exact cause in under two minutes. It's a decision tree, not a guessing game.

Start by pressing Fn + Space once. Then type a number. If it works now, the issue was Fn lock.

If not, move on.

Next, check the OS mode. Hold Fn and press W for Windows mode, or Fn + M for Mac mode. Try the numbers again.

If they work, your keyboard was sending the wrong signal. This is extremely common for people who switch between a work laptop and a personal PC.

Still dead? Switch to wired mode with the USB-C cable. Unplug the Bluetooth receiver or disconnect the keyboard from your computer's Bluetooth settings.

Then test the number row. If numbers work on USB, the problem lives in the wireless connection, not the board.

If none of that helps, test the keyboard on another device. A phone or a second computer works fine. Numbers that type correctly on another device point back to the original computer's settings.

Numbers that fail everywhere point to the keyboard itself. That split is the whole game.

Here's the same logic in a quick reference table:

One extra tip: while testing, open a free online key tester in your browser. It shows exactly which keycodes the board sends. That turns a vague "not working" into a concrete answer in seconds.

Step-by-Step Fixes for Every Cause

Now let's apply the fix. Work through these in order. Most people stop after step two.

Each step is quick and safe.

1. Toggle the Fn lock. Press Fn + Space once. Test the number row.

If digits appear, you're done. This is the single most common fix.

2. Correct the OS mode. Press Fn + W for Windows. Press Fn + M for Mac.

Test again. If you switch devices often, make this your second habit after plugging in.

3. Reset the connection. For Bluetooth, delete the pairing from your computer. Then press and hold the Bluetooth key (usually Fn + P or the dedicated BT key, depending on the version) to enter pairing mode.

Re-pair and test. For a 2.4GHz receiver, unplug and plug it back in, then restart the keyboard.

4. Factory reset the keyboard. Unplug it. Hold Fn + Space, then plug the USB cable back in while holding both keys.

Release after three seconds. This restores default settings and clears any stuck macro layer.

5. Update the firmware. Download the latest firmware from the Royal Kludge support page. Follow the included instructions exactly.

Do not unplug the cable during the flash. A botched firmware update can lock up the board.

6. Clean or replace a faulty switch. If a single number key never works, the switch may be dirty or dead. On the RK61, switches are typically hot-swappable.

Pull the keycap and switch with a puller, then install a fresh one. No soldering needed.

If you get through all six and numbers still fail, the issue is likely hardware. Keep reading.

Don't Make These Mistakes When Troubleshooting

Half of the failed fixes we see come from avoidable errors. Here are the big ones, straight from real user stories.

Mistake one: ignoring the Fn lock. People assume the keyboard is broken and order a replacement. Then the replacement behaves the same way because the setting follows the keyboard, not the PC.

Mistake two: testing in the wrong mode. If the RK61 is set to Mac mode on a Windows computer, keys misbehave. Check the mode before blaming hardware. It's a two-second test.

Mistake three: forgetting Bluetooth dormancy. A keyboard that's been idle for a few minutes drops the first keystroke. That's not a broken key. Press once to wake it, then type again.

If you're still suspicious, unplug and plug in the USB-C cable.

Mistake four: cleaning with sloppy technique. Spraying compressed air straight down can push debris deeper into the switch. Instead, tilt the board at an angle and clean from the side. For a stuck switch, use a switch puller and gently work the stem.

Mistake five: opening the case before checking firmware. Voiding your warranty for a fixable firmware bug is a painful way to learn patience. The RK61 doesn't need a teardown for the issues in this guide.

Mistake six: replacing keycaps to fix a switch. Keycaps don't change the electrical contact. If the switch is dead, a new cap won't help. You need a new switch, not a pretty set of plastic.

Mistake seven: blaming the keyboard when it's software. Some keyboards have unwanted input filters or remapped keys. Check your operating system's keyboard settings before buying anything. If you're on Windows, that means the Language and Keyboard section.

If you're on macOS, it's the Modifier Keys settings.

Hardware Problems: Switches, Solder, and When to Stop Fixing It Yourself

At this point, you have worked through every software setting, connection mode, and factory reset. If the number row still fails, hardware is the likely culprit. Here is how to tell the difference between a minor fix and a repair that needs a pro.

Image source: Bing (Web (fair-use with source credit))

Is it one key or the whole row? A single dead number key points to a bad switch. On the RK61, switches are hot-swappable. Use a switch puller to remove the faulty switch.

Install a new one in the same orientation. No soldering needed. Aggregate user feedback reports that Gateron and Outemu switches fit the board stock, but any three-pin mechanical switch should work.

Does every number key fail? That suggests a circuit board fault or a damaged ribbon cable inside the case. If you feel confident, you can open the keyboard and reseat the ribbon connecting the main PCB to the key matrix. But this voids your warranty.

The official RK61 manual states that unapproved disassembly can cancel support.

When should you stop fixing it yourself? If you have tried a new switch and the key still does not register, stop. The issue could be a cold solder joint or a cracked trace on the PCB. That requires a soldering iron and multimeter.

For most users, contacting Royal Kludge support or buying a replacement board is the smarter move. At the RK61's price point, a full replacement often costs less than a repair shop.

Frequently Asked Questions

Why do my number keys type F1 through F12 instead of numbers?

The Fn lock is active. Press Fn + Space once to release it. This toggles the number row between digit mode and function key mode.

It is the most common cause for this symptom.

How do I factory reset my Royal Kludge RK61?

Unplug the USB cable. Hold Fn and Space together. Plug the cable back in while holding both keys.

Release after three seconds. The keyboard resets to factory defaults.

Can I replace the switches on my RK61 without soldering?

Yes. The RK61 uses hot-swappable switch sockets. Use a switch puller to remove the old switch.

Line up the pins and press the new switch into place. No soldering required.

Why do my number keys work on one computer but not another?

Your OS mode is set wrong for that device. Use Fn + W for Windows or Fn + M for Mac. The keyboard remembers this setting, so it can be correct for one computer and wrong for another.

How do I clean a stuck number key switch?

Pull the keycap with a keycap puller. Use compressed air at an angle, not straight down. Work the switch stem gently with a switch puller to loosen debris.

If that fails, replace the switch entirely.