Windows sometimes needs an application to run with elevated privileges before it can change system-wide settings, write to protected locations or perform an administrative task. You may see the option Run as administrator when you right-click a program or shortcut. Elevating an app can be useful, but it also gives that process more authority than an ordinary application, so it should be used only when the task actually requires it.
What “administrator” means
An administrator account has access to actions that standard users may not be allowed to perform. Windows User Account Control (UAC) is designed to help protect the system by asking for approval when an action requires elevation. The exact prompt depends on the account and security configuration.
Run an app as administrator from the Start menu
- Open Start.
- Search for the application.
- Right-click the application result.
- Choose Run as administrator.
- Approve the UAC prompt if Windows asks you to do so.
If the application requires elevation for the action you are trying to perform, it should now run with the required permissions. Microsoft documents UAC as a security boundary that helps prevent unauthorized system changes.
Run a program as administrator from File Explorer
Find the application's executable file or shortcut in File Explorer, right-click it, and choose Run as administrator when the option is available. This is useful when you already know which executable you need rather than searching through the Start menu.
Why an administrator prompt appears
An app may request elevation because it needs to change settings for all users, modify protected system areas or perform an administrative installation or repair. The prompt does not automatically mean that the application is unsafe. It means Windows is treating the requested action as requiring a higher level of access.
Why you should not run everything as administrator
Elevation increases what the process can do. If an application is compromised, badly configured or given a malicious file, extra privileges can increase the consequences of the problem. For ordinary browsing, document editing or media playback, there is usually no reason to elevate the application just because the option exists.
Example: editing a protected configuration
Suppose you need to edit a system-wide configuration file stored in a protected folder. A normal text editor may open the file but fail when it tries to save changes. Running the editor as administrator can allow the save operation, provided you actually have authorization to change that file.
Before doing this, check that you are editing the correct file and keep a backup. Administrator access does not make a wrong configuration change safer.
Use administrator access only for the required task
A good habit is to elevate only the program and action that needs it. Once the task is complete, close the elevated application. Avoid leaving an administrator-level application open while performing unrelated work.
What if “Run as administrator” is missing?
The application may be a packaged app, the context menu may differ, or the current account may not have the required permissions. If the task normally requires elevation, check the software's documentation or your organization's Windows policy. Do not disable UAC simply to remove the prompt.
UAC is a security control
Windows User Account Control exists to make elevation visible and require approval for certain changes. Lowering UAC settings or disabling the feature is not a general solution for applications that request administrator rights. If an application constantly asks for elevation, investigate why it needs it instead of weakening the system-wide security control.
When an application should not be elevated
Do not elevate an unknown program merely because a website tells you to. Verify the application's source, publisher and purpose first. A request for administrator access from an unexpected installer, script or executable deserves extra scrutiny.
Troubleshooting a failed elevated action
- Confirm that you launched the intended executable.
- Read the exact error message.
- Check whether your account has permission to perform the task.
- Look at the application's current documentation.
- Try the supported repair or installation method rather than repeatedly increasing privileges.
Quick checklist
- □ I understand why the task needs elevation.
- □ I trust the application and its source.
- □ I backed up important configuration before editing it.
- □ I approved UAC intentionally.
- □ I did not disable UAC just to avoid the prompt.
- □ I closed the elevated app after finishing the task.
Quick answer
To run a program as administrator, search for it from Start or right-click its executable/shortcut and choose Run as administrator, then approve the UAC prompt when requested. Use elevation only when the task genuinely requires it, because administrator privileges increase the authority of the application.