Recommended sequence: Back up the source, select only intended items, enable one rule at a time, inspect all proposed names, verify uniqueness, apply on a small batch, and then scale up.
Pre-rename checklist
- Copy important files to a separate backup directory.
- Confirm you are in the correct Windows folder and that the right items are selected.
- Disable unused rule panels and choose only the needed transformation.
- Check new names for duplicates, invalid characters, and unintended extension changes.
- Check hidden files, folder operations and recursive scanning.
- Apply to a few copies and open files afterward to validate.
- Record the before/after mapping for rollback.
Renaming files can break links, scripts, playlists, shortcuts and external references. On network shares and synchronized folders coordinate changes with other users.
Detailed troubleshooting
Preview file renames before applying
The New Name column is a safety check showing expected changes before any filesystem operation.
Undo a bulk rename operation
BRU offers mechanisms for reverting some recent renames, but recovery should be tested before a large or critical batch.
Prevent duplicate filenames during batch rename
A batch must produce unique target names in the same directory to avoid conflicts.
Create a backup before renaming 1000 files
Keep a verified copy or versioned backup before a batch that affects many files or nested directories.
Test a renaming rule on three sample files
A small rehearsal exposes unexpected case changes, extension modifications and duplicate results early.
Keep file extensions unchanged
Most BRU name transformations change the filename stem; leave Extension rules inactive to preserve the recognized type.
More safety and troubleshooting articles are available in the safety topic library.