Filbot (Windows APP-store) Admin rights

[casperse]

Hi

I keep getting a confirmation prompt when I process files? (This wasn't a problem before so maybe a update?)
I have to say yes to delete each left over directory.

Normal way for me to fix this would be to edit properties on shortcut to run as Admin.
BUT since this is from app-store there is no installation folder and there is no option to run as Admin
The users under security have admin rights, but Filebot keeps asking me for each and every folder (+100 folders to delete takes forever)

Best regards
Casperse

[rednoah]

Can you take a screenshot? I haven't managed to get any such confirmation dialog on my test setup.

Running anything as admin is generally not a good idea, and this might be the reasons why you're getting the confirmation dialogs, if files are somehow owned by admin because they've previously been touched by admin.

Do you get the same sort of issues if you process newly created test files on your Desktop?

Nothing has changed in this regard for many versions. Not sure how to fix it if I can't reproduce it. Also, Store apps can't be run as admin, so no easy work around neither.

[BDS369]

Hello,

I have just now encountered this issue.

Here are some screenshots:


https://imgur.com/a/27FQqMn



Then, after clicking continue I see this:


https://imgur.com/a/CaJcI0T

After clicking yes on this prompt, the file is still not renamed.

This is a windows 10 system - and I am running a licensed copy that was purchased through the Microsoft Store.
Its not on my account - on a friends.

Please let me know what we can try to resolve.

Thanks

[rednoah]

Why do your files need admin permissions? Typically, in the Windows world, admin permissions are only required when modifying system files for security reasons. I'd probably start by fixing the permissions so that your user has access to your own files. That's also a good chance that the permissions dialog is misleading, especially if you're processing files on a remote file system where the server-side ultimately decides what you can and cannot do.


You can try to launch FileBot via the filebot command. That'll launch FileBot with Windows Move / Copy Dialog native integration disabled. It probably won't work, but you might get a better error message from FileBot directly.