Skip to main content

How to Redirect Standard Error (2>) in a Batch Script

When a command runs in a batch script, it can produce two different kinds of text output. The first is its normal, expected result, called Standard Output (stdout). The second is for warnings, error messages, and failures, called Standard Error (stderr). By default, both of these "streams" are printed to the command prompt window, but they are internally separate.

Being able to control these streams independently is a critical skill for writing clean, robust scripts. This guide will teach you how to specifically manage the Standard Error stream. You will learn how to hide error messages, redirect them to a separate log file, and how to combine them with standard output for comprehensive logging.

What are Standard Output (1) and Standard Error (2)?​

Think of a command having two output channels:

  • Standard Output (stdout): This is for normal, successful output. It is internally referred to as stream 1. The standard redirection operator (>) is actually a shortcut for 1>.
  • Standard Error (stderr): This is for error messages. It is internally referred to as stream 2.

This separation is why you can redirect a DIR command's successful output, but still see an error on the screen.

Example of script in which the error message still appears on the console because we only redirected stream 1.

REM This command will succeed, and its output will go to the file. Nothing appears on screen.
DIR C:\Windows > output.txt

REM This command will FAIL. The > only affects stdout. The stderr is not redirected.
DIR C:\NonExistentFolder > output.txt

Output of the second command:

File Not Found

The Core Syntax: 2> and 2>>​

To control standard error, you must explicitly refer to stream 2.

  • command 2> filename: Redirects stderr to a file, overwriting the file's contents.
  • command 2>> filename: Redirects stderr to a file, appending to the end of the file.

The 2 must be immediately before the > with no space.

Basic Example: Hiding Error Messages (2>NUL)​

The most common use for stderr redirection is to suppress error messages to keep a script's output clean. This is done by redirecting the error stream to the NUL device, which is a virtual "black hole."

This script attempts to delete a file that may not exist. We don't want the user to see a "File Not Found" error if it's missing.

@ECHO OFF
ECHO --- Cleaning Up Temporary Files ---

REM If temp_file.tmp doesn't exist, this would normally print an error.
REM The 2>NUL suppresses that error message.
DEL temp_file.tmp 2>NUL

ECHO Cleanup attempt complete.

This script will now run silently, whether the file existed or not.

Redirecting stderr to a Separate Error Log​

For administrative scripts, you don't want to throw errors away; you want to log them for later review.

For example, this script pings a server. If it succeeds, the output goes to the screen. If it fails, the error message is saved to a log file.

@ECHO OFF
SET "Target=non-existent-server"
SET "ErrorLog=ping_errors.log"

ECHO Pinging %Target%...
PING -n 1 %Target% 2> "%ErrorLog%"

If the ping fails, the console will be clean, but ping_errors.log will contain:

Ping request could not find host non-existent-server. Please check the name and try again.

The Ultimate Combination: Redirecting Both Streams (> ... 2>&1)​

The most powerful technique is to redirect both stdout and stderr to the same file. This creates a single, comprehensive log of everything the command did, in the correct chronological order.

Syntax: command > "logfile.txt" 2>&1

Let's break this down:

  1. > "logfile.txt": This part is executed first. It tells cmd.exe to redirect stdout (stream 1) to logfile.txt.
  2. 2>&1: This is the crucial part. It tells cmd.exe to redirect stderr (stream 2) to the same location as stream 1 (&1). The & is a special symbol that means "the handle of the stream," not the literal number "1".
@ECHO OFF
(
    ECHO Starting process...
    DIR C:\Windows
    ECHO Now trying a command that will fail...
    DIR C:\NonExistentFolder
    ECHO Process finished.
) > "comprehensive_log.txt" 2>&1

The file comprehensive_log.txt will now contain both the success output from the first DIR and the error message from the second DIR, all in one place.

Common Pitfalls and How to Solve Them​

  • Order of Redirection Matters: The command command 2>&1 > "logfile.txt" is NOT the same and will not work as expected. It first redirects stderr to the console (the current location of stdout), and then redirects stdout to the file. The errors will still appear on the screen.

    • Solution: Always use the > "file" 2>&1 order.

  • Forgetting to Redirect Both: If your goal is a silent script, remember that >NUL is not enough. A command can still fail and produce output on stderr.

    • Solution: For a completely silent command, you must redirect both: command >NUL 2>NUL.

Practical Example: A Clean Robocopy Log Script​

This script runs a Robocopy backup and captures every single message (informational, success, and error) into a single, clean log file.

@ECHO OFF
SET "Source=C:\MyData"
SET "Dest=E:\Backups"
SET "LogFile=backup_log.txt"

ECHO --- Starting Backup ---
ECHO See %LogFile% for detailed output.

REM This is the standard, professional way to log a command's full output.
ROBOCOPY "%Source%" "%Dest%" /MIR /R:2 /W:5 > "%LogFile%" 2>&1

IF %ERRORLEVEL% LSS 8 (
    ECHO [SUCCESS] Backup completed.
) ELSE (
    ECHO [FAILURE] Robocopy reported a serious error. Check the log.
)

Conclusion​

Understanding and controlling the standard output and standard error streams is a fundamental skill for writing clean and professional batch scripts.

Key takeaways:

  • Standard Output is stream 1 (>); Standard Error is stream 2 (2>).
  • To silence errors, redirect them to the null device: 2>NUL.
  • To log errors separately, redirect them to a file: 2> "error.log".
  • To create a single, comprehensive log of all output, use the standard idiom: > "all.log" 2>&1.

Table of Contents