• windows key + r keys and control + shift + enter keys but without UAC p

    From Mickey D@21:1/5 to All on Mon Oct 21 08:45:58 2024
    XPost: alt.comp.os.windows-11

    When I type the "windows + r" keys and then I type the "control + shift + enter" keys, a "User Account Control" prompt asks me "Do you want to allow
    this app to make changes to your device?" which is unnecessary for me.

    Is there a way to make that UAC prompt not show up when you enter an admin command prompt by typing "windows + r" and "control + shift + enter"?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ed Cryer@21:1/5 to Mickey D on Mon Oct 21 16:49:18 2024
    XPost: alt.comp.os.windows-11

    Mickey D wrote:
    When I type the "windows + r" keys and then I type the "control + shift + enter" keys, a "User Account Control" prompt asks me "Do you want to allow this app to make changes to your device?" which is unnecessary for me.

    Is there a way to make that UAC prompt not show up when you enter an admin command prompt by typing "windows + r" and "control + shift + enter"?


    The Windows key + r is a regular Win10 shortcut (as are lots of other
    Win + ), but Control + shift + enter is not. It is, however, often used
    in third-party progs; for example in MS Word and Mozilla T(B)bird.
    It's your user account control settings that are causing the prompt.
    What level are they set at?

    Ed

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to mickeydavis078XX@ptd.net on Mon Oct 21 12:41:46 2024
    XPost: alt.comp.os.windows-11

    In alt.comp.os.windows-10, on Mon, 21 Oct 2024 08:45:58 -0400, Mickey D <mickeydavis078XX@ptd.net> wrote:

    When I type the "windows + r" keys and then I type the "control + shift + >enter" keys,

    What is your goal when you typce ctrl-shift-enter? If it is to run the program in the run box, why not click on OK?

    Is there some other goal?

    I happen to have msinfo32 showing up in the box and when i do as you do,
    I get the same UAC question you do, but when I click on OK, it starts
    like it always did.

    a "User Account Control" prompt asks me "Do you want to allow
    this app to make changes to your device?" which is unnecessary for me.

    Is there a way to make that UAC prompt not show up when you enter an admin >command prompt by typing "windows + r" and "control + shift + enter"?

    Maybe not, but try OK. ;-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to micky on Mon Oct 21 17:32:59 2024
    XPost: alt.comp.os.windows-11

    On Mon, 21 Oct 2024 12:41:46 -0400, micky wrote:

    What is your goal when you typce ctrl-shift-enter?

    Try it and you'll instantly figure out why it's useful.

    The question isn't why it's useful as EVERYONE will always find it useful.

    The question is how to bring up that admin cmd window WITHOUT a UAC prompt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Ed Cryer on Mon Oct 21 17:33:15 2024
    XPost: alt.comp.os.windows-11

    On Mon, 21 Oct 2024 16:49:18 +0100, Ed Cryer wrote:

    The Windows key + r is a regular Win10 shortcut (as are lots of other
    Win + ), but Control + shift + enter is not. It is, however, often used
    in third-party progs; for example in MS Word and Mozilla T(B)bird.
    It's your user account control settings that are causing the prompt.
    What level are they set at?

    Did you try it?

    It's one of the finest little-known efficiency commands in all of Windows.

    My UAC is set just like yours is and just like everyone's is. The default.

    The question is how to bring up that admin cmd window WITHOUT a UAC prompt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to mickeydavis078XX@ptd.net on Mon Oct 21 18:56:51 2024
    XPost: alt.comp.os.windows-11

    In alt.comp.os.windows-10, on Mon, 21 Oct 2024 17:32:59 -0500, Mickey D <mickeydavis078XX@ptd.net> wrote:

    On Mon, 21 Oct 2024 12:41:46 -0400, micky wrote:

    What is your goal when you typce ctrl-shift-enter?

    Try it and you'll instantly figure out why it's useful.

    I'm not here to play games. I'm trying to offer you a helpful
    suggestion and you won't answer a simple question.

    The question isn't why it's useful as EVERYONE will always find it useful.

    The question is how to bring up that admin cmd window WITHOUT a UAC prompt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to micky on Mon Oct 21 20:11:47 2024
    XPost: alt.comp.os.windows-11

    On Mon, 10/21/2024 6:56 PM, micky wrote:
    In alt.comp.os.windows-10, on Mon, 21 Oct 2024 17:32:59 -0500, Mickey D <mickeydavis078XX@ptd.net> wrote:

    On Mon, 21 Oct 2024 12:41:46 -0400, micky wrote:

    What is your goal when you typce ctrl-shift-enter?

    Try it and you'll instantly figure out why it's useful.

    I'm not here to play games. I'm trying to offer you a helpful
    suggestion and you won't answer a simple question.

    The question isn't why it's useful as EVERYONE will always find it useful. >>
    The question is how to bring up that admin cmd window WITHOUT a UAC prompt.

    This sequence is using the Run box. The OP has not explained which
    executable he is elevating. I am using Notepad.exe as that example.
    (You should NOT run Chrome or Firefox or MSEdge this way. Not good practice.)

    windows r Notepad.exe ctrl-shift-Enter , UAC prompt appears (to elevate Notepad)

    So now I'm running Notepad as Administrator.

    There aren't a lot of executables you need to be running that way.
    It is an option for Process Explorer (procexp.exe), where if you elevate,
    some things like stack sniffing work.

    But for other things, I would find a different way to run them.
    I quite frequently start an Administrator Powershell or
    Administrator Command Prompt, and run an executable in there,
    to get it elevated.

    As for the topic of UAC, blah blah blah.

    If I go to start Seamonkey (it's pinned to Task Bar), and up pops a UAC prompt, that's "abnormal" and you click Cancel if that happens. That's an example where the user is supposed to notice this is a *bad thing* and you stop it from happening.
    That's about the only regular thing that pulls a stunt like that.
    And it happens, because Seamonkey is trying to Upgrade itself, and
    it doesn't have the trick the other browsers use to do it.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Paul on Mon Oct 21 21:31:03 2024
    XPost: alt.comp.os.windows-11

    On Mon, 21 Oct 2024 20:11:47 -0400, Paul wrote:

    This sequence is using the Run box. The OP has not explained which
    executable he is elevating.

    Oh. My mistake. I'm sorry. I didn't realize people misunderstood.

    I thought everyone knew how Windows works when I said in the original post
    the following sentence about specifically elevating the "command prompt".

    "Is there a way to make that UAC prompt not show up when you enter an admin command prompt by typing "windows + r" and "control + shift + enter"?"

    I had assumed people knew that "cmd" is the Windows command prompt.
    I thought that was common knowledge - but it's my mistake if it's not.

    I apologize.

    As you said, any command will be elevated with this method, but I was specifically talking about the command prompt which comes up when you enter "windows + r" and "control + shift + enter" & then "cmd" into the Run box.

    The question is how to make that admin command window come up without the
    UAC prompt. (Sorry for the confusion but I thought everyone knew of "cmd".)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Mickey D on Mon Oct 21 21:33:19 2024
    XPost: alt.comp.os.windows-11

    On Mon, 21 Oct 2024 17:33:15 -0500, Mickey D wrote:

    The question is how to bring up that admin cmd window WITHOUT a UAC prompt.

    I didn't realize people don't know about the "cmd" windows. My mistake.

    I thought it was common knowledge that you can get into an admin command
    window by typing "windows + r" & "cmd" & "control + shift + enter".

    The question is how to bring up that admin cmd window without a UAC prompt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Mickey D on Mon Oct 21 21:37:22 2024
    XPost: alt.comp.os.windows-11

    On Mon, 21 Oct 2024 21:31:03 -0400, Mickey D wrote:

    As you said, any command will be elevated with this method, but I was specifically talking about the command prompt which comes up when you enter "windows + r" and "control + shift + enter" & then "cmd" into the Run box.

    Just to be super clear about the sequence, any command will be elevated
    with this method, but I was specifically talking about the command prompt
    which comes up when you enter "windows + r" and "control + shift + enter"
    with "cmd" into the Run box as shown super clearly obviously in the below.

    1. Windows + r
    2. cmd
    3. Control + shift + enter
    4. Yes to the UAC prompt

    All I want to do is figure out a way for #4 to not happen.
    Any ideas?

    (Other than turning off UAC for all commands - which is not a good idea.)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Mickey D on Tue Oct 22 01:46:04 2024
    XPost: alt.comp.os.windows-11

    On Mon, 10/21/2024 9:37 PM, Mickey D wrote:
    On Mon, 21 Oct 2024 21:31:03 -0400, Mickey D wrote:

    As you said, any command will be elevated with this method, but I was
    specifically talking about the command prompt which comes up when you enter >> "windows + r" and "control + shift + enter" & then "cmd" into the Run box.

    Just to be super clear about the sequence, any command will be elevated
    with this method, but I was specifically talking about the command prompt which comes up when you enter "windows + r" and "control + shift + enter" with "cmd" into the Run box as shown super clearly obviously in the below.

    1. Windows + r
    2. cmd
    3. Control + shift + enter
    4. Yes to the UAC prompt

    All I want to do is figure out a way for #4 to not happen.
    Any ideas?

    (Other than turning off UAC for all commands - which is not a good idea.)


    Well, that's what works, is turning off UAC entirely.

    *******

    There is a second way to run the OS.

    1) Enable the "real administrator" account.
    Now, there is a home directory for the Administrator.

    2) Start : Run : dropmyrights.exe cmd.exe

    That is an example, of starting the Command Prompt window
    in an unelevated state. The "dropmyrights" executable
    as far as I know, is third party. I have a couple other utilities
    of this sort, which are also third party, and are useful for weird
    stuff like that. Todd is the one who posted about this.

    So that's "running upside-down" in a sense. You are always elevated,
    except when you specifically want to de-elevate yourself. As an IT
    guy, Todd likes this when doing a series of maintenance commands for
    a customer. When most of the commands need the elevation, and
    only the occasional one needs "dropmyrights.exe" placed in front of it.

    *******

    Windows has had a "sudo" command added. However,
    this is likely to be a half-assed job and the UAC prompt
    is *still* going to come up. Whether that is in 24H2 only,
    or is available as a Feature before 24H2, I don't know.
    Personally, I am not placing bets on this feature being
    worth my time.

    In Linux, after you authenticate on the first instance of
    "sudo" usage, the token is kept for around ten minutes or so.
    This means if you enter "sudo notepad.exe" a second time,
    you would not be asked for authentication again. However,
    the Windows design intent, is to always present the UAC prompt,
    even if doing identical things in a row:

    sudo notepad.exe UAC prompt, proceed with what you were doing
    sudo notepad.exe UAC prompt, proceed with what you were doing
    sudo notepad.exe UAC prompt, proceed with what you were doing

    Because again, the idea is not to refine the presentation of UAC and
    make it a minimalist thing. The intention is belt-and-suspenders,
    to make sure the user really intended to do this. Even if to any
    casual observer, there's no point in doing the second and third one.

    Some day, I'm going to get to see this new "sudo" feature... Maybe
    I should fire up the Insider and repair it.

    https://learn.microsoft.com/en-us/windows/sudo/

    "Because sudo elevates the targeted process to run
    with administrator-level permission, a prompt will
    open asking you to verify that you want to continue." <=== Bwahahaha!!! No shit!

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Mickey D on Tue Oct 22 06:54:16 2024
    XPost: alt.comp.os.windows-11

    Mickey D wrote:

    1. Windows + r
    2. cmd
    3. Control + shift + enter
    4. Yes to the UAC prompt

    All I want to do is figure out a way for #4 to not happen.

    Hack much?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Mickey D on Tue Oct 22 06:52:21 2024
    XPost: alt.comp.os.windows-11

    Mickey D wrote:

    I thought it was common knowledge that you can get into an admin command window by typing "windows + r" & "cmd" & "control + shift + enter".

    It's not that people here are unaware, it's that You didn't mention
    "cmd" in your original message ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Mickey D on Tue Oct 22 06:47:19 2024
    XPost: alt.comp.os.windows-11

    Mickey D wrote:

    When I type the "windows + r" keys

    The "Run" dialog opens ...

    and then I type the "control + shift + enter" keys

    I just get an error bong, and nothing else happens ...

    a "User Account Control" prompt asks me "Do you want to allow
    this app to make changes to your device?"

    Not here ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Andy Burns on Tue Oct 22 09:52:30 2024
    XPost: alt.comp.os.windows-11

    On Tue, 22 Oct 2024 06:54:16 +0100, Andy Burns wrote:

    1. Windows + r
    2. cmd
    3. Control + shift + enter
    4. Yes to the UAC prompt

    All I want to do is figure out a way for #4 to not happen.

    Hack much?

    It's a neat trick, but it's so simple I wouldn't call it a hack.

    I figured out how to do it using the Windows task scheduler.
    Checking the taskchd.msc "Run with highest privileges" box skips UAC.

    1. Windows + r
    2. admin
    3. enter

    Up comes the command line prompt in a red administrator window.
    The neat trick is not only does #4 not happen, but "enter" works now.

    There's no longer the need to use "Control + shift + enter" anymore.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Mickey D on Tue Oct 22 16:06:57 2024
    XPost: alt.comp.os.windows-11

    Mickey D wrote:

    Andy Burns wrote:

    Hack much?

    It's a neat trick, but it's so simple I wouldn't call it a hack.
    On you own machine, do whatever you like, but I don't want anyone to be
    able to just walk-up to e.g. a relative's machine and get an admin session.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Paul on Tue Oct 22 10:24:31 2024
    XPost: alt.comp.os.windows-11, alt.msdos.batch

    On Tue, 22 Oct 2024 01:46:04 -0400, Paul wrote:

    On Mon, 21 Oct 2024 21:31:03 -0400, Mickey D wrote:

    As you said, any command will be elevated with this method, but I was
    specifically talking about the command prompt which comes up when you enter >>> "windows + r" and "control + shift + enter" & then "cmd" into the Run box. >>
    Just to be super clear about the sequence, any command will be elevated
    with this method, but I was specifically talking about the command prompt
    which comes up when you enter "windows + r" and "control + shift + enter"
    with "cmd" into the Run box as shown super clearly obviously in the below. >>
    1. Windows + r
    2. cmd
    3. Control + shift + enter
    4. Yes to the UAC prompt

    All I want to do is figure out a way for #4 to not happen.
    Any ideas?

    (Other than turning off UAC for all commands - which is not a good idea.)


    Well, that's what works, is turning off UAC entirely.

    *******

    There is a second way to run the OS.

    1) Enable the "real administrator" account.
    Now, there is a home directory for the Administrator.

    2) Start : Run : dropmyrights.exe cmd.exe

    That is an example, of starting the Command Prompt window
    in an unelevated state. The "dropmyrights" executable
    as far as I know, is third party. I have a couple other utilities
    of this sort, which are also third party, and are useful for weird
    stuff like that. Todd is the one who posted about this.

    So that's "running upside-down" in a sense. You are always elevated,
    except when you specifically want to de-elevate yourself. As an IT
    guy, Todd likes this when doing a series of maintenance commands for
    a customer. When most of the commands need the elevation, and
    only the occasional one needs "dropmyrights.exe" placed in front of it.

    *******

    Windows has had a "sudo" command added. However,
    this is likely to be a half-assed job and the UAC prompt
    is *still* going to come up. Whether that is in 24H2 only,
    or is available as a Feature before 24H2, I don't know.
    Personally, I am not placing bets on this feature being
    worth my time.

    In Linux, after you authenticate on the first instance of
    "sudo" usage, the token is kept for around ten minutes or so.
    This means if you enter "sudo notepad.exe" a second time,
    you would not be asked for authentication again. However,
    the Windows design intent, is to always present the UAC prompt,
    even if doing identical things in a row:

    sudo notepad.exe UAC prompt, proceed with what you were doing
    sudo notepad.exe UAC prompt, proceed with what you were doing
    sudo notepad.exe UAC prompt, proceed with what you were doing

    Because again, the idea is not to refine the presentation of UAC and
    make it a minimalist thing. The intention is belt-and-suspenders,
    to make sure the user really intended to do this. Even if to any
    casual observer, there's no point in doing the second and third one.

    Some day, I'm going to get to see this new "sudo" feature... Maybe
    I should fire up the Insider and repair it.

    https://learn.microsoft.com/en-us/windows/sudo/

    "Because sudo elevates the targeted process to run
    with administrator-level permission, a prompt will
    open asking you to verify that you want to continue." <=== Bwahahaha!!! No shit!


    Thanks for your advice and helpful assistance in streamlining Windows.
    I figured out how to bring up an admin command prompt window without UAC.

    At the same time, I streamlined step #3 from 3 keys to only 1 keystroke.
    Plus I was able to colourize the admin command window to make it obvious.

    BEFORE:
    1. Windows + r
    2. cmd
    3. control + shift + enter
    4. Yes to UAC
    5. This opens an administrator command prompt window

    AFTER:
    1. Windows + r
    2. admin
    3. enter
    4. This opens (a red) administrator command prompt window

    I set it to invoke a red administrator command window with white letters.
    The reason for those colors is to distinguish between regular cmd windows.

    All I needed was to make a shortcut that pointed to the task scheduler.
    In taskschd.msc I checked "Run with highest privileges" to skip the UAC.

    Then I added this program to be run when the shortcut calls taskshd.msc.
    cmd /k "cd /d "C:\Windows\System32" & echo admin: & color 4f"

    Clicking the shortcut opens up a red admin cmd window without invoking UAC. Then I needed a quick way to invoke that shortcut from the Windows Run box.

    So I added an "admin" command in the registry to invoke that shortcut. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\admin.exe
    (where admin.exe points to the admin shortcut invoking the admin task).

    With streamlining, I was able to skip not only UAC but multiple keystrokes. Success at last!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Andy Burns on Tue Oct 22 16:57:26 2024
    XPost: alt.comp.os.windows-11, alt.msdos.batch

    On Tue, 22 Oct 2024 06:47:19 +0100, Andy Burns wrote:

    a "User Account Control" prompt asks me "Do you want to allow
    this app to make changes to your device?"

    Not here ...

    Instead of
    1. Windows + r
    2. cmd
    3. control + shift + enter
    4. Yes to UAC
    5. This opens an administrator command prompt window

    The three Windows tricks below reduce those steps to about half.
    1. Windows + r
    2. admin
    3. enter
    4. This opens (a red) administrator command prompt window

    Here's exactly how to set it up so that it works perfectly on any PC.

    1. Create a new task by typing "taskschd.msc" in the Windows Run box.
    Name = admin
    [x]Run with highest privileges
    Action = Start a program = %comspec%
    Arguments = /k "cd /D "C:\Windows\System32" & echo admin: & color 4f"

    2. Point to that new task using a Windows shortcut placed anywhere.
    Name = admin.lnk
    Target = C:\Windows\System32\schtasks.exe /run /TN "admin"
    Start in = %windir%\system32
    Comment = %comspec% /k "cd /D "C:\Windows\System32" & echo admin: & color 4f"

    When you test this shortcut, it should bring up a red admin command
    window (without popping up a UAC request for you to press Yes to).

    3. Create a Windows Run box command in the Windows system registry.
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\
    Rightclick on "App Paths" to create a "New key" named "admin.exe"
    String Value Data = C:\wherever-you-put-the-shortcut\admin.lnk

    Now when you want to enter an admin command prompt, you can just type
    "admin" + "enter" into the Run box which is pinned to your taskbar.

    If you can make it even fewer steps, please let me know how (as that's the
    most efficient way to bring up an admin window I can think of for now).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Andy Burns on Tue Oct 22 16:59:12 2024
    XPost: alt.comp.os.windows-11

    On Tue, 22 Oct 2024 16:06:57 +0100, Andy Burns wrote:

    It's a neat trick, but it's so simple I wouldn't call it a hack.

    On you own machine, do whatever you like, but I don't want anyone to be
    able to just walk-up to e.g. a relative's machine and get an admin session.

    I don't understand your concern since your machine is no different than
    mine (with or without the hack).

    How do you prevent them from getting an admin prompt if they walk up to
    your machine now? What's different with my machine from your machine?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Mickey D on Wed Oct 23 12:43:37 2024
    XPost: alt.comp.os.windows-11

    Mickey D wrote:

    Did you try it out for yourself yet?

    I have plenty of ways to run local or remote batch files or powershell
    scripts

    runas
    sunar
    psexec
    schtasks

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to ...winston on Wed Oct 23 12:15:07 2024
    XPost: alt.comp.os.windows-11, alt.msdos.batch

    On Tue, 22 Oct 2024 20:06:36 -0400, ...winston wrote:

    a "User Account Control" prompt asks me "Do you want to allow
    this app to make changes to your device?"

    Not here ...

    Instead of
    1. Windows + r
    2. cmd
    3. control + shift + enter
    4. Yes to UAC
    5. This opens an administrator command prompt window

    The three Windows tricks below reduce those steps to about half.
    1. Windows + r
    2. admin
    3. enter
    4. This opens (a red) administrator command prompt window

    Here's exactly how to set it up so that it works perfectly on any PC.

    1. Create a new task by typing "taskschd.msc" in the Windows Run box.
    Name = admin
    [x]Run with highest privileges
    Action = Start a program = %comspec%
    Arguments = /k "cd /D "C:\Windows\System32" & echo admin: & color 4f"

    2. Point to that new task using a Windows shortcut placed anywhere.
    Name = admin.lnk
    Target = C:\Windows\System32\schtasks.exe /run /TN "admin"
    Start in = %windir%\system32
    Comment = %comspec% /k "cd /D "C:\Windows\System32" & echo admin: & color 4f"

    When you test this shortcut, it should bring up a red admin command
    window (without popping up a UAC request for you to press Yes to).

    3. Create a Windows Run box command in the Windows system registry.
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\
    Rightclick on "App Paths" to create a "New key" named "admin.exe"
    String Value Data = C:\wherever-you-put-the-shortcut\admin.lnk

    Now when you want to enter an admin command prompt, you can just type
    "admin" + "enter" into the Run box which is pinned to your taskbar.

    If you can make it even fewer steps, please let me know how (as that's the >> most efficient way to bring up an admin window I can think of for now).


    You first asked how to avoid the UAC prompt.
    Now you're trying to educate folks on how to use their devices for
    something only you might use/need?

    Open Command.com in two steps.
    Change the shortcut properites for command.com to an admin level shortcut. Place a copy of the shortcut on your desktop.

    Click the shortcut, click yes. <= two steps

    That works, where I describe the sequence below for others to use also.

    1. Find the location of the command you wish to make a shortcut for
    C:\> where cmd.exe => C:\Windows\System32\cmd.exe
    2. Create a shortcut to that desired executable
    3. Change that shortcut's properties to be an admin-level shortcut
    Rightclick > Shortcut tab > Advanced button >
    Then check the "Run as administrator" box > OK > OK
    4. After testing, rightclick on that shortcut to pin to your taskbar.

    The problem with this method is that you have only so much real estate on
    your task bar and on your desktop where the method I outlined uses none.

    Also, you STILL have to accept the UAC prompt, which negates it as a
    solution if we stick to what the original question had initially asked.

    But - you made me think of a possible way to create a directory of
    shortcuts to any executable that you wish to graphically tap to invoke.

    Initial (messy) PSEUDOCODE below to create the shortcuts you want.

    REM I can't get the syntax to get the next two lines to work:
    REM set /P USER_INPUT = "What command do you want to make a shortcut to?"
    REM where %USER_INPUT% > whereisit.txt
    REM set /P TARGET=<whereisit.txt
    REM So I punt on syntax and just set the target manually. (sigh)

    set TARGET='c:\Windows\System32\cmd.exe'
    set SHORTCUT='c:\TEMP\command.lnk'
    set PWS=powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile
    %PWS% -Command "$ws = New-Object -ComObject WScript.Shell; $s = $ws.CreateShortcut(%SHORTCUT%); $S.TargetPath = %TARGET%; $S.Save()"

    That creates a shortcut to any command that the "where" command finds.
    But I need syntax help for it to create shortcuts to ANY command you like.

    --- https://superuser.com/questions/651352/set-environment-variable-to-output-of-command-in-windows-command-prompt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Mickey D on Thu Oct 24 16:42:36 2024
    XPost: alt.comp.os.windows-11

    Mickey D <mickeydavis078XX@ptd.net> wrote:
    [...]
    Like you, I don't have a need for programs to run with admin privileges,
    but I seem to have a DIFFERENT setup than you with respect to UAC.

    In "my" case, the UAC prompt defaults to NO (and not to YES as yours does). Also in "my" case, no amount of carriage returns will accept that default.
    In "my" case, I MUST move my hands from the keyboard to the mouse for UAC.

    Since forever, you've been able to use the tab key to move around in
    popups like this. In this case either two tabs (No -> Show more details
    Yes) or shift+tab to get from No to Yes (on Windows 11).

    How did you make your UAC popup GUI work completely differently anyway?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to ...winston on Thu Oct 24 12:30:28 2024
    XPost: alt.comp.os.windows-11

    On Thu, 24 Oct 2024 01:09:37 -0400, ...winston wrote:

    For me, that's wasted effort. Still need to access the directory(and
    extra step). Since the UAC prompt defaults to 'Yes' i.e. approve, seems
    like pressing the enter key, since your hands or mouse are readily available(click or press).

    While I would not need or desire to have all programs run in admin mode beyond those that are design by default to do so... the few shortcuts
    that I have enabled to run in admin mode are - Outlook, Command,
    Powershell, Acronis, and Macrium.

    I understand you where I always try to implement solutions that are as
    close to a single tap as possible while taking up zero real estate on the desktop & taskbar - which is what my new red "admin" command does for me.

    Like you, I don't have a need for programs to run with admin privileges,
    but I seem to have a DIFFERENT setup than you with respect to UAC.

    In "my" case, the UAC prompt defaults to NO (and not to YES as yours does). Also in "my" case, no amount of carriage returns will accept that default.
    In "my" case, I MUST move my hands from the keyboard to the mouse for UAC.

    How did you make your UAC popup GUI work completely differently anyway?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mickey D@21:1/5 to Frank Slootweg on Thu Oct 24 12:59:01 2024
    XPost: alt.comp.os.windows-11

    On 24 Oct 2024 16:42:36 GMT, Frank Slootweg wrote:

    In "my" case, the UAC prompt defaults to NO (and not to YES as yours does). >> Also in "my" case, no amount of carriage returns will accept that default. >> In "my" case, I MUST move my hands from the keyboard to the mouse for UAC.

    Since forever, you've been able to use the tab key to move around in
    popups like this. In this case either two tabs (No -> Show more details
    Yes) or shift+tab to get from No to Yes (on Windows 11).

    Must be a setup thing where in "my" case on Windows 10, no amount of tabs
    (or shift tabs) or any keyboard key has any effect on the UAC prompt.

    In trying to think of why my UAC GUI is unresponsive to the keyboard while yours isn't, long ago I disabled the capslock key, so maybe that's why?

    The fact I need to take my hands off the keyboard to access the UAC is why
    I create admin commands (such as regopen for regedit) which bypass the UAC.

    Does everyone else but me have their UAC prompt respecting keyboard inputs?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Mickey D on Thu Oct 24 18:22:58 2024
    XPost: alt.comp.os.windows-11

    Mickey D wrote:

    The fact I need to take my hands off the keyboard to access the UAC is why
    I create admin commands (such as regopen for regedit) which bypass the UAC.

    Does everyone else but me have their UAC prompt respecting keyboard inputs?

    I always use Alt-Y (or Alt-N) to respond to UAC prompts.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charlie@21:1/5 to Andy Burns on Thu Oct 24 12:11:19 2024
    XPost: alt.comp.os.windows-11

    On this Thu, 24 Oct 2024 18:22:58 +0100, Andy Burns wrote:

    Does everyone else but me have their UAC prompt respecting keyboard inputs?

    I always use Alt-Y (or Alt-N) to respond to UAC prompts.

    Windows 11 works different from Windows 10 on UAC controls.

    Change User Account Control (UAC) Settings in Windows 11 https://www.elevenforum.com/t/change-user-account-control-uac-settings-in-windows-11.1523/

    Starting with Windows 11 build 27718.1000 (Canary) you can now enable Administrator Protection to use for Admin Approval Mode (aka: elevated
    rights) instead of User Account Control (UAC). https://www.elevenforum.com/t/windows-11-insider-canary-build-27718-1000-oct-2.29083/

    Enable or Disable Administrator Protection for Admin Approval Mode in Windows 11
    https://www.elevenforum.com/t/enable-or-disable-administrator-protection-for-admin-approval-mode-in-windows-11.29115/

    Administrator Protection is an upcoming platform security feature in
    Windows 11, which aims to protect free floating admin rights for
    administrator users allowing them to still perform all admin functions with just-in-time admin privileges. This feature is off by default and needs to
    be enabled via group policy. Microsoft plans to share more details about
    this feature at Microsoft Ignite.

    Admin Approval Mode runs in legacy mode by default, and uses User Account Control (UAC) for elevation approval.

    If you enable Administrator Protection, Admin Approval Mode uses Windows Security for a more secure elevation approval instead of User Account
    Control (UAC).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)