Error 0x80070522 Required Privilege Not Held: Fix

Error 0x80070522, which reads “A required privilege is not held by the client,” appears when Windows blocks an action because your user account lacks the specific security right needed to perform it. The fix is to run the action as an administrator, adjust the User Account Control (UAC) settings, or grant your account the missing privilege. This guide explains the causes and gives you step-by-step fixes for the most common scenarios.

What This Error Means

Windows uses a security model where every process runs with a set of privileges. A privilege is not the same as a user account type (Administrator vs. Standard User); it is a specific right, such as SeBackupPrivilege (back up files) or SeDebugPrivilege (debug programs). Error 0x80070522 occurs when a program tries to perform an operation that requires one of these privileges, but the process token does not include it. This commonly happens with file operations, registry edits, or service management.

Even if you are logged in as an administrator, Windows often runs programs with a filtered token — a version of your account that has the administrator privileges removed. This is a security feature called User Account Control (UAC). When you right-click an app and choose “Run as administrator,” you get the full token with all privileges. Without that, the action fails with 0x80070522.

Why You Get This Error

The most frequent triggers include:

• Running a program without elevation — the app needs admin rights but you didn’t select “Run as administrator.”
• Modifying files in protected folders — such as C:\Program Files, C:\Windows, or the root of the system drive.
• Using a standard user account — even with the correct password, standard users cannot perform admin-level tasks.
• Group Policy restrictions — an administrator may have removed certain privileges from your user or group.
• Antivirus or security software — some security tools restrict privileges to protect against malware, which can cause false positives.

For example, trying to copy a file into C:\Program Files from a non-elevated command prompt will often produce this error. Similarly, editing the registry with a standard tool without elevation can trigger it.

How to Fix It: Step-by-Step

Try these fixes in order. Most users will resolve the issue with the first one.

1. Run the program as administrator — Right-click the executable or shortcut and select “Run as administrator.” If a UAC prompt appears, click “Yes.” This gives the process the full token with all privileges.
2. Use an elevated command prompt — For file operations, open Command Prompt as administrator (type “cmd” in Start, right-click, “Run as administrator”) and then run your command.
3. Disable UAC temporarily — If you frequently need admin rights for a specific app, you can lower UAC settings. Go to Control Panel > User Accounts > Change User Account Control settings, and drag the slider to “Never notify.” Restart. Warning: This reduces security; re-enable it after troubleshooting.
4. Check your account type — Go to Settings > Accounts > Your Info. If it says “Standard user,” you need an administrator to promote you. If you are an admin, ensure the account is not a child account with parental controls.
5. Take ownership of the file/folder — Right-click the target, Properties > Security > Advanced > Change owner to your account, then grant yourself full control. This is necessary if the object is owned by TrustedInstaller or SYSTEM.
6. Disable antivirus temporarily — Some security suites block privilege escalation. Disable real-time protection briefly and retry. Re-enable it immediately.
7. Use Group Policy Editor (Pro/Enterprise only) — Run gpedit.msc, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment, and ensure your account has the needed privilege (e.g., “Adjust memory quotas for a process”).

Common Scenarios and Specific Fixes

Here are typical situations where the error appears and the exact fix:

• Copying files to C:\Program Files — Use an elevated File Explorer (right-click File Explorer, “Run as administrator”) or move the file via an elevated command prompt.
• Running a batch file that modifies system files — Right-click the .bat file and “Run as administrator.”
• Installing a driver or service — The installer must be run elevated. If it fails, right-click the installer and choose “Run as administrator.”
• Editing the registry — Open Regedit as administrator. If you still get the error, check the specific key’s permissions.
• Deleting a file in a protected folder — You may need to take ownership first, then delete.

What to Do If the Error Persists

If you’ve tried the above and still get 0x80070522, consider these deeper checks:

• Check for malware — Some infections strip privileges to prevent removal. Run a full scan with Windows Defender or a reputable tool.
• Create a new user account — If your profile is corrupted, a new admin account may work. Go to Settings > Accounts > Family & other users > Add someone else to this PC.
• Use System File Checker — Open an elevated command prompt and run sfc /scannow. This repairs corrupted Windows files.
• Reset Windows — As a last resort, you can reset the PC while keeping your files (Settings > Update & Security > Recovery > Reset this PC).

Frequently Asked Questions

Why does this error happen even when I am the administrator?

Because of UAC, even administrators run with filtered tokens unless they explicitly elevate. The error occurs because the process lacks the privilege, not because your account type is wrong.

Can I permanently disable UAC to avoid this?

Yes, but it’s not recommended. Disabling UAC means all programs run with full admin rights, which makes malware more dangerous. Instead, use “Run as administrator” for the specific app.

Is this error dangerous?

No, it’s a security feature. It indicates that Windows blocked an operation to protect your system. It’s not a sign of a virus, though persistent errors could indicate a malware infection.

Does this error appear on Windows 10 and 11?

Yes, it appears on both. The fixes are identical.

What if I don’t have an administrator password?

You’ll need to contact the person who set up the computer. If it’s your own PC and you forgot the password, you may need to reset it via Microsoft account recovery or a password reset disk.

Preventing Future Occurrences

To minimize this error in daily use:

• Always install software by right-clicking the installer and choosing “Run as administrator.”
• Keep your user account as a standard user for everyday tasks, and use an admin account only when needed.
• If you frequently need admin rights for a specific app, create a shortcut and enable “Run as administrator” in its properties (Compatibility tab).
• Regularly run Windows Update to ensure your system has the latest security patches.

By understanding that this error is a privilege issue, not a permission issue, you can resolve it quickly and safely.

Related

• Fix WHEA Uncorrectable Error Windows 10
• Fix Android Phone Not Showing Up on Mac
• Fix Local Security Authority Protection Is Off in Windows 11