How to Keep Num Lock On After Startup on Windows: Step-by-Step Guide in 2026

If you’re tired of your number pad refusing to work every time you boot up your computer, you’re not alone. The Num Lock key defaulting to “off” at startup is one of those small annoyances that compounds over time, especially if you regularly enter numerical data, work with spreadsheets, or use the numeric keypad for navigation.

The good news? You can permanently enable Num Lock at startup through several reliable methods. This guide walks you through every solution that actually works in 2026, from the simplest Registry tweak to BIOS settings and third-party utilities.

Why Does Num Lock Turn Off at Startup?

Windows doesn’t randomly decide to disable your Num Lock key. The behavior stems from how your system stores keyboard states between sessions. By default, Windows remembers the Num Lock state from when you last shut down, but many systems are configured to override this and default to “off” regardless of your preference.

Several factors influence this behavior:

BIOS/UEFI settings often control the initial keyboard state before Windows even loads. If your motherboard’s firmware sets Num Lock to disabled, Windows inherits that setting.

Windows Registry values determine whether the operating system should enable Num Lock during the login screen and after you sign in.

Legacy compatibility settings from older Windows versions sometimes carry forward, maintaining outdated default behaviors that no longer make sense for modern workflows.

Understanding the source helps you pick the right fix. Some methods work at the hardware level, others at the operating system level, and some affect only your user account.

Method 1: Enable Num Lock Through Windows Registry

The Registry edit is the most direct and reliable solution for most Windows users. This method works across Windows 10, Windows 11, and even older versions still in use.

Step-by-Step Registry Edit

Press Windows + R to open the Run dialog, type regedit, and press Enter. If prompted by User Account Control, click Yes to grant permission.

Navigate to this exact Registry path:

HKEY_USERS\.DEFAULT\Control Panel\Keyboard

Look for a value named InitialKeyboardIndicators in the right pane. If it doesn’t exist, you’ll create it in a moment.

Double-click InitialKeyboardIndicators and change its value based on what you want enabled at startup:

• 2 = Num Lock only
• 1 = Caps Lock only
• 3 = Both Num Lock and Caps Lock
• 0 = Neither enabled

For most people, setting this to 2 solves the problem immediately.

If the value doesn’t exist, right-click in the right pane, select New > String Value, name it InitialKeyboardIndicators, then double-click it and set the value to 2.

Close the Registry Editor and restart your computer. Your Num Lock should now activate automatically at the login screen and remain on after you sign in.

Why This Method Works

The .DEFAULT user hive controls settings for the login screen and new user profiles. By modifying InitialKeyboardIndicators here, you’re telling Windows to enable Num Lock before anyone even logs in, which then carries through to your desktop session.

One important note: some laptops with function-key-controlled number pads might not respond to this setting because their Num Lock implementation differs from standard keyboards. If you’re using a laptop without a dedicated numeric keypad, you may need to check your keyboard’s specific documentation.

Method 2: Configure Num Lock in BIOS/UEFI Settings

BIOS and UEFI firmware provide hardware-level control over keyboard initialization. This method supersedes Windows settings because it activates before the operating system loads.

Accessing Your BIOS/UEFI

Restart your computer and immediately press the BIOS access key. Common keys include:

• Del or Delete (most common on desktops)
• F2 (common on laptops and some desktops)
• F10 (HP computers)
• F12 (Dell computers)
• Esc (certain HP and Lenovo models)

The exact key appears briefly on screen during the boot logo. If you miss it, restart and try again.

Finding the Num Lock Setting

BIOS interfaces vary significantly by manufacturer, but the setting usually lives in one of these sections:

• Boot or Boot Options
• Advanced or Advanced Settings
• Peripheral Configuration
• Integrated Peripherals

Look for an option labeled:

• Num Lock State
• Boot Up Num Lock
• NumLock Key
• POST NumLock

Change this setting to Enabled or On.

Save your changes (typically by pressing F10 and confirming) and exit. Your computer will restart with Num Lock enabled at the hardware level.

When BIOS Method Is Necessary

Some systems ignore the Windows Registry setting entirely because the BIOS forcibly controls keyboard initialization. Corporate computers, especially those with management features enabled, often fall into this category. If the Registry edit didn’t work for you, the BIOS setting almost certainly will.

Modern motherboards with UEFI interfaces sometimes hide this setting or label it differently. Check your motherboard manufacturer’s documentation if you can’t locate it. MSI’s support documentation and ASUS support resources provide searchable manuals for most models.

Method 3: Group Policy Editor for Windows Pro and Enterprise

Windows Professional, Enterprise, and Education editions include Group Policy Editor, which provides another avenue for controlling Num Lock behavior.

Using Group Policy Editor

Press Windows + R, type gpedit.msc, and press Enter.

Navigate through the left pane to:

Computer Configuration > Administrative Templates > System > Logon

Find the policy named Turn on Num Lock or Turn on convenience PIN sign-in.

Double-click the policy and set it to Enabled.

Click Apply, then OK. Restart your computer for the change to take effect.

Group Policy vs Registry

Group Policy essentially modifies Registry values through a more user-friendly interface. For single computers, the Registry method works equally well and doesn’t require Windows Pro or higher editions. Group Policy becomes valuable in managed environments where IT administrators need to deploy this setting across multiple machines through Active Directory.

Method 4: Use a Third-Party Utility

If you prefer avoiding Registry edits and BIOS settings, several lightweight utilities can manage Num Lock state at startup.

NumLock Manager Tools

NumLocker is a simple, free utility that runs at startup and forces Num Lock on. It consumes minimal system resources and works reliably across all Windows versions.

AutoHotkey scripts offer more customization. Create a simple script with this code:

SetNumLockState, AlwaysOn

Save it as a .ahk file and add it to your Windows startup folder (shell:startup in the Run dialog).

When to Use Utilities

Third-party tools make sense if you need additional keyboard customization beyond just Num Lock, or if you’re uncomfortable editing the Registry or BIOS. However, they add another program to your startup sequence, which can marginally slow boot times.

For most users, the Registry or BIOS method provides a cleaner, more permanent solution without additional software overhead.

Troubleshooting Common Issues

Even with correct settings, some systems exhibit stubborn behavior. Here’s how to address the most common problems.

Num Lock Turns Off After Login

If Num Lock activates at the login screen but disables after you sign in, the issue lies in your user-specific Registry settings.

Navigate to:

HKEY_CURRENT_USER\Control Panel\Keyboard

Create or modify the InitialKeyboardIndicators value here as well, setting it to 2.

This ensures your user profile maintains the Num Lock state independently of the system-wide setting.

Laptop-Specific Num Lock Behavior

Many laptops use Fn + Num Lock combinations because they lack dedicated numeric keypads. These implementations sometimes ignore standard Num Lock settings.

Check if your laptop has:

• Fn Lock functionality that might interfere
• BIOS settings specifically for Fn key behavior
• Manufacturer-specific keyboard utilities that override Windows settings

Lenovo, Dell, and HP laptops often include proprietary keyboard management software that takes precedence over Windows configuration.

Wireless Keyboard Complications

Some wireless keyboards, particularly those with built-in memory, store Num Lock state in the keyboard’s firmware rather than relying on Windows settings. If you’ve tried every method without success and you’re using a wireless keyboard, check for:

• Firmware updates from the keyboard manufacturer
• Configuration software specific to your keyboard model
• Hardware reset procedures that might clear incorrect default states

Logitech and Microsoft wireless keyboards typically include configuration utilities that manage these behaviors.

Which Method Should You Use?

Your ideal solution depends on your comfort level with system configuration and your specific hardware.

Method	Best For	Difficulty	Permanence
Registry Edit	Most Windows users	Easy	Permanent
BIOS/UEFI Settings	Systems where Registry fails	Moderate	Permanent
Group Policy	IT administrators, domain environments	Easy	Permanent
Third-Party Utility	Users avoiding system changes	Very Easy	Requires software

Start with the Registry method if you’re on a standard desktop or laptop with Windows 10 or 11. It takes less than two minutes and works for approximately 80% of users.

Move to BIOS settings if the Registry edit doesn’t stick after restart, or if you’re using managed corporate hardware.

Consider third-party utilities only if you need additional keyboard customization or want the simplest possible implementation.

Advanced Considerations for Power Users

Multiple User Accounts

If your computer has multiple user accounts, you’ll need to apply Registry changes to each user profile individually, or use the system-wide BIOS method that affects all accounts simultaneously.

To modify settings for all existing users, you can edit each user’s Registry hive, but this requires administrative access and careful navigation through HKEY_USERS.

Remote Desktop Scenarios

Remote Desktop Protocol (RDP) sometimes ignores local Num Lock settings because it captures keyboard state from your client machine rather than the remote session. If you frequently use Remote Desktop, you may need to enable Num Lock on your local machine before initiating the connection.

Some RDP clients include options to sync keyboard states. Check your Remote Desktop client’s settings under “Local Resources” or “Keyboard” configuration.

Virtual Machines

Virtual machines running Windows as guest operating systems require Num Lock configuration within the guest OS itself. The host machine’s Num Lock state doesn’t automatically pass through to virtual machines.

Apply the Registry or BIOS method inside the virtual machine just as you would on physical hardware. VMware and VirtualBox both respect Windows’ Num Lock Registry settings.

Maintaining Your Num Lock Setting

Once configured correctly, your Num Lock setting should persist indefinitely. However, certain events can reset it:

Windows updates occasionally reset keyboard-related Registry values, particularly during major feature updates. After significant updates, verify your Num Lock still activates at startup.

BIOS updates can restore default firmware settings, disabling your previously configured Num Lock behavior. After updating BIOS/UEFI firmware, recheck the setting.

Hardware changes, especially keyboard replacements, might introduce different default behaviors.

Keep a simple text file with your preferred Registry values and BIOS settings so you can quickly reconfigure after system changes.

Summary: Getting Num Lock to Stay On

The persistent Num Lock problem has multiple solutions because different systems control keyboard initialization differently. The Registry edit works for most standard Windows installations, while BIOS settings provide hardware-level control that supersedes software configuration.

Here’s your action plan:

1. Try the Registry edit first by setting InitialKeyboardIndicators to 2 in both .DEFAULT and CURRENT_USER hives
2. If that fails, enter your BIOS/UEFI and enable Num Lock at the hardware level
3. For managed environments, use Group Policy to deploy the setting across multiple machines
4. Consider third-party utilities only if you need additional features or want to avoid system configuration

Most importantly, don’t settle for manually enabling Num Lock every time you start your computer. With five minutes of configuration, you can eliminate this daily frustration permanently. The methods outlined here work reliably in 2026 across all current Windows versions, and they’ll continue working until Microsoft fundamentally changes how Windows handles keyboard initialization, which isn’t on the horizon.