How to stop Windows 11 reselecting its "Windows terminal" for TCC?

[mfarah]

I am so used to the Windows Console host that I don't like the look (and "extra features") of Windows Terminal "hosting" my TCC windows. Simple fix, right? Set this up in Windows 11's settings:

And forget about the new and "improved" terminal. However... I've noticed that if I change any of TCC's properties:

Windows 11 sets back the "Terminal" option to "Let Windows Decide":

... and any subsequent TCC windows are started under Terminal. To add insult to injury, Windows Terminal doesn't even list TCC as a command line prompt option.

So, how to beat back Windows 11 to submission in this regard?

 

[Charles Dye]

.... To add insult to injury, Windows Terminal doesn't even list TCC as a command line prompt option.

View attachment 4719

So, how to beat back Windows 11 to submission in this regard?

You can create new profiles in Windows Terminal. Go into Settings, then scroll down the left pane all the way to the bottom; select "Add a new profile". Make a copy of "Command Prompt", rename it to TCC or whatever, then change it to point to TCC.EXE instead. Once you've got your new profile the way you want it, you can make it the default.

Regarding your main issue: I've never seen that. But I've never used System / For developers — never even knew it was there. I use Settings within Windows Terminal. Does that one work for you?

 

[mfarah]

You can create new profiles in Windows Terminal. Go into Settings, then scroll down the left pane all the way to the bottom; select "Add a new profile". Make a copy of "Command Prompt", rename it to TCC or whatever, then change it to point to TCC.EXE instead. Once you've got your new profile the way you want it, you can make it the default.

I did this and it worked without fuss (although I hate the way Windows Terminal uses thick borders and wastes precious screen space for no reason). This does beg the question: should the TCMD installer include an option to create a Windows terminal profile for TCC?

FUN FACT: I first mistakenly pointed to TCMD.EXE instead of TCC.EXE and set it to the default profile, too. When starting Terminal, it'd start TCMD, which would go on its own window and Terminal would exit. Took me a while to start Terminal without the default profile so I could fix that.

Regarding your main issue: I've never seen that. But I've never used System / For developers — never even knew it was there. I use Settings within Windows Terminal. Does that one work for you?

I configured both the System preferences and the Terminal Startup preferences to opt for the Windows Console Host. If I change the properties on TCC, it still reverts to "Let Windows decide" on both. Changing it again to "Windows Console Host" on the System preferences immediately changed the Terminal Startup preference, so it's clear it's the same registry value or whatever for both.

My money is on a Windows 11 naabug (looks like a bug, but it's "not actually a bug") that MS introduced or has turned a blind eye to, because they are heavily shilling their Windows Terminal.

 

[Charles Dye]

Well, it's Microsoft's computer. You are just tolerated as a guest.

 

[mfarah]

Well, it's Microsoft's computer. You are just tolerated as a guest.

Joke's on them: it's a NZXT rental.

(no, no way I'd pull that shenanigan on my wallet!)