Your arrow keys stop moving between cells in Excel because Excel is no longer treating them as navigation commands. The most common cause is Scroll Lock being on, which turns the arrows into a viewport-scrolling tool instead of a cell selector. Other causes include the numeric keypad with Num Lock off, Sticky Keys or Filter Keys in Windows, a frozen pane, cell-edit mode, an add-in intercepting keystrokes, or a hardware-level key remap. Each cause produces a slightly different symptom, and the symptom pattern tells you which layer failed.
Excel's grid is a focus model, not a scrolling model. When you press an arrow, Excel checks three things in order: whether a cell is in edit mode, whether a modal input layer is active, and whether Scroll Lock has redirected the arrow to the viewport. That ordering matters, because a stuck arrow with the wrong diagnosis can waste an hour on the wrong fix. The layers are independent, so more than one can be wrong at once.
The mechanism: why arrows move cells, not the page
Every keypress in Excel is a message routed through Windows, then through Excel's input handler, then to whichever object has focus. Focus normally sits on the active cell. When Scroll Lock is engaged, Excel reroutes arrow keys to the scrollbars instead of the cell cursor. The Excel status bar shows "Scroll Lock" when this is active, but only if you have not hidden the status bar.
Scroll Lock is a legacy toggle from the IBM PC era, when it let the arrow keys scroll a text screen without moving the insertion point. Excel inherited it. On most desktop keyboards, Scroll Lock lives in the top row near Print Screen and Pause. Many compact laptops and Apple keyboards omit the key entirely and emulate it with Fn+C or Fn+K, which is why some users cannot turn it off by pressing a physical key.
Num Lock is the second routing layer. When the numeric keypad is active for digits, the arrow-labeled keys on the pad (2, 4, 6, 8) output numbers, not directions. Off, they behave as arrows. If your main arrow cluster works but the keypad does not, Num Lock is the culprit.
A frozen pane is a third layer. Freeze Panes locks rows or columns on screen, and arrows still move the active cell, but the view no longer follows beyond the frozen boundary. Users often read this as "arrows stopped working" when the cell cursor actually moved off-screen.
How Excel's input modes change arrow behavior
Excel has several input states that alter what an arrow does:
Cell selection mode: default; arrows move the active cell one cell per press, one visible column or row per press in the frozen region. Edit mode: arrows move the text insertion point inside the cell, not the cell cursor. Press Enter or Esc to exit. Enter mode in a formula: arrows still move the cell cursor while a formula is being built, and Excel inserts cell references instead of moving focus. Scroll Lock on: arrows scroll the worksheet viewport by one row or column per press. Filter or AutoFilter dropdown open: arrows navigate the dropdown list, not the grid. Data Form or Protected View banner active: keystrokes may be intercepted before reaching the grid.
The counterintuitive detail: in Excel for Windows, pressing an arrow while a cell is in edit mode does not move the selection, but pressing F2 toggles edit mode, and pressing Ctrl+Enter commits all selected cells. Users who see arrows "doing nothing" are often in edit mode with a blinking cursor they have not noticed. Look for the status bar text "Edit" in the lower-left corner.
Another professional caveat: an Excel add-in can insert a keyboard hook that swallows arrows before Excel sees them. A power-user macro or a third-party productivity add-in is a common hidden cause. Disabling add-ins one at a time isolates this in minutes. This is the failure mode most troubleshooting guides skip.
Quantified context: how often each cause appears
Across IT support logs reported in public help-forum datasets, Scroll Lock and Num Lock account for the majority of "arrow keys stopped working" tickets. A frozen pane and edit mode are the next most common. Less than a tenth involve add-ins, hardware remap, or accessibility settings. That ranking matches the cost of each cause: a single key toggle is free to test, while an add-in audit takes five to fifteen minutes.
The scroll speed under Scroll Lock is the same as a single arrow press in normal mode: one cell per press, and roughly twenty to forty cells per second when held. On a 100,000-row worksheet, a stray Scroll Lock press does not damage anything, but it wastes time because users believe the cursor is moving when only the viewport is. The distinction is visible: the cell name box in the top-left still shows the original cell, while the visible rows shift.
Timing matters, too. Excel's AutoSave and AutoRecover intervals run every few minutes, so a stuck-arrow session that lasts an hour risks losing work only if a crash occurs. The arrow problem itself is nondestructive. The risk is user error during the confusion, such as overwriting data while thinking the cursor moved.
Timeline: typical recovery path for a stuck arrow key
| Step | Action | Typical time to resolve | What you learn |
|---|---|---|---|
| 1 | Check status bar for "Scroll Lock" | 2-5 seconds | Confirms the most common cause |
| 2 | Press Scroll Lock or Fn+C on laptops | 1-2 seconds | Toggles viewport scrolling |
| 3 | Check Num Lock and press keypad arrows | 2-5 seconds | Isolates keypad from main cluster |
| 4 | Press F2 or Esc to leave edit mode | 1-3 seconds | Restores cell navigation |
| 5 | Check Freeze Panes under View tab | 10-20 seconds | Explains off-screen cursor |
| 6 | Disable add-ins in Options | 5-15 minutes | Isolates keyboard hooks |
| 7 | Check Sticky Keys and Filter Keys | 1-3 minutes | Rules out accessibility filters |
| 8 | Test in a new Excel profile or Safe Mode | 5-10 minutes | Distinguishes Excel corruption |
Most cases resolve in the first five steps, under thirty seconds. The rest are rare but slow, which is why triage order matters. Working from cheapest test to most expensive test is the whole strategy.
Edge cases: hardware, accessibility, and environment
Sticky Keys, a Windows accessibility feature, lets modifier keys latch. If a modifier latches accidentally, an arrow press becomes Shift+Arrow or Ctrl+Arrow. Shift+Arrow extends a selection instead of moving the cursor, which looks like a broken arrow. Filter Keys slows or ignores repeated keystrokes, so a held arrow appears dead. Enable these intentionally on a work laptop and you can recreate the failure on demand.
Hardware remaps and KVM switches are a second edge case. A mechanical keyboard with a firmware-level remap, a gaming keyboard profile, or a KVM switch that drops key-release events can send a stuck modifier to Windows. The same key then appears broken only in certain ports or profiles. Test with the on-screen keyboard to rule out hardware: if on-screen arrows work, the physical keyboard or its driver is at fault.
Remote Desktop and virtual machines add a third layer. Key combinations such as Ctrl+Alt+Arrow are intercepted by the RDP client or the host OS, so the guest Excel never receives them. Scroll Lock itself may not pass through some remote clients at all, which is why users on remote desktops sometimes cannot toggle it and must use the on-screen keyboard inside the session.
Excel Online and mobile apps behave differently. In the browser, arrows require the grid to have focus; clicking a cell first restores navigation. On mobile, arrow keys only exist with an attached hardware keyboard, and iOS and Android handle external keyboard events through their own accessibility layers. If arrows work on desktop but not in the browser, focus loss is almost always the cause.
Mac keyboards need a note. Apple's compact keyboards do not include Scroll Lock, and macOS remaps the function keys by default. Fn+Left and Fn+Right scroll horizontally in many apps, but Excel for Mac maps navigation differently. The View menu and the status bar are the reliable places to check, not the physical key.
Misconceptions that send people down the wrong path
Misconception one: "The keyboard is broken." A broken arrow key usually fails on every app, not just Excel. If arrows work in a browser, text editor, or the Start menu, the key is fine and the problem is Excel-specific. Test outside Excel first; it takes ten seconds and halves the diagnosis.
Misconception two: "Reinstalling Excel will fix it." Reinstalling does not change Scroll Lock, Num Lock, edit mode, or an add-in intercept. It does not change the keyboard driver either. Office repair is useful for corruption, which is a small minority of cases.
Misconception three: "It is a Windows update bug." Some updates have introduced keyboard issues, but the arrow-key symptom in Excel is overwhelmingly an input-state problem. A current Windows build with Scroll Lock on produces exactly the same failure as an older build. Version checks are a low-yield diagnostic.
Misconception four: "The arrow keys are disabled in protected view." Protected View restricts editing, but it does not disable arrows. If arrows fail in Protected View but work after enabling editing, the likely cause is a modal banner or dialog stealing focus, not the protection itself.
The professional caveat worth repeating: multiple layers can fail at once. A laptop with a hardware remap and a latched Sticky Keys setting will not be fixed by turning off Scroll Lock alone. Fix one layer, retest, then move to the next. Do not stack fixes, because you will not know which one worked.
Practical actions: a tested sequence
Work in this order, and stop at the first step that fixes the symptom.
Look at the status bar, lower-left. If you see "Scroll Lock," press the Scroll Lock key, or Fn+C on laptops without one. Retest with one arrow press. Press F2, then Esc. This exits edit mode and returns the arrows to cell navigation. Retest. Press Num Lock once and test the keypad arrows separately from the main cluster. If the main cluster works, the keypad is the issue. Open the View tab and check Freeze Panes. If a pane is frozen, choose Unfreeze Panes and retest. Open File > Options > Add-ins. Set each add-in to inactive in turn, restarting Excel between changes, until arrows work. Open Windows Settings > Accessibility > Keyboard. Turn off Sticky Keys and Filter Keys, then retest. Test arrows in Notepad. If they fail there too, the problem is the keyboard, driver, or KVM, not Excel.
For persistent cases, launch Excel in safe mode by holding Ctrl while starting the app. Safe mode skips add-ins and customizations. If arrows work in safe mode but fail in normal mode, an add-in or startup macro is confirmed. From there, disable startup items one at a time. This isolates the culprit without uninstalling anything.
If arrows fail only in one workbook, the file may contain a macro or event handler that captures keystrokes. Open a blank workbook and test there. Working in one file and failing in another points to file-level customization, not system settings. The fix is to review the workbook's VBA project or open it with macros disabled.
Limitations: what this diagnosis cannot cover
This explanation covers Excel's input layers on desktop Windows, Mac, and the browser. It does not cover physical keyboard repair, driver-level firmware repair, or enterprise device-management policies that block key events. Some organizations deploy Group Policy settings that disable certain accessibility features or remap keys, and those behaviors vary by environment.
The ranking of causes is typical, not universal. A specific machine may have an unusual add-in or a driver bug that only appears with one keyboard model. The sequence above is a triage strategy, not a guarantee, and the safest test is always the same: isolate one layer at a time and retest after each change.