Batch file suppress output

Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Suppress error notification in batch file? Ask Question. Asked 5 years, 11 months ago.

Active 3 years, 8 months ago. Viewed 10k times. I am using Windows Improve this question. When Windows was created, it started life as a fairly thin application switching layer on top of the MSDOS kernel, and thus had the same file name restrictions.

However, the idea that new devices would always get names that would block future user of those names for actual files is obviously unreasonable. Windows NT and all versions that follow 2K, XP, 7, and now 8 all follow use the much more elaborate NT Namespace from kernel code and to carefully constructed and highly non-portable user space code.

For a complete description of the rules surrounding legal names of files and devices in Windows, this page at MSDN will be both informative and daunting. The rules are a lot more complicated than they ought to be, and it is actually impossible to answer some simple questions such as "how long is the longest legal fully qualified path name? I will explain it better below:. Kill the task "test.

Redirect stderr to stdout. Then, redirect stdout to nul. Show the pause message Press any key to continue. NOTE: The symbol is hiding the prompt for each command. You can save up to 8 bytes this way. An character is not needed twice in a line. This code is just 40 bytes, despite the one you've posted being 49 bytes! I actually saved 9 bytes. For a cleaner code look above. How are we doing? Please help us improve Stack Overflow. In just 14kb. You missed a tool that has been around for 16 years.

It saved me a 2 minutes popup every 10 minutes :. Charles Nelson 8 months ago. Novabin 1 year ago. Alex Gorky 1 year ago. HAL Author 1 year ago. Mike 11 months ago. Alex 3 years ago. Yasser 3 years ago. Kiran Vadday 3 years ago.

Jeremy 3 years ago. Nagesh 3 years ago. Myself 3 years ago. HAL Author 3 years ago. Jeerapong Putthanbut 3 years ago. Squashman 3 years ago. To illustrate my story there are some examples you can try for yourself. For an overview of redirection and piping, view my original redirection page.

When I say "on screen", I'm actually referring to the "DOS Prompt", "console" or "command window", or whatever other "alias" is used. The output we see in this window may all look alike, but it can actually be the result of 3 different "streams" of text, 3 "processes" that each send their text to thee same window. Standard Output is the stream where all, well, standard output of commands is being sent to.

Standard Error is the stream where many but not all commands send their error messages. And some, not many, commands send their output to the screen bypassing Standard Output and Standard Error, they use the Console. By definition Console isn't a stream.