Skip to content

Check how to fix "Error 0x80070522: A required privilege is not held by the client" when you create/copy/move/edit files in Windows 10 File Explorer.

Recently, we came across a strange error on our Windows 10 Pro system. This was strictly the File Explorer related error in which we can’t create/copy/move/modify files under system root drive (usually C:). Whenever we try to perform any of these operations, following message appear:

An unexpected error is keeping you from creating the file. If you continue to receive this error, you can use the error code to search for help with this problem.

Error 0x80070522: A required privilege is not held by the client.

FIX Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

With that message, click on Try Again has no effect in the situation. If you also receive this error, the first step to fix it should be of running System File Checker (SFC) There is a strong possibility that corruption in some system file is causing this. Even if running SFC doesn’t helps, go ahead with additional fixes mentioned below.

FIX : Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

FIX 1 – Using File Explorer

1. Right click on your system root drive in File Explorer and select Properties.

FIX Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

2. Next, in the properties window, switch to Sharing tab. Click Advanced Sharing button.

FIX Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

3. Under Advanced Sharing window, check Share this folder and click on Permissions.

FIX Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

4. Then in permissions window, make sure Everyone is listed under Group or user names section. If it is not present there, click Add and type Everyone, select check names and then click OK. Now check Full Control, Change and Read options to provide full control to ‘Everyone‘.

FIX Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

Click Apply followed by OK and in this way close File Explorer. Restart File Explorer using Task Manager and check the status of issue, it should no longer persist.

FIX 2 – Using Registry Editor

Registry Disclaimer: The further steps will involve registry manipulation. Making mistakes while manipulating registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point first.

1. Press W8K + R and put regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here). Click OK.

Windows 10 Registry Editor

2. In the Registry Editor window, navigate to following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

FIX Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

3. In the right pane of System key, look for the registry DWORD (REG_DWORD) named EnableLUA which should be corresponding to Value 1 as its Data. Double click on the DWORD to modify its value:

FIX Error 0x80070522: A Required Privilege Is Not Held By The Client In Windows 10

4. Now In Edit DWORD Value box, set the Value data as 0 and click OK. Close Registry Editor and reboot. After restart, the issue should be fixed.

Hope this helps!


Facebook Google+ Twitter

5 Comments

  • Hi,
    I wonder if you would be so kind as to advise how I fix this annoying problem
    When I try to send emails I get this error message::
    Technical details of permanent failure:
    Google tried to deliver your message, but it was rejected by the relay smtp.talktalk.net [62.24.202.43].

    The error that the other server returned was:
    500 5.7.0 UbNlbcY6HgKst Authentication Denied (TT320)

    I literally have to turn of my laptop and leave it for around 30 minutes before turning it back on and then, sometimes, the email is sent.

    I am not very pc savvy so am a total loss as to what the issue is as it happens with lots of different recipients.
    Please keep any advice and instructions very simple as my knowledge of pc speak is very limited.

    Thanks

    Paul

  • Thank you so much for this article. I’m a lesser IT Professional who had tried everything under the sun up to and including a Windows Refresh (Keep Files), which managed to change the error enough that googling the new error led me to this article I was not finding before. The registry edit fixed my issue.

  • Kapil Arya

    ^^ Glad we could help :)

  • So, everybody can see my files on entire network?

  • Kapil Arya

    ^^ FIX 1 seems wise for standalone machines only. If you’re on domain connected system, you should go ahead with FIX 2 only 😊

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    What's New


    Recent Comments

    • Kapil Arya : ^^ You're always welcome and I'm doing well 😊 It is the read...

      8 hours ago

    • miracle lady : Good morning from Nigeria kapil, I've been going through som...

      17 hours ago

    • ifeanyi anya : Thanks, I think I will manage it since it is not affecting t...

      17 hours ago

    • Kapil Arya : ^^ Thanks a lot for your feedback 😊...

      18 hours ago

    • Kapil Arya : ^^ Glad we could help 😎...

      18 hours ago

    • henry : Step 1 helped me to solve this issue, thank you very much!...

      24 hours ago