| Previous | Next |
| ERROR_OPEN_FAILED | ERROR_DISK_FULL |
ERROR_BUFFER_OVERFLOW
ERROR_BUFFER_OVERFLOW (111, 0x0000006F) is a Win32 system error whose defined message is “The file name is too long.” Despite its name, this code is commonly about a path-length limit rather than a generic memory-buffer overflow.
Legacy path limits
Many Windows file APIs historically use MAX_PATH, usually 260 characters including the terminating null character. A deeply nested directory, a long checkout location, or several long path components can therefore fail even when each individual file name looks reasonable.
Extended-length paths
Unicode file APIs can support much longer absolute paths when an extended-length prefix such as \\?\ is used. This form changes path parsing rules: forward slashes and relative components such as . and .. are not accepted in the same way. Relative paths remain constrained by the traditional limit.
Practical fix
- Log the complete path and its character count before the failing call.
- Use Unicode APIs consistently.
- Reduce unnecessary directory depth when a component of the path is under the application’s control.
- Verify that the particular Windows version, application configuration, and API being used support the chosen long-path approach.
See Microsoft documentation about maximum path length limitations and CreateFile.
Looking for a different code? Search another status or error code.