title title

Создает заголовок для окна командной строки. Creates a title for the Command Prompt window.

Синтаксис Syntax

Параметры Parameters

Параметр Parameter	Описание Description
Задает текст, отображаемый в качестве заголовка окна командной строки. Specifies the text to appear as the title of the Command Prompt window.
/? /?	Отображение справки в командной строке. Displays help at the command prompt.

Комментарии Remarks

Чтобы создать заголовок окна для пакетных программ, включите команду Title в начало пакетной программы. To create window title for batch programs, include the title command at the beginning of a batch program.

После установки заголовка окна его можно сбросить только с помощью команды Title . After a window title is set, you can reset it only by using the title command.

Примеры Examples

Чтобы изменить заголовок окна командной строки для обновления файлов во время выполнения пакетным файлом команды копирования , а затем для возвращения заголовка в командную строку, введите следующий скрипт: To change the Command Prompt window title to Updating Files while the batch file executes the copy command, and then to return the title back to Command Prompt, type the following script:

Windows commands

All supported versions of Windows (server and client) have a set of Win32 console commands built in.

This set of documentation describes the Windows Commands you can use to automate tasks by using scripts or scripting tools.

Prerequisites

The information that is contained in this topic applies to:

• Windows Server 2019
• Windows Server (Semi-Annual Channel)
• Windows Server 2016
• Windows Server 2012 R2
• Windows Server 2012
• Windows Server 2008 R2
• Windows Server 2008
• Windows 10
• Windows 8.1

Command shell overview

The Command shell was the first shell built into Windows to automate routine tasks, like user account management or nightly backups, with batch (.bat) files. With Windows Script Host you could run more sophisticated scripts in the Command shell. For more information, see cscript or wscript. You can perform operations more efficiently by using scripts than you can by using the user interface. Scripts accept all Commands that are available at the command line.

Windows has two command shells: The Command shell and PowerShell. Each shell is a software program that provides direct communication between you and the operating system or application, providing an environment to automate IT operations.

PowerShell was designed to extend the capabilities of the Command shell to run PowerShell commands called cmdlets. Cmdlets are similar to Windows Commands but provide a more extensible scripting language. You can run Windows Commands and PowerShell cmdlets in Powershell, but the Command shell can only run Windows Commands and not PowerShell cmdlets.

For the most robust, up-to-date Windows automation, we recommend using PowerShell instead of Windows Commands or Windows Script Host for Windows automation.

You can also download and install PowerShell Core, the open source version of PowerShell.

Incorrectly editing the registry may severely damage your system. Before making the following changes to the registry, you should back up any valued data on the computer.

To enable or disable file and directory name completion in the Command shell on a computer or user logon session, run regedit.exe and set the following reg_DWOrd value:

To set the reg_DWOrd value, use the hexadecimal value of a control character for a particular function (for example, 0 9 is Tab and 0 08 is Backspace). User-specified settings take precedence over computer settings, and command-line options take precedence over registry settings.

Command-line reference A-Z

To find information about a specific command, in the following A-Z menu, click the letter that the command starts with, and then click the command name.

Changing CMD’s Window Title

May 2, 2006

Changing CMD’s Window Title

When running command line tools, applications or batch files it is often necessary to watch the resultant command window. E.g. to detect their completion you can have the script wait until the command window has closed. The trouble with this is that when you run batch files the title of the command window is always just “C:\WINDOWS\system32\cmd.exe”. So if your script starts more than one batch file, or you have other CMD windows open, how do you know which CMD window is which?

Well how about predefining the window title of the new CMD window? We can do this with the Windows start command. The start command starts a new CMD window and lets you give it any title you want and run a program/command at the same time. For more info type start /? at the command prompt. So we can use this in Macro Scheduler with the Run Program command:

This enables us to monitor this specific window to see when the batch file completes:

Now you might be wondering why we’d want to do the above when you can just make the script wait for the program or command run to finish by setting RP_WAIT to 1, like this:

Well, you may need to manipulate the window at some point during the process. Or you might want the script to detect if the batch file is taking too long to complete, like this:

Using the start command like this to set the CMD window’s title makes it much easier to distinguish between other command windows and ensure we manipulate the one belonging to our batch file.

How Can I Close a Command Window with a Specific Title?

November 30th, 2005

Hey, Scripting Guy! How can I use WSH to close a command window with a specific title?

Hey, MF. You know, some things are just really hard to believe, regardless of whether or not they happen to be true. For example, according to the Big Bang Theory the entire universe was created when a miniscule spec of super-dense matter exploded several billion years ago. That’s crazy, but physicists insist it’s true. The University of Washington football team has won only 3 games in the past 2 years? That’s even crazier . But, as Casey Stengal said, you can look it up.

Editor’s Note . Want to hear something really crazy? Today is the one-year anniversary of the Scripting Guys Editor joining the team. If you knew the history of the Scripting Guys and editors, you’d know how incredible it is that one has survived a whole year. Actually, from what you do know of the Scripting Guys, you’re probably wondering how anybody could work with them a whole year. I know this particular editor is wondering….

Or how about this one: you can’t use WSH (or WMI, for that matter) to close a command window with a specific title. WMI enables you to close command windows (or, more correctly, it enables you to terminate processes running under Cmd.exe) but WMI has no knowledge of command window titles. If all you have to go on is the command window title WMI becomes an all-or-nothing proposition: you can either close all the command windows (that is, all processes running under Cmd.exe) or you can close none of the command windows. But you can’t close a specific command window, at least not based on window title alone.

Of course, there’s one thing that is easy to believe: any time the Scripting Guys tell you that something can’t be done the odds are they’ll come up with some crazy workaround that lets you do the task anyway. This is no exception. Maybe you can’t use WSH to close a command window with a specific title; however, you can use Microsoft Word to close a command window with a specific title.

Believe it or not.

For example, here’s a script that closes a command window with the title My Window :

As you can see, the script begins by creating an instance of the Word.Application object. (See? We told you you could use Microsoft Word to carry out this task!) We then use this line of code to return a collection of all the tasks (processes) running on a computer:

Note . You might have noticed that, unlike most of the Word scripts we use, we never set the Visible property to True in this script. Why not? Well, setting the Visible property to True causes Word to appear onscreen. In this case we don’t want – or need – Word to show up onscreen; we just need it to close a command window for us. So we keep it hidden.

So what’s the difference between the Tasks collection in Word and the set of processes returned by WMI’s Win32_Process class? The primary difference is that Word returns the “friendly name” for each process. WMI returns the name of the executable file, so you get back information like this:

With Word, though, you get back information that looks like this:

Generally speaking, the task name returned by Word will be the name that appears in the title bar of the application window. (That obviously won’t be true for processes that run in hidden windows, but we won’t worry about those today.) As you can see, our command window is returned as My Window and not as the generic Cmd.exe. What does that mean? That means Word – unlike WSH and WMI – can locate specific command windows by title.

Furthermore, Word can also close those command windows. After returning the collection of tasks running on the computer we use the Exists method to determine whether or not there is a process (or task) named My Window. If there is, we call the Close method and terminate that process. That takes just three lines of code:

All we have to do then is use the Quit method to terminate our invisible instance of Word and we’re done.

Yes, we know it’s hard to believe (though less hard than believing that Shrek would turn out to be one of the most popular movies of all time). But it’s all true. For more information about the Tasks collection in Word (and what you can do with) take a look at the article Build Your Own Task Manager Using Microsoft Word (No, Really) .

And, sadly, it is true: the Husky football team has only won 3 games in the past two years. But the basketball team is already 6-0 this season. Go Dawgs!

Tutorial: Configure tab titles in Windows Terminal

By default, the tab title is set to the shell’s title. If a tab is composed of multiple panes, the tab’s title is set to that of the currently focused pane. If you want to customize what is set as the tab title, follow this tutorial.

In this tutorial, you learn how to:

• Use the tabTitle setting
• Set the shell’s title
• Using the suppressApplicationTitle setting

Use the tabTitle setting

The tabTitle setting allows you to define the starting title for a new instance of a shell. If it is not set, the profile name is used instead. Each shell responds to this setting differently.

Shell	Behavior
PowerShell	The title is set.
Command Prompt	The title is set. If a command is running, it is temporarily appended to the end of the title.
Ubuntu	The title is ignored, and instead set to user@machine:path
Debian	The title is set.

Though Ubuntu and Debian both run bash, they have different behaviors. This is to show that different distributions may have different behaviors.

Set the shell’s title

A shell has full control over its own title. However, each shell sets its title differently.

Shell	Command
PowerShell	$Host.UI.RawUI.WindowTitle = «New Title»
Command Prompt	TITLE «New Title»
bash*	echo -ne «\033]0;New Title\a»

Note that some Linux distributions (e.g. Ubuntu) set their title automatically as you interact with the shell. If the above command doesn’t work, run the following command:

This will change the title to ‘New Title’.

For easier access add this to the end of your

After you reopen your shell, you now can change the shell’s title at any time using the following command:

Use the suppressApplicationTitle setting

Since a shell has control over its title, it may choose to overwrite the tab title at any time. For example, the posh-git module for PowerShell adds information about your Git repository to the title.

Windows Terminal allows you to suppress changes to the title by setting suppressApplicationTitle to true in your profile. This makes new instances of the profile set your visible title to tabTitle . If tabTitle is not set, the visible title is set to the profile’s name .

Note that this decouples the shell’s title from the visible title presented on the tab. If you read the shell’s variable where the title is set, it may differ from the tab’s title.