Why Does File Transfer Fail With Error 0x80010135 on Windows?

[lindamary]

I’m trying to move large files across systems, but error 0x80010135 keeps appearing. What triggers this error, and are there reliable fixes?

 

[rebeccareed]

This error is super common and usually tied to path length limits in Windows. Even though newer versions support long paths, a lot of apps and file operations still choke if the full file path goes over ~260 characters. Large folders with deep nesting are the usual trigger.

 

[AnnP111966]

Yep, path length is the main culprit. I see error 0x80010135 all the time in enterprise environments when users try copying project folders with tons of subfolders. A quick workaround is compressing the folder into a ZIP first, then extracting it at the destination.

 

[ArthurMex]

I ran into this moving files from my PC to a NAS. Renaming folders to shorter names helped immediately. I didn’t even realize how long some of the directory names were until I checked. Windows Explorer is surprisingly bad at warning you beforehand.

 

[captainghost]

If you’re comfortable with tools, PowerShell or Robocopy handles this better than File Explorer. I’ve moved files that Explorer refused to copy. It’s not exactly beginner-friendly, but it’s reliable if you move large files often.

 

[TaylorTravels]

There is a registry/group policy option to enable long paths, but I’d be careful. I enabled it once and some older apps started acting weird. It fixes error 0x80010135 for copying, but compatibility can be hit or miss depending on what software you use.

 

[jimmy]

Another angle: if you’re transferring across systems over a network, sometimes SMB settings or network permissions make the error show up more often. I fixed it by copying locally first, then transferring in chunks instead of one massive folder.

 

[rebeccareed]

I also noticed this error more when moving files to external drives formatted as FAT32. Large files + long paths = instant failure. Reformatting to NTFS solved it permanently for me.

 

[Lisa]

Quick question for those who fixed it: does enabling long paths completely remove error 0x80010135, or is it still safer to shorten folder names? I’m worried about breaking legacy apps.

 

[Emmawoods]

Short answer: shortening paths is the safest fix. Enabling long paths helps, but it doesn’t guarantee Explorer or third-party apps will behave properly. In support environments, we always recommend flattening folder structures before moving data.

 

[jameswill8520]

To sum it up, error 0x80010135 is usually triggered by long file paths, deep folder nesting, or filesystem limitations. Reliable fixes include shortening folder names, compressing files, using tools like Robocopy, or changing file systems. It’s annoying, but once you know the cause, it’s pretty manageable.