Microsoft Windows Error Code 0x80070011: How to Fix It
Medium 15-30 minutes Medium Severity
Verified June 2026
- Error Code
- 0x80070011
- Brand
- Microsoft Windows
- Product Type
- hresult
- Severity
- Medium
- DIY Difficulty
- Medium
- Estimated Fix Time
- 15-30 minutes
Ad
Tools You'll Need
- Administrator access
- Command Prompt
How to Fix Error Code 0x80070011
-
Identify the Cross-Device Operation
-
Use Copy and Delete Instead of Move
Ensure you have enough space on the destination drive before pasting. -
Check File Permissions
Be cautious when modifying permissions; incorrect changes can cause access issues. -
Run Disk Check on Both Drives
Running chkdsk may take a long time on large drives. Do not interrupt the process. -
Use Command Line for Rename/Move
Double-check paths to avoid accidental data loss. -
Check for Third-Party Conflicts
Disabling security software temporarily may expose your system to risks. Re-enable immediately after testing.
Ad
When to Call a Professional
If the error persists after trying all steps, there may be underlying hardware issues with the drives (bad sectors, failing disk). Consider consulting a data recovery specialist or IT professional to avoid data loss.Frequently Asked Questions
What does error 0x80070011 mean?
It means ERROR_NOT_SAME_DEVICE: you're trying to move or rename a file across different storage volumes (e.g., from C: to D:), which Windows does not support for certain operations.
Can I move files between drives in Windows?
Yes, but you must use copy and delete instead of move. Moving files between different drives requires a copy operation because the file system cannot simply update pointers across volumes.
Does this error affect external drives?
Yes, it commonly occurs when moving files between internal and external drives, or between different partitions on the same physical disk.
How do I fix error 0x80070011 permanently?
This error is by design; you cannot permanently disable it. The solution is to always use copy/delete for cross-device operations. No registry or system tweak can bypass this limitation safely.
Will a system restore fix this error?
No, because it's not caused by a system corruption; it's a normal behavior. System restore won't help. Focus on changing your file operation method instead.