Issue with desktop.ini somehow forcing filenames to revert after renaming

nc15
#1

Using Nextcloud in Snap at version 15.0.7, I have this weird issue for one user on Windows 10 LTSB 2016 (which we tried after she had this issue in regular Windows 10 Pro), wherein if she changes a filename and moves the file between folders it reverts back to the previous name. Tests showed this only occurs after the Nextcloud client is installed, and I found that the desktop.ini in the container folder has the rename, instead of the folder itself catching the rename.

https://answers.microsoft.com/en-us/windows/forum/windows_10-files-winpc/desktopini-created-instead-of-a-folder-renaming/b8ba52aa-f07a-44b0-aae0-7958083d04f0

I saw that apparently this is ignored if the folder is not read-only but it seems Windows 10 re-inforces read-only, or Nextcloud does, because the entire Nextcloud folder keeps regaining the Read Only aspect.

Is there a reason for Nextcloud folder on the client machine to have the Read Only attribute set? This is oddly a new change (this user was on windows 10 and renaming files and having it stick without problem prior to very recently), so I don’t know if it’s an odd bug with the way the client interacts with explorer, or what specifically it may be.

Any help is appreciated.

#2

How is she doing these operations? Web interface, mounted webdav drive, just in Windows Explorer itself and letting the client try and sync the changes, etc.