Fix 0x800710e0 Operator Administrator Refused

If you see error 0x800710e0 with the message “The operator or administrator has refused the request” when trying to delete, move, or manage files, it usually means Windows permissions are blocking the action. This guide explains why it happens and gives you step-by-step fixes, from taking ownership of the file to adjusting User Account Control settings.

What Is Error 0x800710e0?

Error 0x800710e0 is a Windows error code that translates to ERROR_REFUSED. It appears when the operating system denies a file operation because the current user account does not have the required permissions. The full message often reads: “The operator or administrator has refused the request.”

This error commonly occurs in Windows 10 and Windows 11 when you try to:

• Delete a file or folder
• Move or copy files to another drive
• Change file attributes (like read-only)
• Open files from a network location or external drive

The root cause is almost always a permission mismatch—either the file is owned by another account, the folder has restrictive ACLs, or a security policy is blocking the action.

Why Does the Error Happen?

Windows uses a security model where every file and folder has an owner and a set of permissions. When you attempt an operation, Windows checks if your account (or the group your account belongs to) has the right to do it. If not, it returns an error like 0x800710e0.

Common triggers include:

• File ownership: The file was created by another user account (e.g., an old profile) and the current account lacks explicit rights.
• Read-only attribute: Some files, especially from external sources, are marked read-only, which can cause deletion failures.
• User Account Control (UAC): If UAC is set to a very high level, even administrators may be denied certain operations without elevation.
• Network or removable drives: Files on a network share or USB drive may have permissions from the source machine that conflict.
• Group Policy: In corporate environments, a policy may explicitly deny certain file operations to non-administrators.

Fix 1: Take Ownership of the File or Folder

The most reliable fix is to take ownership of the file/folder and grant your account full control. Here’s how:

1. Right-click the file or folder and select Properties.
2. Go to the Security tab and click Advanced.
3. Next to Owner, click Change.
4. In the “Enter the object name to select” box, type your Windows username (e.g., Administrator or your account name), then click Check Names and OK.
5. Check the box Replace owner on subcontainers and objects if you want to take ownership of everything inside a folder.
6. Click OK to close the Advanced Security window.
7. Back in the Security tab, click Edit, select your account, and check Full control under Allow.
8. Click Apply and OK.

If you don’t see your account in the list, click Add and type your username, then give it Full control.

Fix 2: Use the Command Line to Take Ownership and Grant Permissions

If the GUI method fails (sometimes it does when the file is locked), you can use Command Prompt or PowerShell as an administrator:

1. Press Windows + X and select Terminal (Admin) or Command Prompt (Admin).
2. Type the following command to take ownership (replace C:\path\to\file with your actual path):

takeown /f "C:\path\to\file" /r /d y

This command takes ownership recursively (/r) and automatically answers yes (/d y) to any prompts.

3. Then grant your account full control:

icacls "C:\path\to\file" /grant %USERNAME%:(F) /t

The /t flag applies the permission to all subfolders and files. After both commands, try the original operation again.

Fix 3: Disable Read-Only Attribute

If the file is marked read-only, you may get error 0x800710e0 when trying to delete or modify it. To clear the attribute:

1. Right-click the file and select Properties.
2. Under the General tab, uncheck Read-only.
3. Click Apply and OK.

If the attribute is greyed out, the file may be on a network share or a write-protected drive. For a USB drive, check the physical write-protect switch.

Fix 4: Adjust User Account Control (UAC) Settings

In some cases, UAC can block file operations even for administrators. While it’s not recommended to disable UAC permanently, you can lower it temporarily to see if it resolves the error:

1. Press Windows + R, type regedit, and press Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
3. Find EnableLUA and set its value to 0 (this disables UAC).
4. Restart your computer.

After restarting, try the operation. If it works, you can re-enable UAC by setting EnableLUA back to 1. Note that disabling UAC reduces system security, so only do this temporarily and revert it after the fix.

Fix 5: Check Group Policy or Security Software

If you’re on a work or school computer, a Group Policy might be blocking the operation. You can check with your IT admin. On a personal computer, third-party security software (like antivirus or ransomware protection) can sometimes interfere with file operations. Temporarily disable such software (if you trust it) and try again.

Also, if the file is on a network drive, make sure you have write permissions on the server. On a home network, try copying the file to your local drive first, then modify it there.

Frequently Asked Questions

Can I use this fix for files on an external hard drive?

Yes, but the external drive must be formatted with NTFS or exFAT. If it’s FAT32, Windows doesn’t store permissions, so the error is less likely—but if it happens, it’s usually because the drive is write-protected or the file is in use.

Will taking ownership break anything?

Taking ownership of a system file (like in C:\Windows) can cause issues if you modify or delete it. Only take ownership of files you specifically need to fix. For personal files, it’s safe.

What if I get “Access Denied” when trying to take ownership?

Make sure you are running the command prompt as administrator. Also, if the file is locked by another process, close all programs that might be using it (like a media player or editor).

Does this error happen on Windows 7 or 8?

Yes, error 0x800710e0 can appear on older Windows versions too. The fixes are essentially the same, though the menus may look slightly different.

Is there a way to avoid this error in the future?

Use a standard user account for daily tasks and only use an administrator account when needed. Also, avoid storing files in protected system folders like Program Files unless necessary.

What if none of these fixes work?

If the error persists, the file may be corrupted or the drive may have errors. Run chkdsk /f on the drive (as administrator) to check for disk issues. If it’s a system file, consider running System File Checker (sfc /scannow).

Related

• Transfer SIM or eSIM from iPhone to iPhone: Step-by-Step
• RGB Software Causing Windows 11 Crashes?
• Chromebook Keyboard Lighting: Brightness, Colors & Animation Limits