Double-clicking an executable application, launching a software installer, or triggering an automated PowerShell script in Windows 11 only to be stopped by the dialogue box: “The requested operation requires elevation”, accompanied by Win32 system error code 740 (ERROR_ELEVATION_REQUIRED), halts workflow execution. In Windows User Account Control (UAC) security architecture, standard user accounts and administrative user accounts run applications with standard, restricted access tokens by default. When an application binary or script requires full administrator rights—such as modifying protected directories in C:\Program Files, accessing system registry hives in HKEY_LOCAL_MACHINE, or installing low-level system services—Windows mandates that the process be launched from an elevated security context. This guide walks you through resolving Error 740 across individual shortcuts, command shells, and automated scripts.
Why Does Windows Throw Error 740?
The elevation requirement is an intentional security perimeter designed to prevent background malware from silently altering core system configurations. Common scenarios triggering Error 740 include:
- Unprivileged Parent Process Launching Elevated Child: A non-elevated command prompt, Python script, or third-party launcher attempting to invoke an executable whose manifest requires administrator rights (
requireAdministrator). - Application Compatibility Settings: The application shortcut or binary was previously configured with the “Run this program as an administrator” compatibility flag, but is being called by an automated tool without elevation prompts.
- Protected Destination Directories: Installers or updater utilities attempting to write temporary payload files directly into protected system directories like
C:\Windows. - Corrupted User Account Control (UAC) Token Policies: Group Policy or local security policies misconfigured to silently deny elevation requests rather than displaying the UAC credential prompt.
Method 1: Run the Executable as Administrator Manually
The most direct resolution when launching standalone programs is requesting an elevated security token explicitly.
- Locate the application executable (
.exe) or desktop shortcut. - Right-click the icon and select Run as administrator.
- When the User Account Control dialogue appears asking “Do you want to allow this app to make changes to your device?”, click Yes (or enter an administrator password).
- The application will launch with full administrative privileges.
Method 2: Set Permanent Administrative Rights on the Application Shortcut
If you regularly use an administrative utility (such as disk partitioners, network diagnostics, or legacy business software), configure its shortcut to always prompt for elevation.
- Right-click the program’s shortcut on your Desktop or Start Menu and select Properties.
- In the Shortcut tab, click the Advanced… button in the bottom-right corner.
- Tick the checkbox for Run as administrator.
- Click OK, then click Apply.
- Alternatively, switch to the Compatibility tab, tick Run this program as an administrator, and click OK. Whenever you double-click the shortcut, Windows will automatically present the UAC elevation prompt.
Method 3: Launch Scripts from an Elevated Command Prompt or Terminal
If Error 740 occurs while executing batch files, PowerShell scripts, or command-line compilers, the hosting terminal must be elevated first.
- Press Windows Key + X to open the Power User Quick Link menu.
- Select Terminal (Admin) or Command Prompt (Admin).
- Click Yes on the UAC prompt to launch the elevated shell session.
- Verify that the title bar displays “Administrator: Windows PowerShell” or “Administrator: Command Prompt”.
- Navigate to your script’s directory and execute your command. Because the parent terminal holds elevated tokens, all child processes will inherit elevation without triggering Error 740.
Method 4: Modify UAC Behaviour in Local Security Policy
On Windows 11 Pro and Enterprise editions, ensure that local security policies are configured to prompt standard users and administrators appropriately.
- Press Windows Key + R, type
secpol.msc, and press Enter. - Navigate to Security Settings > Local Policies > Security Options.
- Scroll down to the policies beginning with User Account Control.
- Locate User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode. Ensure it is set to Prompt for consent.
- Locate User Account Control: Detect application installations and prompt for elevation and verify it is set to Enabled.
- Restart your PC to enforce the updated security policies.