Does Windows 10 support setting Terminal as the default console host?

[ExHix]

I found Default terminal application setting in Windows 11 terminal, but couldn't find it in Windows 10.
I am using latest version of Windows 10. Is it because the system is not compatible to it?

[Pawloland]

I don't know since when but it is finally possible. It works for me on : 22H2 19045.3031.
There are two ways to enable it:
Windows settings > Updates > For Developers > scroll down for Terminal, where you can select one of three: legacy windows console host, windows terminal or let windows decide.
You can also right click on legacy cmd window title bar > preferences > terminal tab > in right corner on the bottom you have drop down with the same 3 options as mentioned before.
Note that the exact names of the consecutive sub menus may differ, because I don't have English language set on my PC and I translated them.
As of WT 1.16.10261.0 there is no way of setting WT as the default terminal in OS from inside of WT settings (as it is possible on win 11).

[DHowett]

As @Pawloland notes, this is finally supported on Windows 10! 🎉

After you install KB5026435, you will be able to access the Default Terminal settings in the console host and Developer settings page.

After you install Windows Terminal v1.17, you will also be able to access the setting inside Terminal. Default terminal is supported in earlier versions, but there is no code in those versions to detect that Windows 10 supports it... so it won't give you the option.

[gweinfurther]

This doesn't work. I changed this setting in both places, but Console Host still comes up as the default in Windows 10.

[zadjii-msft]

Are you running the command line application as an Administrator?

[jaredbrogan]

I'm seeing this as well. PowerShell and CMD will launch in Terminal as expected when in non-admin mode, but will not honor the setting when launching either of those as admin.

[Dragodraki]

Windows Registry Editor Version 5.00

; Use Console Host (for running as this user)
[HKEY_CURRENT_USER\Console%%Startup]
"DelegationConsole"="{B23D10C0-E52E-411E-9D5B-C09FDF709C7D}"
"DelegationTerminal"="{B23D10C0-E52E-411E-9D5B-C09FDF709C7D}"

Windows Registry Editor Version 5.00

; Use Windows Terminal (for running as this user)
[HKEY_CURRENT_USER\Console%%Startup]
"DelegationConsole"="{2EACA947-7F5F-4CFA-BA87-8F7FBEEFBE69}"
"DelegationTerminal"="{E12CFF52-A866-4C77-9A90-F570A7AA2C6B}"

Take note that HKCU ist relative - its a termination for what is current for the process instance. That means elevated instances with the current user not being member of administrators are different from your desktop user. Its only important if you edit the registry manually - I recommend to import this with the same script/program and the same elevation that also invokes your command prompt - that guarantees that the CMD's design match your setting no matter the user account that script/program was launched with.