Files Won't Copy On Windows? Fix - 0x80004005

Windows is blocking your file transfer with error 0x80004005, even though you are logged in as an administrator. This is almost always caused by a permissions ownership conflict where your user account lacks the specific rights to modify the target directory.

Why this happens

Your user profile does not have explicit ownership of the target folder, causing Windows to restrict write operations for security reasons. Taking ownership resets these access rights to your current account.

What you'll need

You will need an account with administrative privileges to modify folder security settings and access the Command Prompt.

Steps

1. 01
   Right-click the destination folder, select Properties, click the Security tab, and click Advanced.
2. 02
   Click Change next to Owner, type your username in the box, click Check Names to autocomplete it, and click OK.
3. 03
   Check the box labeled Replace owner on subcontainers and objects, then click Apply and OK.
4. 04
   If the error persists, return to the Security tab, click Edit, select your username, check the box for Full Control, and click OK.
5. 05
   To rule out system file corruption, search for cmd in the Start menu, right-click it, and select Run as administrator.
6. 06
   Run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow to repair system image integrity, then restart your computer.

Still not working?

If you are attempting to copy files to a network drive and the above steps fail, ensure your VPN connection is active. Windows often throws 0x80004005 when it loses a secure handshake with a mapped network location, even if the folder properties appear correct.

Frequently asked questions

Will changing ownership delete my existing files?

No, taking ownership simply updates the access control list so your account has permission to write to that folder. It does not touch or remove the files inside.

Is this error related to a virus or malware?

Usually no. Error 0x80004005 is a generic access denied message typically triggered by Windows security policies or corrupt system files rather than malicious activity.

Subscribe for fast, no-fluff fixes and best settings guides

For the games, phones, and apps you actually use - every common error, crash, and "how do I…" answered in under three minutes.

Subscribe on YouTube →