Support for UAC

[GoogleCodeExporter]

What steps will reproduce the problem?
Ctrl+M produces only a non-elevated cmd prompt.

What is the expected output? What do you see instead?
A non-elevated cmd prompt isn't useful to run most commands under Windows 7. 
Holding down Shift and pressing the cmd button (or Shift+Ctrl+M/Shift+assigned 
shortcut) should produce an elevated cmd prompt.

What version of the product are you using? On what operating system?
Windows 7 32-bit.

Please provide any additional information below.
Can you add this feature please? :) Elevated cmd prompt is critical to use of 
this feature.

Original issue reported on code.google.com by xpclient...@gmail.com on 11 Jul 2010 at 8:09

[GoogleCodeExporter]

Original comment by tortoisesvn on 11 Jul 2010 at 5:25

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This won't be easy:
* we have to use ShellExecute(Ex) instead of CreateProcess to start the new app
* elevated processes don't inherit the environment of the parent process. That 
means cmd.exe will always start in c:\windows\system32 instead of the directory 
currently active in explorer.
* we have to find a way to make the new cmd process use the current directory 
of the parent process

Also, using shift as the 'elevate key' isn't good: many people including me 
already use the shift key as part of the hotkey for existing commands.
But instead, using the Window key should be fine.

Original comment by tortoisesvn on 30 Jul 2010 at 5:38

• Changed state: Started
• Added labels: Milestone-1.8.1

[GoogleCodeExporter]

This issue was closed by revision r278.

Original comment by tortoisesvn on 30 Jul 2010 at 6:19

• Changed state: Fixed

[GoogleCodeExporter]

The problem with the Window key is when holding it down and clicking the 
Console button with the mouse, the Start menu pops up after you leave the 
window key. Maybe Ctrl+Shift+<configurable hotkey>? As the Start menu also uses 
Ctrl+Shift to launch anything as admin.

Original comment by xpclient...@gmail.com on 3 Aug 2010 at 8:09

[GoogleCodeExporter]

No, the start menu won't popup if you have UAC enabled: the UAC desktop will 
prevent the start menu from popping up.

Original comment by tortoisesvn on 3 Aug 2010 at 4:51

[GoogleCodeExporter]

It is popping up as I have UAC turned on to highest level (1 notch up from 
default in Windows 7) but kept secure desktop off. I don't think it should rely 
on the secure desktop to prevent the menu from popping. :)

Original comment by xpclient...@gmail.com on 3 Aug 2010 at 7:40

[GoogleCodeExporter]

highest level but secure desktop is off?
That's like paying 5000$ for the best breaks, and then using the handbrake 
instead.

Original comment by tortoisesvn on 3 Aug 2010 at 7:45

[GoogleCodeExporter]

With that setting, it will continue to block silent/hidden attacks but even if 
malware does automate the UAC dialog, it won't be silent. I will come to know. 
Anyways, how does it matter if it's at level 3 or 4? Do you not support the Win 
hotkey in a non-secure desktop scenario? :)

Original comment by xpclient...@gmail.com on 3 Aug 2010 at 8:01

[GoogleCodeExporter]

As I mentioned before, using Ctrl and/or shift isn't an option since those keys 
are already used for normal hotkeys. The only key that's left is the window key.
And even if that brings up the start menu, the command is still executed 
elevated, so it works.
IMHO it's a minor 'annoyance' if the start menu comes up, not really worth 
breaking existing hotkeys for.

Original comment by tortoisesvn on 3 Aug 2010 at 8:14

[GoogleCodeExporter]

But for Win key, won't StExBar have to install a keyboard filter hook? Also, 
the Windows Start menu itself uses Ctrl+Shift combo for admin launching when 
it's open. Surely, Microsoft would have thought out conflicts with other apps 
before they used that key combination? Just using Ctrl or Shift would conflict 
I agree. Even Alt+Shift conflicts but not Ctrl+Shift.

Original comment by xpclient...@gmail.com on 3 Aug 2010 at 8:28