Create & Run any task with Administrative privileges in Windows 11/10

We have read a little about the Run dialog box and the new Run commands in Windows. Now most of us are aware that to open the Run dialog box, you can press WinKey+R. You can also type Run in the search box to access it. In Windows 11/10/8 and Windows RT, you can also open the Run dialog box using the WinX Menu.

Create this task with Administrative privileges

When you Run some tasks, you may see the UAC shield on the Run dialog box, with a message that This task will be created with administrative privileges. This is because, when Windows executes certain tasks, they need to be created with administrative privileges. Windows realizes this and acts accordingly. But what if you decide that you need to create a task with administrative privileges?

In this post, we will see how to open an “elevated” Run box which will let you Run any task with administrative privileges in Windows 10/8.

To do so, right-click on the Taskbar and select Task Manager to open it. If your Task Manager is set to show fewer details, click on More details. Now in the Menu bar, select File > Run new task.

This will open a Run dialog box which shows you an additional option that will allow you to Create this task with administrative privileges.

You can type the task and check this option to run the task as an administrator.

Why does holding the Ctrl key when selecting New Task from Task Manager open a command prompt?

If you hold the CTRL key and click New Task from Task Manager, it directly opens an elevated command prompt. Do you know WHY?

Says Microsoft:

It’s a rogue feature. Windows XP introduced visual styles, and one of the tricky parts of debugging visual styles is that if the visual style engine goes berzerk, you can’t see anything! One of the problems that the visual styles folks encountered when developing their feature was that sometimes they would get into a state where the Run dialog would stop working. And without a Run dialog, you couldn’t install or launch a debugger to begin investigating what went wrong. The solution: Add the rogue feature where holding the Ctrl key when selecting New Task from Task Manager opened a command prompt directly, without involving the Run dialog. From that command prompt, you can then install the debugger and start debugging. (This technique also took advantage of the fact that console windows were not themed in Windows XP. If the visual style system got all messed up, at least your console windows worked!) Over time, the bugs in the visual style system got worked out, and this rogue escape hatch was no longer needed, but for whatever reason, it never got removed.

Take care!