Switch between Windows Terminal and the legacy console

The new graphical console brings a number of improvements over the classic console host. However, for the foreseeable future, both environments are available. In Windows 11, the new terminal is already set as the default, but you can switch between both as needed. Unfortunately, the coexistence between the two terminals is suffering from some inconsistencies.

Author
Recent Posts

Wolfgang Sommergut

Wolfgang Sommergut has over 20 years of experience in IT journalism. He has also worked as a system administrator and as a tech consultant. Today he runs the German publication WindowsPro.de.

Latest posts by Wolfgang Sommergut (see all)

New Group Policy settings in Windows 11 23H2 - Mon, Nov 20 2023
Windows Server 2025 will support SMB over QUIC in all editions - Fri, Nov 17 2023
Switch between Windows Terminal and the legacy console - Thu, Nov 16 2023

Some of the advantages of Windows Terminal include support for tabs, extensive customization of the appearance, intelligent copy and paste, and flexible key bindings, among others.

In general, most users likely don't mind the overall transition to the modern console that Microsoft has implemented in Windows 11. However, if you do not want Windows Terminal as the default, you can change the preferred terminal application in your settings under Startup.

Options for defining the standard console

The same options can be found in the settings of the old console window on the Terminal tab.

Set the default terminal in the old console host

The default value is set to Let Windows decide on Windows, meaning the console configured as the system default will be used. In Windows 11, this is the new terminal, while older Windows versions prioritize the classic console.

This behavior can be overridden by explicitly selecting a terminal application.

Inconsistent behavior

When launching PowerShell on a freshly installed Windows 11 from the search box, Windows Terminal opens as expected. However, if you select Run as administrator, you will get the old console despite the new terminal being configured as the default.

The same applies if you pin the icon from the search result to the taskbar and want to open a PowerShell session as Admin.

In general, one reason for ignoring Windows Terminal may be that the option Use legacy console is activated in the shortcut for PowerShell or cmd.exe. This refers to the old terminal from before Windows 10.

Activating the legacy console can prevent Windows Terminal from launching

This setting extends to all console programs unless launched within the Windows Terminal. However, the behavior in Windows 11 described above is independent of this legacy option.

Running PowerShell as admin in the terminal

To execute a command-line with elevated privileges in the Windows Terminal, it is advisable to start it from there.

To do this, configure a separate admin profile for PowerShell or other command interpreters (see: Run Windows Terminal as admin). If you use the default profile for this, the terminal prompts the UAC dialog right at startup.

Conclusion

While Windows Terminal is intended to replace the old console host, the latter is retained for compatibility reasons. Microsoft, however, has yet to solve the coexistence of these two environments very well.

Subscribe to 4sysops newsletter!

Although it is possible to designate one of the consoles as the default, this setting applies only when starting PowerShell or cmd.exe via a shortcut as a standard user. Sessions with elevated privileges always activate the old console host unless initiated directly within the Windows Terminal.