start /elevated /inv not invisible
- Thread starter jabelli
- Start date
On Thu, 30 Jun 2011 19:56:17 -0400, jabelli <> wrote:
|Code:
|---------
|> start /elevated /inv notepad
|---------
|Expected result: a notepad I have to kill with ProcExp or taskend because I can't see it
|
|Actual result: I can just click the [X] button because I can see it
Same here, it's not hidden, on XP. But first it shows a dialog (what user ...).
Is that (a dialog) what happens on newer versions of windows?
|Code:
|---------
|> start /elevated /inv notepad
|---------
|Expected result: a notepad I have to kill with ProcExp or taskend because I can't see it
|
|Actual result: I can just click the [X] button because I can see it
Same here, it's not hidden, on XP. But first it shows a dialog (what user ...).
Is that (a dialog) what happens on newer versions of windows?
Not sure why you'd want to do that, but ...
It's Windows, not TCC. TCC sets the hide flag, but Windows ignores it when starting elevated.
On Thu, 30 Jun 2011 22:47:18 -0400, rconn <> wrote:
|---Quote (Originally by jabelli)---
|Code:
|---------
|> start /elevated /inv notepad
|---------
|Expected result: a notepad I have to kill with ProcExp or taskend because I can't see it
|
|Actual result: I can just click the [X] button because I can see it
|---End Quote---
|
|Not sure why you'd want to do that, but ...
|
|It's Windows, not TCC. TCC sets the hide flag, but Windows ignores it when starting elevated.
After starting it elevated, can you hide it with
|---Quote (Originally by jabelli)---
|Code:
|---------
|> start /elevated /inv notepad
|---------
|Expected result: a notepad I have to kill with ProcExp or taskend because I can't see it
|
|Actual result: I can just click the [X] button because I can see it
|---End Quote---
|
|Not sure why you'd want to do that, but ...
|
|It's Windows, not TCC. TCC sets the hide flag, but Windows ignores it when starting elevated.
After starting it elevated, can you hide it with
Code:
ACTIVATE "Untitled - Notepad" hide
Code:
alias sysprompt=`start /elevated /inv psexec -sid "%_cmdspec"`OK. I’ll put that one back to using HSTART. Apparently Windows doesn't do that if the program doing the starting is a Windows program rather than console.