Command Prompt Won T Let Me Type

If Command Prompt opens but won’t accept typing, a keyboard or focus problem is a common first thing to rule out with about 3 quick checks: switch to another app, click inside the window, and try a different keyboard. If you ignore it, you can lose access to repair commands, settings changes, and recovery steps for a broken Windows session. This guide covers keyboard failure, console-mode mismatch, and Windows input corruption in that order.

Likely causes

The most common cause is simple: the keyboard is not reaching the active window. Less often, Command Prompt opens without focus, or Windows routes input through a console host that behaves differently. Administrator context, Windows Terminal settings, Safe Mode, and a damaged user profile can also change how CMD accepts input.

Say your keyboard types fine in Notepad, Edge, and the Run box, but CMD ignores every key. That points away from the keyboard itself and toward a console or Windows input issue. Suppose Command Prompt accepts input on a standard user profile but stops responding to keystrokes in a separate work profile. That points more toward the user profile than the system as a whole.

📊 wikiHow notes Windows 10 users can replace Command Prompt with Windows PowerShell in the Power User menu. Source: Wikihow.

Command Prompt decision table

Check the keyboard and focus first

If typing works everywhere else, begin here. Command Prompt can open and still ignore input if another window has focus, the keyboard connection is unstable, or the input path is blocked before it reaches CMD. Command Prompt is a Windows command-line tool, and you can open it from Start search, Run, or an admin context.

1. Open any text box outside CMD, such as Notepad or the Run dialog with Win + R.
2. Type a few characters. If that fails too, check the keyboard connection first.
3. For USB or wired keyboards, unplug and reconnect the cable. Try a different USB port if one is available.
4. For Bluetooth keyboards, turn Bluetooth off and on, then reconnect the device.
5. Open Command Prompt again from Start search or by typing cmd in Run.
6. Click once inside the black CMD window before typing. A ready window may show a blinking cursor or dash.

A dead keyboard or loose connection is still the fastest explanation at this point. If typing works in other apps but not in CMD, move to the console-specific checks below.

Why does typing work everywhere else?

When the keyboard works in Word, Settings, and browser fields, the hardware is usually fine. That leaves Command Prompt focus, console settings, or Windows input handling. If CMD is open but inactive, a click inside the window can restore input. If it still refuses keys, compare normal mode with Safe Mode.

1. Open Command Prompt from the Start menu search box or from Win + R by entering cmd.
2. Click once directly inside the CMD window, not on the title bar.
3. Try typing a simple command such as dir.
4. If nothing appears, close CMD and reopen it from a different launch path, such as Start search instead of a pinned shortcut.
5. Open the On-Screen Keyboard from Ease of Access Center and test input there.

A common mistake is assuming the window is frozen when it only lacks focus. A blinking dash or cursor is often enough to show CMD is ready.

Can’t type in command prompt after opening it as administrator?

Administrator privileges matter for some tasks, but they do not usually fix input by themselves. If standard CMD fails and elevated CMD fails the same way, the problem is broader than permissions. If only the elevated window behaves differently, that difference helps narrow the cause to context, policy, or a host setting.

1. Open cmd.exe with elevated permissions from Start search or a shortcut, then choose Run as administrator.
2. Compare the elevated window with a standard CMD window opened the usual way.
3. Type the same short command in both windows, such as dir.
4. If typing works only in one of them, note which window responds and which does not.
5. If both fail, move on to console-mode and Windows Terminal checks.

Administrator mode is a comparison point, not a universal fix. If the keyboard does not reach either window, privileges are not the main issue.

Does switching to legacy console mode fix CMD input problems?

Legacy Console mode can help when current console behavior is the problem. It is not a cure for a broken keyboard, but it can restore typing in some CMD sessions. This setting lives in CMD Properties > Options, and check it if CMD opens through a modern console host.

1. Open Command Prompt.
2. Right-click the title bar and open Properties.
3. Open the Options tab.
4. Enable Use legacy console if it is available.
5. Apply the change, close CMD, and open it again.
6. Retest typing in the new session.

Could Windows Terminal settings cause Command Prompt not to accept typing? Yes. If CMD opens through Windows Terminal and typing fails there, review Terminal settings as well as the CMD Properties path. A mismatch in the host can look like a keyboard problem even when the keyboard itself is fine.

How do I use the on-screen keyboard in Command Prompt?

The On-Screen Keyboard, or osk, is the fastest fallback when the physical keyboard will not type. It does not fix the cause, but it lets you keep working while you separate a keyboard fault from a Windows input issue. You can start it from the Ease of Access Center.

1. Open Ease of Access Center.
2. Start On-Screen Keyboard.
3. Return to Command Prompt and click inside the window.
4. Use the on-screen keys to enter a short command.
5. If osk works and the physical keyboard does not, focus on the keyboard connection or driver path next.

If paste works but typing does not, osk is especially useful. That split points away from CMD itself and toward the physical input path.

How do I isolate Safe Mode interference?

Safe Mode helps separate Windows itself from third-party interference. If CMD accepts typing in Safe Mode but not in normal mode, the problem is likely tied to startup software, a shell extension, or another background component. On the Startup Settings screen, choose 4 or press F4 for Safe Mode.

1. Restart Windows and open Startup Settings.
2. Choose 4 or press F4 for Safe Mode.
3. After Windows loads, open Command Prompt again.
4. Test typing in CMD.
5. If it works in Safe Mode, restart normally and compare what changes after startup apps load.

If CMD still fails in Safe Mode, third-party startup software is less likely. That pushes the problem toward Windows input corruption, account damage, or a host setting.

What to do if Windows is the cause

If the failure follows one Windows account, the user profile may be damaged. If it follows the whole system, the issue is wider. Test with a different user profile first. If that account works, the original profile needs repair or replacement. If no account works, move to Windows updates or system repair.

1. Sign out and sign in to a different local or Microsoft account.
2. Open Command Prompt in that account and test typing again.
3. Install pending Windows updates through Settings > Windows Update.
4. If the symptom stays with one account, create a new profile and move your files.
5. If the symptom stays with the system, use a supported Windows repair path before deeper changes.

Keep a second local admin account ready for troubleshooting. That gives you a clean comparison point when one profile stops accepting input.

Still not working?

If none of the checks changes the symptom, stop guessing and move to account repair or system repair. At that point, the useful distinction is whether the problem follows the keyboard, the account, or the whole Windows install. If it follows the whole system and affects Safe Mode too, a supported repair install or vendor support is the next step.

1. Test another keyboard if one is available.
2. Test another Windows account.
3. Test CMD in Safe Mode with 4 or F4.
4. Check CMD Properties > Options for legacy console behavior.
5. If all of those fail, use Windows repair tools or contact your device vendor for support.

Frequently asked questions

Why does Command Prompt open but not let me type?

That usually means the window is open but input is not reaching it. Check focus first by clicking inside the CMD window, then test the keyboard in another app. If typing works elsewhere, the problem is more likely a console setting, host issue, or Windows input layer than a dead keyboard.

How do I type in Command Prompt if nothing happens?

Use the On-Screen Keyboard from Ease of Access Center, then click inside CMD and enter a short command like dir. If that works, the physical keyboard path is the part to inspect. If even osk fails, the issue is more likely with the CMD session or Windows input handling.

Can’t get to command prompt, what should I check first?

Use Start search for Command Prompt, or press Win + R, type cmd, and press Enter. If the window opens but input still fails, click inside it once. If you need admin access, right-click the result and choose Run as administrator.

Why won’t my keyboard work in Command Prompt but works everywhere else?

That pattern usually points to CMD focus, the console host, or a Windows input setting rather than the keyboard itself. Try a fresh CMD launch from Start search, then from Run with cmd, and compare the result. If Safe Mode works, the normal startup environment is the likely trigger.