Error 740 means Windows blocked a program or command because it was started without the elevated administrator token required for that operation. The usual fix is to close it, launch the program or shell with Run as administrator, and approve the User Account Control (UAC) prompt. If no prompt appears, Windows policy, account permissions, or the application’s configuration may be preventing elevation.
This guide explains what the code means, why it can appear even when you are an administrator, how to fix it safely, and what information to give an administrator when the computer is managed.
As an Amazon Associate I earn from qualifying purchases.
What Error 740 means
Microsoft’s Win32 system-error table defines error 740, hexadecimal 0x2E4, as “The requested operation requires elevation.” In practical terms, the process that attempted the action did not have the full administrator token Windows requires.
Elevation is a permission change for one process, not a permanent label attached to your user account. A program can be launched by a member of the Administrators group and still begin with a filtered token. Windows then requires that program to request a higher-privilege token before it can change protected settings, write to protected folders, install components, or perform another administrative task.
#1 Best Overall
Why this can happen to an administrator
UAC normally runs an administrator’s everyday applications with a filtered standard access token. When an operation needs administrator rights, Windows displays a consent prompt and starts the selected process with the full administrator token after you choose Yes. Therefore, being listed as an administrator does not prove that the particular Command Prompt, Terminal window, launcher, installer, or utility is elevated.
A standard user can also complete an approved administrative task by entering valid credentials for a local administrator account. If the prompt is configured to deny elevation automatically, however, Windows displays an access-denied result instead of offering a usable elevation path.
Choose the right fix first
| What you see | Most likely next step |
|---|---|
| Error 740 appears immediately when starting a program or command | Close it and start the executable or shell with Run as administrator. |
| A UAC prompt appears and asks for confirmation | Verify the program and requested action, then select Yes if you intended to run it. |
| A credential prompt appears | Enter valid credentials for a local administrator account, or ask the device administrator to perform the task. |
| No elevation prompt appears and access is denied | Ask an administrator or IT team to review UAC and local or Group Policy settings. |
| The same application requires elevation on every launch | Inspect its Compatibility settings and ask the vendor whether a current build can run only the task that genuinely needs elevation. |
| The computer belongs to an employer, school, or shared gaming setup | Do not change security policy yourself; provide the exact error and launch details to the administrator. |
Fix Error 740 in a safe order
1. Elevate the program once
- Save your work and close the program that displayed Error 740.
- Find its desktop shortcut, Start menu entry, or executable file in File Explorer.
- Right-click the shortcut or executable and select Run as administrator.
- Read the UAC prompt. Confirm that the publisher and program match what you intended to open.
- Select Yes to approve the operation. If another person administers the computer, select the option to provide administrator credentials when Windows requests them.
For a game or game utility, elevate the component that actually produced the message. If a launcher starts a separate updater, anti-cheat component, configuration utility, or mod tool, closing and elevating only the launcher may not elevate the child process. Start the named helper program directly only when you know it is part of the installation and you obtained it from a trusted source.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →2. Open an elevated Command Prompt
- Open Start and search for Command Prompt.
- Right-click Command Prompt and choose Run as administrator.
- Approve the UAC prompt or enter administrator credentials.
- Run the command again in that new window.
Do not simply reopen a normal Command Prompt and assume that membership in the Administrators group is enough. The window must have been launched through the elevation path. Keep the original command unchanged while testing; changing several variables at once makes it harder to identify the cause.
3. Open an elevated Windows Terminal or PowerShell window
- Open Start and search for Windows Terminal or PowerShell.
- Right-click the result and select Run as administrator.
- Approve the UAC prompt.
- Choose the appropriate shell tab and repeat the command.
If the command is stored in a script or batch file, launching the script from an elevated shell may be sufficient. If the script starts another executable, that executable can still have its own elevation requirement or application-manifest setting.
4. Supply administrator credentials when Windows asks
A standard account cannot approve an administrative action with its own password unless it has the required rights. At a credential prompt, enter the username and password for a local administrator account supplied by the device owner or IT team. An administrator using Admin Approval Mode normally sees a consent prompt and must select Yes.
If you do not have authorized administrator credentials, do not attempt to bypass the prompt. Ask the owner or administrator to run the task, or request the specific permission needed. Repeatedly trying different accounts can create confusing audit records and does not change the permission state of the already-running process.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →5. Check whether UAC policy is blocking elevation
Windows UAC policy can be configured to prompt for consent, prompt for credentials, or deny elevation requests automatically. The Automatically deny elevation requests setting produces an access-denied message instead of allowing the user to approve the operation.
If you receive no usable prompt, ask an authorized administrator to review the local security or Group Policy settings. On a managed computer, the organization may intentionally prevent users from elevating applications. Do not lower UAC or disable the secure desktop merely to make one game, installer, or command run; those controls are part of Windows’ protection against unauthorized changes.
6. Inspect the application’s Compatibility setting
- Close the application.
- Right-click its shortcut or executable and choose Properties.
- Open the Compatibility tab.
- Look for Run this program as an administrator.
- If it is selected, determine whether the program truly needs elevation every time. Clear the setting only if you understand the effect and the application can operate correctly without it.
- Select Apply, then OK, and test the program normally.
Microsoft’s application guidance says most desktop applications should run with an asInvoker execution level and request elevation only for the operation that genuinely requires it. An application that truly needs full administrator rights can declare requireAdministrator. If a program has been configured to elevate for every launch but needs elevated access only for one maintenance task, ask its vendor for an updated build or a configuration that separates those actions. Unnecessary elevation increases the attack surface of the application.
Rank #3
7. Ask the device administrator on managed PCs
On an employer-owned, school-managed, family-shared, or kiosk-style PC, Group Policy and local security policy may control UAC behavior. Changing those settings without authorization can violate the organization’s security requirements or be reversed at the next policy refresh.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Give the administrator a concise record containing:
- The exact error text and code, including
740or0x2E4. - The program, executable path, or complete command that triggered it.
- Whether the process was started from a normal or elevated Command Prompt, PowerShell, or Windows Terminal window.
- Whether the account is standard or a member of the Administrators group.
- Whether Windows displayed a consent prompt, a credential prompt, or an immediate access-denied message.
- The Windows edition and build, and whether the device is managed by an organization.
Those details let an administrator distinguish a missing one-time elevation from a policy denial or an application configuration problem.
Game-related cases where Error 740 appears
Game launchers and installers
If an installer or launcher needs to write to a protected location or modify system-wide settings, close it and use Run as administrator once. Approve only a prompt that identifies the installer or launcher you intentionally started. If the same prompt appears for an unfamiliar executable, stop and verify the file’s origin before granting access.
Mods, utilities, and configuration tools
A mod manager, graphics utility, save-game tool, or server administration script may target a protected folder or require an elevated helper. First elevate the shell or utility that directly performs the operation. If the tool demands elevation on every launch, check its Compatibility setting and look for a current release that requests rights only when it performs the administrative action.
Anti-cheat or update components
If a launcher starts a separate service, updater, or protection component, the child executable may have a different elevation requirement. Record the exact file name shown in the error and report it to the game publisher or your administrator. Do not replace a component with an unrelated executable or disable Windows security controls to force the game to start.
Protected save and installation folders
An elevation error can occur when a tool tries to modify a protected installation directory rather than a user-writable folder. The safe response is to follow the software vendor’s documented storage location or have an administrator perform the approved change. Moving folders or changing permissions blindly can break updates, separate user profiles, or expose files to other accounts.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why “Run as administrator” may still fail
The wrong process was elevated
Elevating a launcher does not guarantee that every helper it starts receives the same token. Identify the executable named in the message and test that component through its own shortcut or from an elevated shell.
The account lacks usable administrator credentials
An account can be listed as an administrator in one context while the current sign-in, remote session, or organizational policy still requires another account’s credentials. If Windows asks for credentials you do not have, the correct fix is to involve the authorized administrator.
Recommended Free Tools
Policy denies elevation
An immediate access-denied response without a consent or credential path points toward UAC or security-policy settings rather than a simple missing click. Capture the prompt behavior and have an administrator review policy.
Best Value
The application requests elevation unnecessarily
A compatibility checkbox or an application manifest can force every launch to request full administrator rights. That setting may be intentional, but it can also reflect an outdated application design. Ask the vendor for a version that follows the least-privilege model when possible.
The task is not actually permitted
Elevation grants the token requested by the application; it does not authorize every operation against every file, service, or organizational setting. A separate access-control rule, ownership restriction, or managed-device policy can still block the action. Treat a new error after elevation as a distinct problem and record its exact wording.
What not to do
- Do not disable UAC as the default fix. UAC prompts and the secure desktop are Windows security controls, and lowering or disabling them weakens protection.
- Do not download replacement executables or “elevation bypass” tools from unverified sources.
- Do not grant administrator rights to an unfamiliar file merely because a game or installer will not proceed.
- Do not change Group Policy or local security policy on a managed computer without approval.
- Do not assume that a successful launch proves the application should always run elevated.
If an administrator approves a controlled diagnostic change to UAC policy, restore the normal setting immediately after testing. A permanent elevation workaround should be documented and justified by the application’s actual requirement.
Verification checklist
After applying a fix, test the original operation once and record the result. A useful checklist is:
- The exact program or command is identified.
- The shell or executable was launched through Run as administrator.
- The expected consent or credential prompt appeared and was handled by an authorized user.
- The task completed without Error 740.
- The application does not remain permanently elevated unless its vendor or administrator requires that configuration.
- Any approved UAC or policy change has been returned to the organization’s normal setting.
If the error returns, repeat the evidence capture rather than cycling through random permission changes. Note what changed between the successful and failed attempts: the executable, shell, account, prompt behavior, Windows build, or policy context. That comparison usually identifies whether the issue is a one-time elevation request, an application manifest, or a policy decision.
Quick Recap
As an optional shortcut after trying the manual steps, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, while also offering settings adjustments, cleanup, privacy checks, vulnerability checks, a real-time boost, file shredding, and an app-crash log. It runs on Windows 11, 10, 8, and 7; its free trial is offered by category for at least two days before a paid subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
