You are not logged in.
The beta dated 29-11-2020 has a problem: It cannot rename some files (error reported: Access is denied).
But I can rename the same file using the FreeCommander (a freeware file manager).
Here are some factors that may be relevant:
I select files in FreeCommander and then use the send to > ReNamer context menu of FreeCommander.
That way I can pass all selected files to ReNamer as argument.
This has been working, but the beta started giving problem.
To install all ReNamer betas, I simply unzip to this folder:
C:\Program Files (x86)\Util\ReNamer
Each time, the latest beta replaces the earlier files.
I tried out the regular ReNamer, which is available as installer (as opposed to a zip).
The installer automatically found the folder where the beta was unzipped, and installed itself.
(I did not have to specify the path.)
What could be the issue?
Last edited by narayan (2020-12-05 13:19)
Offline
It sounds like a selective scrutiny by the many components of Windows Security.
They are particularly sensitive to new binary code, such as Beta versions, because the security components have not yet learned enough about them from all the Windows users out there, i.e. the reputation-based scrutiny.
Try playing with settings of Windows Security, User Account Control (UAC), Controlled Folder Access.
Offline