Failed renaming
The renaming operation can fail for a variety of reasons. The built-in validation process attempts to identify common problems before renaming by raising warnings during the preview stage, but it cannot catch every possible issue.
The most common reasons for a failed renaming operation are described below.
File path is too long
The total length of the file path exceeds the system limit. In Windows, the maximum file path length is 260 characters, as defined by the MAX_PATH constant.
As a workaround, you can use the "long path" specification by prepending the file path with \\?\, which effectively raises the maximum path length to 32,767 characters. See Long paths for more information.
Alternatively, shorten the filename or the name of one of its parent folders to bring the total path length within the limit.
Destination file already exists
A file with the target name already exists at the destination, causing a name conflict. There are several ways to resolve this:
- Enable Fix conflicting new names on preview in Preview settings to automatically resolve conflicts by appending a number suffix during preview.
- Use Fix Conflicting New Names from the Options menu to resolve conflicts on demand.
- Manually edit the new name of the conflicting file.
- Rename or move the existing file at the destination to eliminate the conflict.
Source file does not exist
The file listed in the Files pane no longer exists at its original path. This can happen if:
- The file was moved or renamed outside of ReNamer.
- The file's parent folder was renamed first, making the stored path stale.
To fix this, remove the affected items from the Files pane and re-add them using their current path.
File is in use by another program
The file is currently locked by another process and cannot be renamed. Use a utility such as Windows Task Manager or Process Explorer to identify and close the program holding the file. If the file is still being downloaded, simply wait for the download to complete before renaming.
Insufficient privileges
You do not have the necessary permissions to rename the file. If you are not the administrator, contact the owner or admin. If you are the administrator, check the permissions of the containing folder.
Invalid destination path
The new filename contains one or more characters that are not permitted in Windows file paths:
\ / : * ? " < > |
Remove or replace any of these characters in the new name.
Parent path changed earlier in the list
A parent folder of the affected file was renamed earlier in the same renaming operation, which made the file's stored path stale. This can occur when renaming both folders and their contents at the same time.
To avoid this, always rename the contents of a folder before renaming the folder itself. This can be achieved by sorting the Files pane by the Folder or Path column in descending order before running the operation.
For more information, see Renaming folders.