It looks like if when FreeFileSync decides to remove a file from a Google Drive folder, it does not check weather it is the owner of the file (and google drive throws an error if you are not). I think FreeFileSync may try to become the owner of the file before trying to delete (as APIs for taking ownership are documented):
https://stackoverflow.com/questions/37479170/google-drive-api-transfer-ownership-as-delegated-admin
The scenario is quite common, as when you add a folder that is shared with you in Google drive, it's common to see there files created by other users (thus, having owners different than yourself).
Fails to remove files on Google Drive folders when user not the owner
- Posts: 1
- Joined: 28 Nov 2019
- Site Admin
- Posts: 7212
- Joined: 9 Dec 2007
Fixed! Shared files in Google Drive are like symbolic links as far as ownership is concerned. FFS shouldn't try to delete the target (which isn't allowed anyway), but just remove the link, which is also what the Google Drive web interface does.
https://www.mediafire.com/file/xej2jxxus7t7xkd/FreeFileSync_10.19_%5BBeta%5D_Windows_Setup.exe
https://www.mediafire.com/file/xej2jxxus7t7xkd/FreeFileSync_10.19_%5BBeta%5D_Windows_Setup.exe
- Posts: 2
- Joined: 20 Sep 2019
"Me too!" - thanks for fixing. That was confusing for a while there. TIL Windows 10 can have duplicate file names in a folder.