Seafile Drive Client (2.0.12) deletes files instead of saving/syncing

Hello,

me and some colleagues have the problem that the Seafile Drive Client deletes files automatically after saving (under Windows 11).
For example, after adding changes to file “XYZ.pdf” and clicking the Save-Button in the PDF-application, the client announces “Repo XYZ is synchronized - deleted file XYZ.pdf”. In the repo folder, the file is still stored locally and the syncing-symbol appears next to it. But the file never gets uploaded, and the other users of the repo cannot see the file in their SeaDrive anymore.
Right now, the solution seems to be to restart the client anytime this happens. Afterwards, the synchronization starts. Additionally, we save the “deleted” file to any local folder (not connected to SeaDive) to avoid a complete loss of the file.

I checked the log-file, but there is nothing suspicious in there (from my point of view):
[10/24/22 10:38:19] Repo ‘name’ sync state transition from ‘synchronized’ to ‘committing’.
[10/24/22 10:38:19] All events are processed for repo token.
[10/24/22 10:38:19] Repo ‘name’ sync state transition from ‘committing’ to ‘uploading’.
[10/24/22 10:38:19] Upload with HTTP sync protocol version 2.
[10/24/22 10:38:19] Transfer repo ‘token’: (‘normal’, ‘init’) → (‘normal’, ‘check’)
[10/24/22 10:38:19] Transfer repo ‘token’: (‘normal’, ‘check’) → (‘normal’, ‘commit’)
[10/24/22 10:38:19] Transfer repo ‘token’: (‘normal’, ‘commit’) → (‘normal’, ‘fs’)
[10/24/22 10:38:19] Transfer repo ‘token’: (‘normal’, ‘fs’) → (‘normal’, ‘data’)
[10/24/22 10:38:19] Transfer repo ‘token’: (‘normal’, ‘data’) → (‘normal’, ‘update-branch’)
[10/24/22 10:38:19] Transfer repo ‘token’: (‘normal’, ‘update-branch’) → (‘finished’, ‘finished’)
[10/24/22 10:38:19] removing blocks for repo token
[10/24/22 10:38:19] Repo ‘name’ sync state transition from ‘uploading’ to ‘get sync info’.
[10/24/22 10:38:19] Repo ‘name’ sync state transition from ‘get sync info’ to ‘synchronized’.

Additional info: I and another colleague, who had this problem, activated BitLocker a few weeks ago. Might there be any conflict between BitLocker and SeaDrive?

Looking forward to any helpful ideas/suggestions.
Kind regards,
Jannik