Command Prompt Closes After Running a Command in Windows: How to Fix It

How to Stop Command Prompt from Closing Immediately After a Command

If Command Prompt opens, runs a command, and closes immediately, the command was probably started from Run, a shortcut, a script, or a batch file that ends automatically. The simplest fix is to open cmd.exe first and run the command inside the already-open window.

Why CMD Closes After Running a Command in Windows 10 and Windows 11

This behavior is often normal. A console window closes when the process that opened it finishes. For example, if you double-click a .bat file or run a command through the Run dialog, Windows may create a temporary console window only for that command. When the command ends, the temporary window closes.

Open Command Prompt First, Then Run the Command

This is the safest troubleshooting method because the window remains open and you can see the complete output.

1. Press Win+R.
2. Type cmd and press Enter.
3. Run the command inside the already-open Command Prompt window.
4. Read the output, error message, or exit status before closing the window manually.

For commands that require administrator rights, open Start, type Command Prompt, choose Run as administrator, and then run the command.

Use cmd /k to Keep the Command Prompt Window Open

The cmd command supports switches that control what happens after a command runs. The two most common switches are /c and /k.

Example: this opens Command Prompt, runs ipconfig, and keeps the window open:

Commandcmd /k ipconfig

Example: this runs a command and closes the window when it finishes:

Commandcmd /c ipconfig

Fix a BAT or CMD File That Closes Immediately After Running

If a .bat or .cmd file closes immediately, add pause at the end while testing. This makes the script wait until you press a key.

Batch file example@echo off
ipconfig /all
pause

If the script has several branches, add pause before each possible exit line or before a section where you suspect the script fails.

Debugging example@echo off
echo Starting script...
net use
if errorlevel 1 (
    echo The command failed.
    pause
    exit /b 1
)
echo Done.
pause

Run the batch file from an existing CMD window

Another good method is to open Command Prompt, go to the folder where the batch file is located, and run it manually.

Commandcd /d "C:\Path\To\Folder"
my-script.bat

When launched this way, the script can end, but the parent cmd.exe window usually remains open.

Check Shortcut Targets That Make Command Prompt Close

If CMD closes after opening a desktop shortcut, the shortcut target may be configured to close the console after the command completes.

1. Right-click the shortcut and select Properties.
2. Open the Shortcut tab.
3. Check the Target field.
4. If it contains cmd /c, change it to cmd /k while testing.
5. Click Apply, then run the shortcut again.

For example, change this closing version:

Shortcut target that closesC:\Windows\System32\cmd.exe /c ipconfig

To this version that stays open:

Shortcut target that stays openC:\Windows\System32\cmd.exe /k ipconfig

PowerShell, Python, and Installer Commands Can Also Close Too Fast

The same problem can happen with PowerShell, Windows Terminal, Python, installers, and command-line utilities. If you double-click a script file, Windows may open a console only for that script and close it when the process exits.

For PowerShell scripts, you can also add a temporary read prompt at the end while debugging:

PowerShell debug lineRead-Host "Press Enter to exit"

How to Find the Error Before the CMD Window Disappears

If the window closes before you can read the text, the goal is to capture the output. You can keep the window open, redirect output to a file, or check system logs depending on the command.

Redirect command output to a text file

This saves both normal output and error output to a file on the desktop:

Commandyour-command-here > "%USERPROFILE%\Desktop\cmd-output.txt" 2>&1

Replace your-command-here with the real command. Then open cmd-output.txt on the desktop and read the result.

Show each command in a batch file

If your batch file starts with @echo off, temporarily remove it or change it to echo on. This helps you see which line runs before the script exits.

Batch debug modeecho on
rem Your commands go here
pause

Check common mistakes

• The command path is incorrect or the file no longer exists.
• The command needs administrator rights.
• The script uses exit too early.
• The shortcut uses /c instead of /k.
• A required tool is not installed or is not in the PATH environment variable.
• Quotation marks are missing around a path with spaces.

When CMD Opens and Closes by Itself: Check Startup Tasks and Malware

If Command Prompt opens and closes by itself without you running anything, treat it differently. It may be a scheduled task, a startup entry, a driver utility, a software updater, or unwanted software.

1. Open Task Manager and check the Startup apps list.
2. Open Task Scheduler and review recently added or suspicious tasks.
3. Run a full scan with Windows Security.
4. Check whether a specific application opens CMD during updates or maintenance.
5. If the window appears repeatedly, use Reliability Monitor or Event Viewer to look for related errors at the same time.

Command Prompt Closes After Running a Command: Frequently Asked Questions

Best Fix When Command Prompt Closes Too Quickly

For most cases, the fix is simple: open Command Prompt first and run the command inside it. If you are editing a shortcut, use cmd /k instead of cmd /c. If you are debugging a batch file, add pause near the end or before the line where the script exits.