Apple Magic Keyboard Numpad Not Working on Windows? Here's the Real Fix

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 Mac Keyboard Tester

Your Apple Magic Keyboard numpad is not working on Windows because Windows assigned it the wrong keyboard layout, disabled Num Lock at the driver level, or never received the Apple HID descriptor it needs to map the extended key cluster correctly. The Magic Keyboard's numpad section uses a standard USB or Bluetooth HID report, but Apple encodes modifier behavior differently than a Windows OEM keyboard, and Windows 10 and 11 both default to a US-QWERTY HID layout that drops or remaps several numpad scancodes. There is no hardware fault here in the vast majority of cases, no broken membrane, no failed Scissor mechanism contact, just a software handshake problem you can resolve without touching Device Manager blindly.

Confirm the Numpad Is Actually Sending Keystrokes

Before changing any settings, verify which keys are dead and which are alive. Open the Mac Keyboard Test in your browser, press every numpad key individually, and watch for visual registration. If the numpad digits 0 through 9, the period, Enter, and the arithmetic operators all light up in the tester, Windows is receiving the scancodes fine and your problem is purely an application-level layout issue. If nothing lights up on the entire numpad cluster, you have a Num Lock state problem or a Bluetooth pairing gap. If only some keys register, for example the operators register but digits do not, you have a scancode remapping conflict introduced by a third-party utility like AutoHotKey, SharpKeys, or Microsoft PowerToys Keyboard Manager.

Write down exactly which keys fail. That list determines which fix you go to first.

The Num Lock Problem on Apple Keyboards in Windows

Apple ships the Magic Keyboard without a physical Num Lock key. On macOS the numpad is always active. Windows, however, stores the Num Lock state in the registry and defaults it to OFF after a clean install or after the HID driver re-enumerates the device, which happens every time you re-pair over Bluetooth. When Num Lock is off, numpad digit keys send navigation scancodes: scancode 0x4F becomes End, 0x50 becomes Down Arrow, and so on.

To force Num Lock on permanently, open Registry Editor (Win + R, type regedit, Enter) and navigate to HKEY_USERS\.DEFAULT\Control Panel\Keyboard. Change the value of InitialKeyboardIndicators from 0 to 2. Log out and back in. The value 2 sets bit 1, which is the Num Lock flag. This applies system-wide before any user profile loads, so it survives Bluetooth re-pairing.

If you are on a domain machine where Group Policy overwrites that key, ask your admin to set Computer Configuration > Administrative Templates > System > Logon > Turn on Num Lock to Enabled.

Driver and Layout Fixes for Windows 10 and Windows 11

Windows assigns keyboard layouts at two levels: the HID class driver (which translates USB or Bluetooth scancodes to virtual key codes) and the language layout DLL (which maps virtual key codes to characters). The Magic Keyboard needs the Apple Wireless Keyboard driver from Boot Camp to get full scancode coverage, including the numpad cluster, the Fn layer, and the top-row function keys.

  1. Download the Boot Camp Support Software for your Mac model from Apple's support downloads page. The package is a self-extracting EXE. Even on a non-Mac Windows machine you can extract it with 7-Zip and install only the AppleKeyboardInstaller64.exe found under BootCamp\Drivers\Apple.
  2. Run AppleKeyboardInstaller64.exe as Administrator. It installs the Apple HID driver that correctly maps the extended numpad cluster scancodes.
  3. After installation, open Device Manager (devmgmt.msc), expand Keyboards, right-click Apple Wireless Keyboard, and choose Update Driver > Browse My Computer > Let Me Pick. Select Apple Wireless Keyboard from the list. Do not choose the generic HID Keyboard Device entry.
  4. Reboot. Re-pair the keyboard if it was connected over Bluetooth.

If you are on Windows 11 and the Apple driver refuses to install due to a signature enforcement error, open an elevated PowerShell and run: bcdedit /set testsigning on, install the driver, then run bcdedit /set testsigning off and reboot. This is a temporary toggle and does not weaken system security permanently.

Layout Conflicts: Comparing Common Failure Scenarios

Symptom Root Cause Fix
All numpad keys send navigation (arrows, Home, End) Num Lock state is OFF in registry Set InitialKeyboardIndicators to 2 in HKEY_USERS\.DEFAULT\Control Panel\Keyboard
Numpad digits work, numpad Enter does not Generic HID driver maps numpad Enter (scancode 0xE01C) to regular Enter Install Apple Boot Camp HID driver
Numpad keys type wrong characters (e.g., comma instead of period) Windows language layout set to non-US locale Settings > Time and Language > Language and Region > set keyboard to English (United States)
Numpad works in some apps, dead in others App-level Num Lock override or AutoHotKey script running Disable AutoHotKey / PowerToys Keyboard Manager, retest
Numpad dead only after Bluetooth reconnect HID re-enumeration resets Num Lock state Registry fix above plus Apple driver install

After applying any fix, retest with the Mac Keyboard Test before touching anything else. Layering fixes without testing between steps is how you end up with three conflicting remapping rules and a keyboard that works in Notepad but not Excel.

Bluetooth-Specific Issues with the Magic Keyboard on Windows

The Magic Keyboard with Touch ID (model A2449) uses Bluetooth 5.0 and pairs in two modes: a standard HID-over-GATT profile and a proprietary Apple mode. Windows only sees the HID-over-GATT profile, which is correct, but some Bluetooth adapters running Intel or Realtek firmware drop extended descriptor packets during pairing, causing Windows to enumerate the keyboard with a truncated key map that omits the numpad cluster entirely.

Check your Bluetooth adapter firmware. Open Device Manager, expand Bluetooth, right-click your adapter, Properties, Driver tab. Intel adapters should be on driver version 22.110 or later. Realtek adapters should be on 1.3.901.2 or later. Older firmware versions have confirmed HID descriptor truncation bugs. Update through Windows Update > Advanced Options > Optional Updates, not through the adapter manufacturer's website, because Windows Update delivers the version validated for your chipset stepping.

If you are using a USB Bluetooth dongle under $15, replace it. Cheap CSR8510-based dongles have a well-documented HID report size bug that silently truncates descriptors longer than 256 bytes. The Magic Keyboard's descriptor is 273 bytes.

Frequently Asked Questions

Why does the Apple Magic Keyboard numpad work on macOS but not on Windows?

macOS uses its own HID stack and keeps Num Lock permanently active at the kernel level. Windows uses a stateful Num Lock flag stored in the registry that defaults to off, and its generic HID driver does not fully parse Apple's extended HID descriptor without the Boot Camp driver installed.

Do I need a Mac to download the Boot Camp drivers?

No. Apple hosts the Boot Camp Support Software packages as direct downloads on their support site. You can download the ZIP or EXE on any Windows machine, extract it with 7-Zip, and run only the keyboard installer from the Apple driver subfolder.

My numpad number keys work but the numpad Enter key still does nothing. Why?

Numpad Enter sends scancode 0xE01C, which is a separate extended scancode from regular Enter at 0x1C. The generic Windows HID driver often maps both to the same virtual key. The Apple Boot Camp HID driver distinguishes them correctly. Install that driver and the numpad Enter will register as a distinct key in all applications.

Will this fix work on Windows 11?

Yes. The registry path, the Boot Camp driver install process, and the Bluetooth firmware update steps all apply identically to Windows 11. The apple keyboard number pad not working windows 11 reports are more frequent only because Windows 11 does a more aggressive HID re-enumeration on wake from sleep, which resets the Num Lock state more often than Windows 10 did.

Can I use the keyboard tester to check individual numpad keys?

Yes. The Mac Keyboard Test reads raw browser KeyboardEvent data, so it shows you exactly which virtual key codes Windows is delivering per keypress, independent of any application layout. It is the fastest way to confirm whether your fix worked before rebooting or changing additional settings.

I fixed the numpad but now my Option and Command keys are swapped. How do I fix that?

Open the Apple Keyboard control panel installed by the Boot Camp driver (Start > Apple > Apple Keyboard). Check the box labeled Swap the Command and Option keys. Alternatively, in PowerToys Keyboard Manager, remap Left Alt (virtual key 0xA4) to Left Win and Left Win (0x5B) to Left Alt. Do not do both or you will create a circular remap.

Launch Companion Diagnostic Tool

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

Open Mac Keyboard Tester