Microsoft has made some improvements to the Windows Console Host over the years. If you’ve ever tried copying a block of text from the command line and pasting it into another window, then you know what I’m talking about. It’s also the mechanism that lets you change the font size or copy and paste in a command line environment.Įven though the Windows Console Host gets the job done, it’s dated and leaves much to be desired in a modern computing environment. The Windows Console Host is tied to a process called ConHost and is what allows the command prompt environments to run inside a window. This is the backend mechanism that both PowerShell and the Windows Command Prompt leverage. This similarity stems from the Windows Console Host. The command line and PowerShell side by side! Even though the two command line environments support different commands, the interfaces look and behave very similarly.

If you’ve ever worked with the Windows Command Prompt Window or with PowerShell, you might have noticed the similarities between the two environments. In this article, I’ll explain why Microsoft is changing the Windows command line environment and what you can expect from this change.įirst, let’s look at why Microsoft is implementing a new command line environment! Why Is Microsoft Changing the Command Line Environment? Although this move might initially seem counterintuitive, it’ll likely make your life easier in the long run.

Several months ago, Microsoft announced that it would be replacing the default command line experience with Windows Terminal for Windows 11 users. Why is Microsoft replacing the default Windows command line?

Windows terminal command