Published by


Brink's Avatar
Administrator

Posts: 25,184

Show Printable Version 


Enable or Disable Legacy Console for Command Prompt and PowerShell in Windows 10

information   Information
The console host (conhost.exe) for the command prompt and PowerShell has been updated with new features in Windows 10.

Windows Console new features include:

Enable Ctrl key shortcuts
Allows new Ctrl key shortcuts for consoles, but may interfere with some applications.

Filter clipboard contents on paste
When you paste text into a console, unsupported characters will either be converted or stripped out, remove tabs, and convert smart quotes to regular quotes.

Enable line wrapping selection
When you select and copy lines of text in a console, it will include wrapping lines instead of being rectangular.

Extended text selection keys
Enable enhanced keyboard editing on command line. For example, you can use Shift and the arrow keys to select characters or lines of text or Ctrl+A to select all the text on the command line or all the text in the window.

Wrap text output on resize
When resizing a console window, wrap text to fit width.

Transparency (opacity)
You can set the transparency level of a console window by setting an opacity value between 30-100%.



This tutorial will show you how to enable or disable using legacy console for all command prompt and PowerShell windows for your account in Windows 10.

CONTENTS:
  • Option One: Enable or Disable Legacy Console for Command Prompt and PowerShell in Properties
  • Option Two: Enable or Disable Legacy Console for Command Prompt and PowerShell using REG file


EXAMPLE: Features disabled when you use legacy console
Name:  Use_legacy_console-1.png
Views: 285
Size:  26.2 KB Name:  Use_legacy_console-2.png
Views: 288
Size:  19.6 KB Name:  Use_legacy_console-3.png
Views: 284
Size:  24.9 KB






Enable or Disable Legacy Console for CMD and PowerShell in Windows 10 OPTION ONE Enable or Disable Legacy Console for CMD and PowerShell in Windows 10
Enable or Disable Legacy Console for Command Prompt and PowerShell in Properties

1. Open a command prompt or PowerShell console window.
Note   Note
You could also just directly right click on the command prompt or Powershell shortcut or file, click/tap on Properties, and go to step 3 below.

2. Right click or press and hold on the title bar of the command prompt or PowerShell, and click/tap on Properties. (see screenshots below)

Name:  command_prompt_legacy_mode-1.png
Views: 285
Size:  20.3 KB Name:  PowerShell_legacy_mode-1.png
Views: 283
Size:  20.8 KB

3. Click/tap on the Options tab, check or uncheck (default) the Use legacy console box for what you want, and click/tap on OK to apply. (see screenshots below)

Name:  command_prompt_legacy_mode-2.png
Views: 281
Size:  27.8 KB Name:  command_prompt_legacy_mode-3.png
Views: 281
Size:  33.4 KB

4. Close and reopen the command prompt or PowerShell to apply.






Enable or Disable Legacy Console for CMD and PowerShell in Windows 10 OPTION TWO Enable or Disable Legacy Console for CMD and PowerShell in Windows 10
Enable or Disable Legacy Console for Command Prompt and PowerShell using REG file

Note   Note
The .reg files below will modify the DWORD value in the registry key below.

HKEY_CURRENT_USER\Console

ForceV2 DWORD

0 = Use legacy console (enable)
1 = Don't use legacy console (disable)


1. Do step 2 (enable) or step 3 (disable) below for what you would like to do.


 2. To Enable Use Legacy Console

A) Click/tap on the Download button below to download the file below, and go to step 4 below.

Use_legacy_console.reg

download


 3. To Disable Use Legacy Console

NOTE: This is the default setting.

A) Click/tap on the Download button below to download the file below, and go to step 4 below.

Do_not_use_legacy_console.reg

download

4. Save the .reg file to your desktop.

5. Double click/tap on the downloaded .reg file to merge it.

6. When prompted, click/tap on Run, Yes (UAC), Yes, and OK to approve the merge.

7. Close and reopen any command prompt and PowerShell console windows to apply.

8. If you like, you can now delete the downloaded .reg file.


That's it,
Shawn