What Windows "magic" invokes a command window as an Administrator window simply by using Control+Shift+Enter versus Enter?

What Windows "magic" turns a command window into Administrator simply by
using "Control+Shift+Enter" versus "Enter"?

1. This opens an administrator command window:
Start Run cmd Control+Shift+Enter
2. This opens a user-level command window:
Start Run cmd Enger

How does that work?

What Windows "magic" enables that to work so beautifully elegantly?

--
See also Don Kuenz' detection of the elevated prompt window.
https://alt.comp.os.windows-10.narkive.com/JQYSByUO/over-250-start-run-commands-please-improve-this-start-run-commands-list#post10

On Wed, 14 Aug 2019 23:57:01 -0000 (UTC), Arlen George Holder wrote:
What Windows "magic" turns a command window into Administrator simply by
using "Control+Shift+Enter" versus "Enter"?

1. This opens an administrator command window:
Start Run cmd Control+Shift+Enter
2. This opens a user-level command window:
Start Run cmd Enger

How does that work?

What Windows "magic" enables that to work so beautifully elegantly?

Nice magic, but there's no such magic in Windows 7. It only exist in Windows
10.

In alt.comp.os.windows-10 Arlen George Holder wr
ote:
What Windows "magic" turns a command window into Administrator simply by
using "Control+Shift+Enter" versus "Enter"?

1. This opens an administrator command window:
Start Run cmd Control+Shift+Enter
2. This opens a user-level command window:
Start Run cmd Enger

How does that work?

What Windows "magic" enables that to work so beautifully elegantly?

The process access rights are probably set to PROCESS_ALL_ACCESS when
the Run dialog calls CreateProcess.

https://docs.microsoft.com/en-us/win...-access-rights

Thank you, 73,

--
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.

On 8/15/2019 8:25 AM, JJ wrote:
On Wed, 14 Aug 2019 23:57:01 -0000 (UTC), Arlen George Holder wrote:
What Windows "magic" turns a command window into Administrator simply by
using "Control+Shift+Enter" versus "Enter"?

1. This opens an administrator command window:
Start Run cmd Control+Shift+Enter
2. This opens a user-level command window:
Start Run cmd Enger

How does that work?

What Windows "magic" enables that to work so beautifully elegantly?

Nice magic, but there's no such magic in Windows 7. It only exist in Windows
10.


Windows 7 SP1 Ultimate (x64)

When I hold Ctrl-Alt and select Run, the dialogue contains the following
under the input area:
"This task will be created with administrative privileges."

--
David E. Ross
http://www.rossde.com/

The headline reads:
"Trump urges 'common sense' gun measures, seeks NRA input"

Tell me, Mr. Fox, how many hens do you want in the hen house
we are asking you to guard?

"JJ" wrote in message .. .

On Wed, 14 Aug 2019 23:57:01 -0000 (UTC), Arlen George Holder wrote:
What Windows "magic" turns a command window into Administrator simply by
using "Control+Shift+Enter" versus "Enter"?

1. This opens an administrator command window:
Start Run cmd Control+Shift+Enter
2. This opens a user-level command window:
Start Run cmd Enger

How does that work?

What Windows "magic" enables that to work so beautifully elegantly?

Nice magic, but there's no such magic in Windows 7. It only exist in
Windows
10.

Works for me in Windows 7 SP1 32-bit.
--

On Thu, 15 Aug 2019 09:45:08 -0700, David E. Ross wrote:

Windows 7 SP1 Ultimate (x64)

When I hold Ctrl-Alt and select Run, the dialogue contains the following
under the input area:
"This task will be created with administrative privileges."

That's same as my system. Looks like it's only available after certain
hotfix, considering that I don't allow automatic updates (I only have some
installed manually), including for Win8, Win8.1, and Win10 in my VMs. All
those OSes in the VMs, only Win10 has such feature.

On Sat, 17 Aug 2019 00:38:31 +0700, JJ wrote:

All
those OSes in the VMs, only Win10 has such feature.

Does anyone know what "magic" enables this wonderful feature?
I read that process doc but I still don't understand how it works.

On Thu, 15 Aug 2019 16:36:51 -0000 (UTC), Don Kuenz, KB7RPU wrote:

The process access rights are probably set to PROCESS_ALL_ACCESS when
the Run dialog calls CreateProcess.

https://docs.microsoft.com/en-us/win...-access-rights

Hi Don Kuenz,

Maybe that reference explains the "magic", but I didn't get anything from
that which was useful in explaining HOW this "magic" works.

BTW, it works the same with both "cmd" and "powershell" for me anyway...
o Over 250 Start Run commands (please improve this Start Run commands list)
https://groups.google.com/forum/#!topic/microsoft.public.windowsxp.general/cc1lGn3ty0E

From that useful reference, are these two sets of magical commands:

Start Run cmd Enter (opens a user-level command prompt)
Start Run cmd Ctrl+Shift+Enter (opens an admin-level command prompt)

Start Run powershell Enter (opens a user-level powershell)
Start Run powershell Ctrl+Shift+Enter (opens an admin-level powershell)

What is the Windows 'magic' that makes this work so beautifully?

Arlen George Holder wrote:
On Thu, 15 Aug 2019 16:36:51 -0000 (UTC), Don Kuenz, KB7RPU wrote:

The process access rights are probably set to PROCESS_ALL_ACCESS when
the Run dialog calls CreateProcess.

https://docs.microsoft.com/en-us/win...-access-rights

Hi Don Kuenz,

Maybe that reference explains the "magic", but I didn't get anything from
that which was useful in explaining HOW this "magic" works.

BTW, it works the same with both "cmd" and "powershell" for me anyway...
o Over 250 Start Run commands (please improve this Start Run commands list)
https://groups.google.com/forum/#!topic/microsoft.public.windowsxp.general/cc1lGn3ty0E

From that useful reference, are these two sets of magical commands:

Start Run cmd Enter (opens a user-level command prompt)
Start Run cmd Ctrl+Shift+Enter (opens an admin-level command prompt)

Start Run powershell Enter (opens a user-level powershell)
Start Run powershell Ctrl+Shift+Enter (opens an admin-level powershell)

What is the Windows 'magic' that makes this work so beautifully?


Special powder made from pulverized unicorn horns.

The 'magic' is simply the code some programmer put in while developing
the shell, same as WinKey+R opens the run dialog.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Sat, 17 Aug 2019 17:00:25 -0000 (UTC), Arlen George Holder wrote:

And killed & restarted C:\Windows\explorer.exe and then found that "Run"
was "Run.lnk" (so it's a 'normal' shortcut, at least based on the naming.

But even so, I couldn't find out where this "Run.lnk" shortcut goes.
https://i.postimg.cc/JhwzLhY0/run02.jpg

BTW, killing explorer.exe outside the task manager is easy:
C:\Windows\System32\taskkill.exe /im "explorer.exe" /t /f

But starting it back up _required_ the Task Manager:
Three-finger salute Task Manager File Run new task explorer.exe

It's interesting to note that the WinKey+R was disabled when "explorer.exe"
wasn't running.

Is there another way of bringing up the Run box when explorer.exe is dead?

On Sat, 17 Aug 2019 17:00:25 -0000 (UTC), Arlen George Holder wrote:

It's _embarrassing_ that none of us know how Windows works

Proprietary closed source is like drugs. Just say no.

Arlen George Holder wrote:
Hi Jonathan,

It's _embarrassing_ that none of us know how Windows works, least of all
me.

That's the nature of proprietary software. The alternative is open
source. This is why this is my only and last Winbox. All others I have a
Linux.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

In alt.comp.os.windows-10 T. Ment wrote:
On Sat, 17 Aug 2019 17:00:25 -0000 (UTC), Arlen George Holder wrote:

It's _embarrassing_ that none of us know how Windows works

"If you could see your way, sir, to confining your remarks to your own
peculiarities, you would find that you had an ample field for comment."

Proprietary closed source is like drugs. Just say no.

As a BSD aficionado, Jonathan and your sympathies are certainly shared
by me. Be that as it may, it's far too late for the likes of us. The
Windows pandemic took hold decades ago.


Windows provides several ways to invoke its Run Dialog. Here's how the
Task Manager ultimately spawned a new process back in the day:

/* Try to exec 'szCommandLine'. */

/*changed order, since wPendINstance is a 32b HANDLE, and ret is WORD*/
if (!lpP)
lpP = TEXT("");

wsprintf(lpReserved, lpReservedFormat, 0, 0);

ret = (WORD)RealShellExecute(ghwndDialog, NULL, lpszPath, lpP,
lpDir, NULL, lpTitle, lpReserved,
(WORD)SW_SHOWNORMAL, &hProcess);

RealShellExecute is most likely a wrapper for the API CreateProcess
function shown below. (It's too much work for me to investigate this any
further for curiosity's sake.)
Inet searches indicate that some people seem to get some mileage out
of calling CreateProcess from within PowerShell. C's my native language
so don't ask me how to do this in PowerShell.

CreateProcess

The CreateProcess function creates a new process and its
primary thread. The new process runs the specified executable
file in the security context of the calling process.

If the calling process is impersonating another user, the new
process uses the token for the calling process, not the
impersonation token. To run the new process in the security
context of the user represented by the impersonation token,
use the CreateProcessAsUser or CreateProcessWithLogonW function.


BOOL CreateProcess(
LPCTSTR lpApplicationName,
LPTSTR lpCommandLine,
LPSECURITY_ATTRIBUTES lpProcessAttributes,
LPSECURITY_ATTRIBUTES lpThreadAttributes,
BOOL bInheritHandles,
DWORD dwCreationFlags,
LPVOID lpEnvironment,
LPCTSTR lpCurrentDirectory,
LPSTARTUPINFO lpStartupInfo,
LPPROCESS_INFORMATION lpProcessInformation
);

Thank you, 73,

--
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.

In message , Jonathan N. Little
writes:
Arlen George Holder wrote:
Hi Jonathan,

It's _embarrassing_ that none of us know how Windows works, least of all
me.

While it's a truism that none of us knows how _all_ of Windows works,
there _are_ people who know how sections of it do - and taken as a
whole, we _do_. And by now, there are probably enough who are now
outside Microsoft that we - _as a whole_ - do know how it works, with
the exception of those bits that are to do with licencing/activation
etcetera.

I don't think it's _embarrassing_ as such, that no single individual
knows how all of it works: it's no different to any other complex
entity, such as a power station or even, these days, a car.

That's the nature of proprietary software. The alternative is open
source. This is why this is my only and last Winbox. All others I have a
Linux.

I'm curious: given that Windows has now been around significantly longer
than the average or even extended life of a machine, as has Linux: if
"this" is your current machine, given your stated view of proprietary
software, why did you buy it when you did (alternatives would have been
available)?
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The voices of Radio 4 continuity and newsreading have been keeping me right
for as long as I can remember. I can call on a million different information
sources, but it doesn't make sense unti I've heard it from Peter, Harriet,
Charlotte and the rest.- Eddie Mair in Radio Times 10-16 November 2012

On Sun, 18 Aug 2019 02:08:44 -0000 (UTC), Don Kuenz wrote:

Proprietary closed source is like drugs. Just say no.

As a BSD aficionado, Jonathan and your sympathies are certainly shared
by me. Be that as it may, it's far too late for the likes of us. The
Windows pandemic took hold decades ago.

Empires rise, empires fall. It's only a matter of time.