RunAs PowerShell - Ctrl+C no longer works...
Timothy
sequence no longer works.
An example...
If I run "ping.exe -t" which will ping endlessly, the way you get back to
the command prompt is by pressing CTRL+C. If I run PowerShell under my user
context, this works fine. If I run PowerShell as an admin, it's as if CTRL+C
is ignored. I have to "X" to close the window. This is highly frustrating.
The weird thing is that PowerShell itelf seems to react to CTRL+C because if
I press it at an empty command line, it gives me a new command line, so it is
definitely seeing something being pressed.
Anybody have any clues?
--
Timothy Carroll
MCSA/MCSE: Security
Security+
www.avianwaves.com
Techstarts
Thomas Lee
<preet...@gmail.com> writes
>? irrespective of you use powershell/CMD prompt, if use ping -t option
Not so. Ctrl-C works fine to stop a ping -t.
I can not reproduce the OP's problem. :-(
--
Thomas Lee
doct...@gmail.com
MVP - Admin Frameworks and Security
GodOfLions
matter what account I RunAs, it will not let me use Ctrl+C to stop the
process, i have to use Task Manager to kill the Powershell session itself to
stop it.
GodOfLions
not matter what account I RunAs with Powershell Ctrl+C does not stop the
process. The only way for me to stop the process is to use Task Manager to
Kill PowerShell.
Timothy
it won't stop it either when being RunAs'ed... This must be some weird issue
with just the Windows Console mode itself. Can you try it with CMD and see
if you get the same results?
This is aggrivating.. The windows console has _got to be replaced_!!!
I'm going to try this with Vista tonight. I have that on my laptop at home.
I wonder if the issue persisted through to Vista...
--
Timothy Carroll
MCSA/MCSE: Security
Security+
www.avianwaves.com
klu...@gmail.com
> I'm also running Win XP SP2 here. I just tried it in a standard CMD.EXE and
> it won't stop it either when being RunAs'ed... This must be some weird issue
> with just the Windows Console mode itself. Can you try it with CMD and see
> if you get the same results?
>
> This is aggrivating.. The windows console has _got to be replaced_!!!
>
> I'm going to try this with Vista tonight. I have that on my laptop at home.
> I wonder if the issue persisted through to Vista...
>
> --
> Timothy Carroll
> MCSA/MCSE: Security
> Security+www.avianwaves.com
>
>
>
> "GodOfLions" wrote:
> > FYI: I've had the same problem with using runas and Powershell. It doesn't
> > matter what account I RunAs, it will not let me use Ctrl+C to stop the
> > process, i have to use Task Manager to kill the Powershell session itself to
> > stop it.
>
> > "Thomas Lee" wrote:
>
> > > <preetamz...@gmail.com> writes
> > > >? irrespective of you use powershell/CMD prompt, if use ping -t option
> > > >you've to press x to stop ping, not sure if there is any work around.
>
> > > Not so. Ctrl-C works fine to stop a ping -t.
>
> > > I can not reproduce the OP's problem. :-(
>
> > > --
> > > Thomas Lee
> > > MVP - Admin Frameworks and Security- Hide quoted text -
>
> - Show quoted text -
I can duplicate that this error occurs under the runas scenario in 1)
Powershell.exe 2) plain old cmd.exe and 3) our own console based
host (even with the button that you click to stop the pipeline as well
at CTRL-C) , but not in our GUI based host - Powershell Analyzer . it
seems to be something with the console subsystem.
Has anybody 1) submitted this on connect , or 2) researched it in the
cmd.exe context on google?
-Karl
Thomas Lee
GodOfLions <GodOf...@discussions.microsoft.com> writes
>I'm having the same problem. I'm using an Windows XP SP2 system, and it
>does not matter what account I RunAs with Powershell Ctrl+C does not
>stop the process. The only way for me to stop the process is to use
>Task Manager to Kill PowerShell.
Not sure what I did last time - but I can now reproduce this 'feature'.
Time to file a bug me thinks.
Thomas Lee
writes
>In message <2BBEA17E-3375-4BD9...@microsoft.com>,
>GodOfLions <GodOf...@discussions.microsoft.com> writes
>>I'm having the same problem. I'm using an Windows XP SP2 system, and
>>it does not matter what account I RunAs with Powershell Ctrl+C does
>>not stop the process. The only way for me to stop the process is to
>>use Task Manager to Kill PowerShell.
>
>Not sure what I did last time - but I can now reproduce this 'feature'.
>
>Time to file a bug me thinks.
https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=28307
5&SiteID=99
Feel free to vote.
Al Dunbar
"Thomas Lee" <t...@psp.co.uk> wrote in message
news:$$snF0Ied...@mail.psp.co.uk...
This might not be a powershell issue, per se. I get similar behaviour on XP
SP2 when I run cmd.exe under alternate credentials - even if the alternate
credentials are the same as the ones I use to invoke runas. There are a
number of things that work somewhat differently via runas, for example,
windows explorer needs an explicit refresh when you are viewing a folder in
which a file is created, renamed, or deleted.
/Al