Problem using start to launch admin command prompt via TCC toolbar button

[Richard Kaye]

This one has been bugging me for years and thought I'd finally ask what I'm doing wrong. I've created a button like this.

I click the button and I get this.

I'm sure I'm doing something dumb with PATHing or maybe COMSPEC, etc. because I can type that directly into a TCC prompt. Any ideas?

TIA

 

[Fross]

The COMMAND needs to include a command (cmd presumably). So command should be cmd /elevated......

 

[Alpengreis]

Or TCC presumably, like that:

tcc.exe start /elevated /pgm "c:\windows\system32\cmd.exe"

 

[vefatica]

@Richard Kaye, have you (or anyone) ever done this successfully? I don't think it's possible for an unelevated TCMD to host an elevated app in a tab.

Forgetting about the toolbar button for a moment, if, in an enelevated TCC running in an unelevated TCMD, you issue start /tab /elevated cmd, you get an elevated CMD, not in a tab and completely unseen.

 

[Richard Kaye]

Thanks all for the replies.

Since start is an internal command of TCC, the winner is Alpengreis!

Just for background, on occasion I need a regular admin command prompt and want to invoke from Take Command. I'm not trying to get it to surface as a tab inside the TC container.

 

[AnrDaemon]

tcc /c start "" /elevated "x:\path\someprogram"

 

[ohenryx]

In Windows Terminal, this (in the settings file) will do the job. Note that the guid needs to be unique.

{
"commandline": "%SystemRoot%\\System32\\cmd.exe",
"elevate": true,
"guid": "{0caa0dad-35ce-5f56-a8ff-afceeeaa6101}",
"hidden": false,
"name": "CMD Admin"
},

 

[AnrDaemon]

Good idea with wt.