Create Elevated Shortcut without UAC prompt in Windows 10  

Great news.

nlztrk said:

Thanks for this topic. Saved for my all time.

I'm glad it could help nlztrk, and welcome to Ten Forums.

Cirus said:

@Brink
I read this useful tutorial in the past even on Windows 7 Forums and especially I successfully applied Method 2: "To Create Elevated Shortcut for User using runas Command".
Pardon me if I have missed something but could it be applied also to "wushowhide.diagcab"?
I tried unsuccessfully.
If you know a way.
Thanks.

I don't think it can work with "wushowhide.diagcab" since it would most likely run an application file within the .cab instead.

jstuardo said:

Hello,

I am wondering why the command parameters has to be specified this way:

Code:

/c start "Task Name" "Full path of application file"

when running a program using CMD program, one can only use

Code:

/c "Full path of application file"

Regards
Jaime

Hello Jaime,

I have always had success with "start" included in the command in Task Manager, while it may not always work without it. Basically, just to make sure the task's script runs.

The start command can be used to run a command/batch file (task script in this case) in a separate command window or to launch an application from command line.

@Brink,
I have written CMD and VBScript files that can automatically create an elevated app shortcut with no UAC prompt. They apply to built-in apps such as Command Prompt, PowerShell, and Registry Editor as well as third-party apps such as WAU Manager. Users just have to take three steps:

1. Double-click on the script file "Create an elevated shortcut.cmd".
2. Enter the application's name, to be used as the task name and shortcut name.
3. Enter the application's full path.

Then, the scripts will create a scheduled task with highest privileges and a CMD file, used as a shortcut, on the desktop. The scripts are in this attached file: Create_an_elevated_shortcut.zip. Would you consider including it in this tutorial?

PS A small problem in my deleted post has been fixed in this post.