I figured out a different workflow where I can use the Win10 version across my network. I can perform the rename operation on the same server network share that the original file is located on (and you're right that it's simply a rename and not a copy as long as the share doesn't change) and then ...

Thanks for your reply. If I use FileBot on the server to rename a file, it is an instant file move unless the file is being renamed across drives. However, Windows 10 sees network shares on the server, not drives. So if I use filebot on Windows 10 to rename a file between shares like this: \\server ...

Same issue here. Been running FileBot for a year on my Windows Server 2016 Essentials Media Server and Windows 2012 R2 Essentials before that. I originally installed with the Windows .EXE-based Installer package, but switched to the choco package manager and am running this version: FileBot 4.7.9 ...