Error 0x80070052 on Windows 10 typically means Windows cannot copy a file to a destination because the path is too deep or the file name is too long. The most direct fix is to shorten the file path or use a different copy method, such as robocopy, to bypass the limit.
What Causes Error 0x80070052?
This error is tied to the MAX_PATH limitation in Windows, which restricts the full path (including drive letter, folders, and file name) to 260 characters. When you copy, move, or extract files that exceed this limit, Windows returns error 0x80070052. It often appears when extracting a deeply nested ZIP archive, syncing a large folder to cloud storage, or copying a project with many subdirectories.
Another common trigger is a corrupted or locked file, but the path length issue is the most frequent. The error message itself may say “The file name(s) would be too long for the destination folder.” That message is a clear indicator of the path-length problem.
How to Fix Error 0x80070052
Try these fixes in order, from simplest to most advanced. Stop once the copy or extraction succeeds.
- Shorten the file path. Move the folder to a higher level, like C:\Temp, and rename folders to shorter names. For example, change C:\Users\John\Documents\Projects\2024\ClientReports\Final\Draft to C:\Temp\R1.
- Enable long paths in Windows 10. Open the Group Policy Editor (gpedit.msc) and go to Computer Configuration > Administrative Templates > System > Filesystem. Double-click “Enable Win32 long paths,” set it to Enabled, and restart. This allows paths up to 32,767 characters for apps that support it.
- Use robocopy. Open Command Prompt as Administrator and run:
robocopy "source" "destination" /E /COPYALL. Robocopy handles long paths better than File Explorer. - Extract ZIP files with 7-Zip. 7-Zip can extract files with long paths without the error. Right-click the ZIP, choose “7-Zip > Extract Here.”
- Check for file locks. If the error persists, close any program that might be using the file (like a document editor or media player). You can also use Process Explorer to find which process has the file open.
How to Avoid the Error in the Future
Prevention is easier than fixing. Adopt these habits:
- Keep folder structures shallow. Instead of nesting folders five levels deep, create a flatter structure.
- Use short, descriptive folder and file names. Avoid long sentences as file names.
- When creating ZIP archives, avoid including the full path in the archive. Use “Relative path” in WinRAR or 7-Zip.
- If you use cloud sync (OneDrive, Google Drive), be aware that they have their own path limits. Keep synced folders near the root of the drive.
Alternative Methods to Copy Files with Long Paths
Besides robocopy, there are other tools that can handle long paths:
- PowerShell with the
\?\\prefix. Example:Copy-Item -Path '\\?\C:\long\path\file.txt' -Destination '\\?\D:\short\file.txt'. - Total Commander – a file manager that supports long paths natively.
- Far Manager – another file manager that bypasses the limit.
- Windows Subsystem for Linux (WSL) – you can use Linux commands like
cpto copy files, which do not have the 260-character limit.
Common Misconceptions About Error 0x80070052
Many users think this error is caused by a corrupted drive or a virus. While those can cause copy errors, 0x80070052 is specifically the “path too long” error. The error code is consistent across Windows versions. Another misconception is that enabling long paths in Group Policy immediately fixes all apps. It only works for apps that are explicitly designed to support long paths. Older apps (like some built-in utilities) still fail.
When to Use a Different Error Fix
If you see error 0x80070052 but the path is clearly short, then the issue might be a file permission problem. In that case, try:
- Running the copy as Administrator.
- Taking ownership of the destination folder.
- Disabling antivirus temporarily (but re-enable it immediately after).
If the error is accompanied by a message about the destination being on a network drive, check the network connection and permissions.
Frequently Asked Questions
Can I simply delete the long path files?
Yes, but you may need to use the same tools. In File Explorer, you might not be able to delete a file with a long path. Use Command Prompt: del \\?\C:\full\path\file.txt or robocopy with an empty folder to mirror-delete.
Does error 0x80070052 mean my hard drive is failing?
No. It is almost always a path length issue. If you suspect drive failure, check the SMART status or run chkdsk, but the error code itself is not a hardware warning.
Will enabling long paths slow down my computer?
No. It only changes a system policy. Performance impact is negligible.
Why does this happen with ZIP files specifically?
ZIP archives can store paths up to 65,535 characters. When you extract, Windows tries to create those long paths and hits the 260-character limit. The archive itself is fine; the extraction process is the problem.
Is there a way to make File Explorer show long paths?
No, File Explorer itself has the 260-character limit. Even with long paths enabled, Explorer may still truncate or fail. You need a third-party file manager for full support.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Slow Internet Lag on Samsung Galaxy Note
- iOS 18 Safari Not Working? Fixes That Help
- How to Check Your Linux Kernel for Spectre
- iPhone Safe Mode: How to Enable or Disable It
- How to Get iOS 17 on iPhone X (Safe Methods)
- Fix Gmail IMAP Error in Outlook: Step-by-Step