Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
Hi, thanks for this wonderful software. I've always used the 32-bit version 2.0.10. Then I wanted to upgrade to the latest version, but now I can't rename any files. I even tried downgrading, but nothing works. The rename operation fails. If I rename manually or with Better file rename, it works. I tried granting all permissions to the software, but nothing. All Metadata settings disabled, Renaming options only force 2 digits for numbers.
The log says FAILED … (Error: Could not copy file, OS Error(2))
Thanks for any help.
Hi nod32,
What OS are you running?
Since downgrading didn't fix the renaming issue, I would assume there may be something wrong with access or access rights - but you already looked at that 🤔
Odd that the other application does work. Odd that the previous version worked, but now no longer seems to work.
Are your files stored local? If not: give that a try (just for the purpose of testing)?
It is a little confusing when it comes to those error numbers, but IIRC OSError means "File not found".
Does the log show anything else like a path and such (I know, its a very limited log)?
Hi, thanks for the prompt reply.
OS is Windows 11.
The log contains the source and destination paths. The files are located on a NAS (QNAP). I tried creating a local folder and it worked.
The strange thing is that the old version renamed the NAS path without any problems, too. I don't know how or what special permissions to assign.
You're welcome 😊
Are you doing anything besides renaming? Like moving the file?
Like settings in this section:
All unselected.
I solved it!
After countless attempts, I deleted the Windows credentials used to access the NAS and logged in again, and voilà! I did it!
Proof that Windows does exactly what it wants... and not what it's told to do.
Thanks for your attention, maybe it will be useful to some users in the future.
I wish you a Happy New Year!
Hi nod32!
Glad to hear that and thank you for posting your fix! 👍
Happy New Year to you too! 😊
