Das, Havit and Everest Numpad Not Working: Budget Board Fixes That Actually Solve It

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 numpad is dead because either Num Lock state is being swallowed by a firmware bug, the USB port is starving the board of current, or the membrane dome cluster under keys 4-6 or 7-9 has delaminated from the PCB trace. Das Keyboard's 4 Professional and 5Q lines use a two-layer USB hub internally, which drops the numpad matrix off a separate logical device when the host port delivers less than 480 mA. Havit HV-KB395L and KB558CM boards ship with a capacitor-coupled Num Lock LED circuit that can latch in a ghost-off state after a hard power cut. Everest GT-100 and Maximus boards use a rubber dome membrane with a notoriously thin silver-ink trace running along the right column that cracks at the fold point near the numpad boundary.

Confirm the Fault Scope Before Touching Hardware

Before pulling keycaps or opening cases, establish exactly what is and is not responding. Open Keyboard Test and press every numpad key individually with Num Lock both on and off. Log which scan codes register and which produce nothing. This separates three distinct failure modes: all numpad keys dead (matrix or power fault), numpad keys dead only with Num Lock on (firmware or OS Num Lock remapping), or a rectangular cluster of dead keys (trace crack or dome dropout).

Num Lock Firmware and OS Fixes for Das, Havit, and Everest

Windows 11 and Windows 10 both store the Num Lock boot state per-user in the registry at HKEY_CURRENT_USER\Control Panel\Keyboard, value name InitialKeyboardIndicators. A value of 2 forces Num Lock on at login. A value of 0 forces it off. Havit boards are particularly vulnerable here because their onboard controller does not assert Num Lock state on USB re-enumeration; it defers entirely to the host. Set the value to 2, reboot, and retest.

Das Keyboard 5Q owners must also check the Das Keyboard Q software, version 3.1 or later. Navigate to Preferences, then Device Settings, then find the Num Lock Sync toggle. If it is enabled and your host sends a Num Lock-off signal during wake from sleep, the board obeys and kills the numpad. Disable that toggle. Das Keyboard 4 Professional has no companion software, so the fix is registry-only.

On macOS, Num Lock does not exist as a system-level state. If you have a Havit or Everest board connected to a Mac, the numpad keys output navigation codes by default. Go to System Settings, Keyboard, Keyboard Shortcuts, and check whether any modifier remapping is intercepting numpad scan codes. Alternatively, use Mac Keyboard Test to verify which codes are actually reaching the OS layer.

For Bluetooth keyboard number pad not working situations on all three brands, the additional variable is HID profile negotiation. Havit KB395L in BT mode sends a boot-protocol HID descriptor that some receivers interpret as a reduced-key layout, stripping the numpad entirely. Pair the board, then in Windows Device Manager under Human Interface Devices, right-click the Havit entry, select Properties, go to the Details tab, and set the property dropdown to Hardware IDs. If the ID ends in &MI_01, that is the numpad interface. If it is missing, the driver did not enumerate it. Uninstall the device, uncheck the box to delete driver software, replug or re-pair, and let Windows reinstall from scratch.

USB Power and Hub Faults on Das Keyboard 5Q

The Das Keyboard 5Q routes its two built-in USB-A ports through an internal GL850G hub IC. That hub draws power from the same upstream port feeding the keyboard controller. If your host port is a USB 2.0 port on a cheap motherboard header delivering only 400 mA instead of the spec 500 mA, the hub IC under-voltages and the numpad matrix, which shares a data line with the hub, drops out intermittently. Measure the port with a USB power meter. Anything below 4.75 V under load is the problem. Move the keyboard to a port directly on the motherboard I/O shield, not a front-panel header, and retest.

If you are using a USB-C to USB-A adapter or a dock, the negotiated current budget may be lower than 500 mA depending on the dock's power delivery contract. Connect the 5Q directly to a Type-A port with no adapter in the chain.

Membrane Trace and Dome Repair on Everest and Havit Boards

Everest GT-100 and Maximus boards use a three-layer membrane: top circuit layer, spacer, bottom circuit layer. The right-column numpad trace runs along the fold edge of the top layer. When that fold cracks, keys 3, 6, 9, and the decimal point go dead as a group because they share that column line.

  1. Remove all keycaps from the numpad cluster. Everest uses standard MX-stem caps; a keycap puller works without risk.
  2. Remove the case screws. Everest GT-100 has six Phillips PH1 screws on the underside, one hidden under the warranty sticker at the top-right corner.
  3. Lift the top case, disconnect the ribbon cable from the controller PCB by pulling the ZIF latch upward, not the cable itself.
  4. Peel back the membrane layers at the numpad right column fold. Look for a gray crack in the silver-ink trace under magnification.
  5. Apply conductive silver epoxy, under $5 for a small syringe from any electronics supplier, across the crack. Let it cure 90 minutes at room temperature before reassembly.

Havit HV-KB558CM uses a similar membrane but the common failure is dome dropout, where the polyurethane dome collapses and no longer makes contact. You can feel this as a key that actuates with zero tactile feedback. Replacement dome sheets for this footprint are available in generic 4x4 grid sheets. Align the dome center to the PCB contact pad, which is a circular gold ring approximately 4 mm in diameter.

Brand-by-Brand Fault Comparison

Brand and Model Most Common Numpad Fault Primary Fix Difficulty
Das Keyboard 4 Professional Registry Num Lock state conflict Set InitialKeyboardIndicators to 2 Easy
Das Keyboard 5Q GL850G hub under-voltage via USB dock Direct motherboard I/O port, no adapters Easy
Havit HV-KB395L (BT) HID boot-protocol stripping numpad interface Re-pair and force full HID re-enumeration Moderate
Havit HV-KB558CM Dome dropout on numpad cluster Replace dome sheet, realign to 4 mm contact pad Moderate
Everest GT-100 Right-column membrane trace crack at fold Conductive silver epoxy on cracked trace Moderate
Everest Maximus Num Lock firmware latch after power cut Registry fix plus full power cycle Easy

Frequently Asked Questions

Why does my Havit bluetooth keyboard number pad not work only on one device?

The Havit BT controller sends different HID descriptors depending on which Bluetooth version the host negotiates. A host that connects via BT 4.0 classic may receive a reduced descriptor that omits the numpad interface, while a BT 5.0 host gets the full layout. Try pairing to a different device to confirm. If the numpad works on one host and not another, the fix is on the host side: update the Bluetooth adapter firmware or switch to the USB cable connection.

Can I test whether the numpad keys are physically registering without installing software?

Yes. Use Keyboard Test in any browser. It reads raw HID scan codes from the browser's KeyboardEvent API, which bypasses driver layers. If a key lights up in that tool, the hardware and USB stack are working and your problem is OS-level remapping or application interception. If nothing lights up, the fault is at or below the USB device layer.

My Das Keyboard 5Q numpad works after a cold boot but fails after sleep. What is happening?

The GL850G hub inside the 5Q does not always re-assert its upstream connection cleanly after USB selective suspend. Windows puts USB devices into suspend after a configurable idle timeout. Go to Device Manager, Universal Serial Bus Controllers, right-click each USB Root Hub, select Properties, Power Management, and uncheck Allow the computer to turn off this device to save power. Do this for every root hub entry. Then go to Power Options, Change Plan Settings, Change Advanced Power Settings, USB Settings, USB Selective Suspend Setting, and set it to Disabled.

The Everest numpad keys feel mushy and do not register. Is this a software problem?

No. Mushy feel with no registration is a collapsed rubber dome. The polyurethane dome has lost its spring and sits flat against the membrane contact pad without generating enough force to complete the circuit. Open the board as described in the membrane section above and inspect the dome sheet. Collapsed domes look visually flat or slightly inverted compared to adjacent functioning domes. A replacement generic dome sheet is the correct fix, not any software adjustment.

Does the Das Keyboard Q software cause numpad problems if I uninstall it?

On the Das Keyboard 4 Professional, no, because that board has no companion software dependency. On the 5Q, uninstalling Q software removes the Num Lock Sync feature but also removes the ability to configure per-key lighting and macros. The numpad will function normally via standard HID after uninstall as long as your registry Num Lock state is set correctly. The board falls back to its default static lighting profile stored in onboard flash.

I replaced the membrane on my Havit board and the numpad still does not work. What did I miss?

Check the ZIF connector on the controller PCB. Havit uses a 0.5 mm pitch flat flexible cable locked by a top-contact ZIF latch. If the latch is not fully closed, columns 5 through 8 of the matrix drop out, which maps exactly to the numpad cluster. Press the latch flat with a spudger until it clicks. Also verify the membrane layers are stacked in the correct order: bottom circuit layer face-down on the PCB, spacer on top, top circuit layer face-up. Reversing any layer produces a dead numpad even with a brand-new membrane sheet.

Launch Companion Diagnostic Tool

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

Open Keyboard Tester