How to Run Windows Applications as Administrator Without UAC Prompts

10 min read

Help Desk Geek is reader-supported. We may earn a commission when you buy through links on our site. Learn more.

A trusted Windows application keeps showing a User Account Control prompt each time you run it as administrator. That gets old fast, but Task Scheduler can launch that app with administrator rights while UAC stays enabled elsewhere.

What Is Windows Task Scheduler?

Windows Task Scheduler is built into Windows. It can start programs on a schedule, after system events, or when you ask.

UAC shows a prompt when an app requests administrator access. This prompt helps stop unapproved software from changing protected files, settings, services, or another user’s data.

Task Scheduler can save an approved setup for one app. Once an administrator approves the task, you can run the app with the highest rights available to that account. You won’t need to approve the same prompt each time.

Warning: Create this launcher only for an app you trust and already run as administrator. Keep its executable at a fixed path in a protected folder, such as C:\Program Files. Don’t use this method for unknown downloads, files that change often, or executables in folders a standard user can edit.

Prerequisites

Make sure you have:

  • Windows 11 or Windows 10
  • An administrator account, or access to an administrator who can approve the task
  • A trusted application that genuinely needs administrator rights
  • The application’s executable path
  • Any command-line arguments the application requires
  • User Account Control left enabled

A standard user can’t use Task Scheduler to give themselves administrator rights. An administrator must check the app and approve the elevated task.

Step-by-Step Guide

Fix #1: Locate the Trusted Application

  • Open Start and search for the application.
  • Right-click the result and select Open file location.
  • If File Explorer opens a shortcut, right-click it and select Properties.
  • Check the path in the Target field.
  • Confirm that the target is the application’s real .exe file from a publisher you trust.
  • For another check, open Settings > Apps > Installed apps and verify the application’s source.

Expected result: You have the full path to a trusted executable, such as C:\Program Files\Example App\ExampleApp.exe.

Stop if the file is in Downloads, a temporary folder, or any place where a non-administrator could replace it. A handy shortcut isn’t worth the risk if you can’t verify the executable.

Fix #2: Open Task Scheduler

  • Open Start.
  • Type the following search query:

Task Scheduler

  • Select Task Scheduler from the results.
Windows Start search results with Task Scheduler selected
  • If it doesn’t appear in search, press Windows + R.
  • Enter this command:

taskschd.msc

  • Select OK.
  • Select Task Scheduler Library in the left pane.

Expected result: The Task Scheduler console opens. You should see the task library, task list, and Actions pane.

Fix #3: Create a Full Task

  • Select Create Task in the right-side Actions pane.
  • Don’t select Create Basic Task. That wizard omits the security, power, and instance settings you need.
Task Scheduler Library selected with Create Task highlighted and Create Basic Task marked as the option not used
  • On the General tab, enter a clear name, such as:

Example App (Admin)

  • Add a description with the executable name. Note that it’s an on-demand elevated launcher.
  • Under Security options, confirm that the correct Windows account is selected.
  • Select Run only when user is logged on. A desktop app needs this setting so its window appears in your session.
  • Select Run with highest privileges.
  • Open Configure for and choose the best Windows version listed. Windows 10 may be the newest choice on some Windows 11 PCs, and that option works.
Create Task General tab showing Name, the selected account, Run with highest privileges, and Configure for

Expected result: The task has a clear name, uses the right account, and runs with the highest rights available to that account.

Fix #4: Point the Task at the Executable

  • Open the Actions tab.
  • Select New.
  • Leave Action set to Start a program.
  • Select Browse beside Program/script.
  • Choose the trusted application’s .exe file.
  • Confirm that Program/script contains only the executable path. For example:

C:\Program Files\Example App\ExampleApp.exe

  • If the app needs command-line options, enter only those options in Add arguments (optional). For example:

–profile “Office”

  • If the app loads files from its installation folder, enter that folder in Start in (optional). Leave out the executable name and quotation marks:

C:\Program Files\Example App

  • Select OK.
New Action dialog showing Start a program, Program/script, Browse, Add arguments, and Start in

Expected result: The Actions tab lists one Start a program action that points to the trusted executable.

Keep the three fields separate. Program/script holds the .exe path. Add arguments holds launch options, while Start in holds the working folder. Mixing them can stop the app from opening correctly or finding its settings files.

Fix #5: Configure Power and On-Demand Settings

  • Open the Conditions tab.
  • On a laptop, clear Start the task only if the computer is on AC power if you want the app to launch on battery power.
  • Clear Stop if the computer switches to battery power if it’s selected and the app must stay open after you unplug the laptop.
Create Task Conditions tab showing the Start the task only if the computer is on AC power restriction
  • Open the Settings tab.
  • Select Allow task to be run on demand.
  • Find If the task is already running, then the following rule applies.
  • Choose Do not start a new instance unless the app should run several copies at once.
Create Task Settings tab showing Allow task to be run on demand and Do not start a new instance

Expected result: You can start the task by hand under your chosen power settings without opening unwanted duplicate windows.

Fix #6: Save and Test the Elevated Task

  • Select OK in the Create Task window.
  • Approve the UAC prompt or enter administrator credentials if Windows asks. This one-time approval saves the elevated task setup.
  • Select Task Scheduler Library.
  • Find and select the task you created.
  • Select Run in the Actions pane.
Task Scheduler Library with the saved task selected and Run highlighted in the Actions pane
  • Confirm that the intended app opens.
  • Try an app function that needs elevation, or check its process with an administrator-status tool.
  • Close the app.
  • Return to Task Scheduler and check Last Run Result. A successful launch often shows 0x0. Some apps leave the task marked as Running until their process closes.

Expected result: The trusted app opens with administrator rights and no new UAC consent prompt.

The app is elevated when Run with highest privileges is selected and the task uses an approved administrator account. Task Scheduler uses the elevated setup you approved when saving the task.

Fix #7: Create a Desktop Shortcut

  • Right-click an empty part of the desktop.
  • Select New > Shortcut.
  • In Type the location of the item, enter this command. Replace the sample name with the task’s exact name:
schtasks.exe /run /tn "Example App (Admin)"
  • If you saved the task in a Task Scheduler subfolder, include its full path:
schtasks.exe /run /tn "\My Tasks\Example App (Admin)"
Windows Create Shortcut dialog containing schtasks.exe /run /tn followed by the exact quoted task name
  • Select Next.
  • Enter a clear shortcut name, such as Example App (Admin).
  • Select Finish.
  • Double-click the new shortcut.
  • Confirm that the app opens without a UAC prompt.

Expected result: The desktop shortcut starts the elevated task without opening the Task Scheduler console.

Don’t enable Run this program as an administrator for the shortcut. That setting asks Windows to elevate the shortcut process, so the UAC prompt returns. The saved task provides the prompt-free elevation.

Fix #8: Assign the Application’s Icon

  • Right-click the finished shortcut.
  • Select Properties.
  • Open the Shortcut tab.
  • Select Change Icon.
  • Select Browse.
  • Choose the trusted application’s executable.
  • Select an icon.
  • Select OK.
  • Select Apply.
Finished desktop shortcut and its Properties dialog with Change Icon highlighted

Expected result: The elevated launcher uses the app’s normal icon, so it’s easy to spot on the desktop.

Configuration

Common Task Patterns

SettingRecommended valueWhy
Run only when user is logged onEnabledLets an interactive desktop window appear
Run with highest privilegesEnabledGives the application the highest rights available to the selected account
Configure forMost appropriate available Windows versionUses compatible Task Scheduler behavior
ActionStart a programOpens the trusted executable directly
Allow task to be run on demandEnabledAllows launches from Task Scheduler and schtasks.exe
If the task is already runningDo not start a new instanceStops repeated clicks from opening duplicate copies
Start only on AC powerDisabled when battery launches are neededStops the task from silently failing on a laptop battery

To edit these settings, open Task Scheduler Library, right-click the task, and select Properties. Windows may ask for administrator approval when you save account or privilege changes.

Keep UAC Enabled

Don’t disable UAC or choose Never notify to avoid the prompt. Those options weaken warnings across Windows. This task grants prompt-free elevation to one approved executable.

Treat the shortcut as an elevated entry point. Check the executable path and publisher after a major app update, especially if the installer moves or replaces the file.

When Windows 11 Sudo Is More Appropriate

Windows 11 sudo runs administrative commands from a terminal. Use it when you need to run a command without opening a separate elevated terminal window.

For a desktop app you open often, the Task Scheduler launcher is a better fit. It gives you a normal shortcut and limits approval to the saved task.

Tips and Troubleshooting

Fix #9: Correct Missing Privileges or the Wrong Account

  • Open Task Scheduler Library.
  • Right-click the task and select Properties.
  • On General, verify the selected user account.
  • Select Run with highest privileges.
  • Confirm that the account has administrator rights.
  • Select OK and provide administrator approval.
  • Test the task with Run.

If the app opens but lacks administrator access, check this setting first. A standard user can’t add elevated rights to their own task. An administrator must review and set it up.

Fix #10: Correct a Shortcut That Cannot Find the Task

  • Open Task Scheduler and copy the task’s exact name.
  • Right-click the desktop shortcut and select Properties.
  • Compare the name after /tn with the saved task name.
  • Keep quotation marks around names that contain spaces.
  • Include the full Task Scheduler folder path when needed:
schtasks.exe /run /tn "\Folder Name\Exact Task Name"
  • Select Apply.
  • Test the shortcut again.

If Run works in Task Scheduler but the shortcut fails, the task name or folder path is usually wrong. Also open the task’s Settings tab and confirm that Allow task to be run on demand is selected.

Fix #11: Correct Arguments and the Working Directory

  • Right-click the task and select Properties.
  • Open Actions.
  • Select the action and choose Edit.
  • Put only the executable path in Program/script.
  • Put only launch options in Add arguments.
  • Put only the containing folder in Start in.
  • Select OK.
  • Test the task from Task Scheduler.

This fixes an odd problem: the app opens but can’t find a profile, plug-in, script, or settings file. The working folder is often the missing piece.

Fix #12: Correct Power and Duplicate-Instance Problems

  • Open the task’s Properties.
  • On Conditions, clear the AC-power limit if launches fail while the laptop uses its battery.
  • On Settings, set the already-running rule to Do not start a new instance if repeated clicks open several copies.
  • Select OK.
  • Test the task under the same conditions that caused the problem.

If the task stays marked as Running after the app closes, edit its action and point it straight to the app’s .exe. I’d avoid wrappers such as cmd.exe unless the program needs one.

Fix #13: Repair a Task After an Application Update

  • Locate the application’s current executable.
  • Verify its publisher and installation folder.
  • Open the task’s Properties.
  • Edit the existing action.
  • Browse to the new executable path.
  • Recheck Add arguments and Start in.
  • Save the task with administrator approval.
  • Test it using Run before returning to the desktop shortcut.

Stop using the task if an unknown process changes the executable or the app starts acting strangely. Repeated path changes, unexplained administrator activity, or security alerts can point to malware or a damaged installation.

Wrapping Up

StepActionApplies To
1Verify the executable and publisherEvery application
2Create a full task with highest privilegesWindows 10 and Windows 11
3Add the executable, arguments, and working folderApplications that require elevation
4Test the task from Task SchedulerEvery new task
5Create a schtasks.exe desktop shortcutOn-demand desktop launches

The Task Scheduler shortcut is my pick for an app you trust and often run as administrator. It removes the repeated prompt while keeping UAC active elsewhere in Windows.

Check the executable after updates. If its path changes for no clear reason or you see unexpected administrator activity, stop using the launcher and scan the PC for malware.