Home / Guides / Windows errors

Error 740: The requested operation requires elevation - fix it properly

"Elevation" is Windows-speak for administrator rights. Error 740 appears when a program needs those rights to do its job - install something, write to a protected folder, manage a service - but the hand-over fails: User Account Control never asked, a shortcut carries wrong flags, or a policy blocks the prompt. The fix is quick once you know which of these it is.

Fix it automatically

Outbyte Driver Updater identifies your installed hardware automatically and updates outdated or broken drivers from official sources, with a backup before every change. Useful when you would rather not run the steps below by hand - the scan and diagnosis are free.

Download Driver Updater Downloads Outbyte Driver Updater for Windows 11, 10, 8 and 7. Free 2-day trial, no credit card required.

Quick answer

Right-click the program or installer and choose "Run as administrator" - that resolves most cases on the spot. If the same program hits error 740 every time, open its Properties, the Compatibility tab, and tick "Run this program as an administrator" so the elevation happens automatically.

Symptoms - how this problem looks

"Error 740: The requested operation requires elevation"
An installer or setup.exe refuses to start with this message
CreateProcess failed with error 740 in a command window or script
The error appears only for one program - everything else runs fine
It started after changing UAC settings or "optimizing" Windows
No UAC prompt ever appears - the program fails silently with 740

Why it happens

The program needs rights it was not given

Installers and system tools must run elevated. When they are started without the administrator hand-over, Windows stops them with 740 instead of letting them fail halfway.

UAC was tampered with

When User Account Control is switched off or set oddly by an "optimizer", the elevation prompt never appears - and programs that need it get error 740 instead.

A stale or misflagged shortcut

Shortcuts keep their own compatibility flags. An old shortcut with a wrong flag, or one pointing at a moved program, triggers 740 while the exe itself starts fine.

One program launching another

When a normal program tries to start an elevated one directly (CreateProcess), Windows refuses with 740 - common in scripts, launchers and download managers.

The fixes, in order

1. Run the program as administrator (fixes most cases)

  1. Right-click the program or installer and choose "Run as administrator".
  2. Answer Yes to the User Account Control prompt.
  3. If it works, and the program always needs elevation, make it permanent with method 2.

2. Make elevation automatic for that program

  1. Right-click the program's exe (or shortcut), choose Properties, then the Compatibility tab.
  2. Tick "Run this program as an administrator" and press OK.
  3. From now on Windows elevates it on every launch - with the normal UAC confirmation.

3. Recreate the shortcut

  1. If the error hits a desktop or Start menu shortcut, delete that shortcut.
  2. Find the program's exe in its installation folder, right-click it and choose "Show more options", then Send to, then Desktop - a fresh shortcut without stale flags.

4. Check that UAC is on and healthy

  1. Press Start, type "UAC" and open "Change User Account Control settings".
  2. If the slider is at the very bottom (Never notify), move it to the default (second from top) and press OK.
  3. Restart the PC. With UAC off, elevation prompts cannot appear and error 740 becomes frequent - keeping UAC on is both safer and more compatible.

5. If it started recently - repair Windows

  1. Right-click Start, open Terminal (Admin), and run sfc /scannow.
  2. If problems persist, run DISM /Online /Cleanup-Image /RestoreHealth, then SFC again, then restart.

Do not do this: Do not switch User Account Control off to "fix" error 740. UAC is the mechanism that grants elevation; disabling it trades one error message for a PC where every program runs unprotected. Elevate the one program that needs it instead.

Frequently asked questions

I am the only user of this PC. Why does Windows still ask for elevation?

Even an administrator account runs programs with standard rights by default - that is how User Account Control protects the system. Elevation is the moment a program is granted the full rights, and error 740 means that hand-over failed rather than that you lack an account.

Is it safe to mark a program to always run as administrator?

For a trusted program that genuinely needs it - an installer, a disk tool, an old game - yes. Do it per program in its Compatibility settings rather than switching UAC off globally: UAC protects every other program on the PC and should stay on.

The error appears for a shortcut on my desktop but not for the program itself. Why?

The shortcut carries its own compatibility flags. If an old shortcut points to a moved or updated program, delete it and create a fresh one from the program's exe - stale shortcuts are a common source of error 740. For other launch errors, see the common Windows errors guide.