Notes on running Bulk Rename Utility on modern Windows, plus fixes for common installation and configuration problems.
Bulk Rename Utility runs natively on both Windows 10 and Windows 11 without special compatibility settings for the vast majority of users. A few things to keep in mind:
If you rename files in protected system folders or want to enable Explorer right-click integration, launch the app with administrator rights.
Windows may show a first-run publisher warning for smaller independent applications. This is standard for many freeware tools and isn't unique to this one.
On very high-resolution displays, older-style desktop applications can sometimes appear small; Windows display scaling settings can be adjusted per-app if needed.
There are no widely reported feature-breaking incompatibilities with current Windows 11 releases.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Installer blocked or deleted immediately | Antivirus heuristic flag, or the file wasn't downloaded from the official source | Re-download from the developer's own site (see our Download & Compatibility page), then allow it through your antivirus if you're confident of the source. |
| "Access denied" during install | Installer wasn't run with sufficient permissions | Right-click the installer and choose "Run as administrator." |
| App won't open after install | Incomplete or interrupted installation | Uninstall, redownload a fresh copy, and reinstall. |
| Right-click "Bulk Rename" option missing | Explorer integration wasn't selected during setup | Re-run the installer and enable the shell-integration option, or enable it from within the app's settings. |
If you run several file-management tools that add their own Explorer right-click entries, menus can get crowded. Disabling unused shell extensions from other tools can help keep things tidy.
If preferences reset each time you open the app, check that the account running it has write access to its settings location, and avoid running it from a read-only or temporary folder.
This is almost always caused by a rule ordering issue rather than a bug — rules apply top-to-bottom, so reordering them in the rules list often resolves it.
The portable/ZIP version may store its settings alongside the executable rather than in your user profile — keep that folder together if you move it between machines.