SeaDrive Error "The Cloud Operation was unsuccessful" when trying to delete files/folders

SeaDrive
,
1

Hi there,
I’ve read through a lot of stuff, but this error persists since months for me.

I use SeaDrive on Windows 11 24H2 (and previously on 22H2) and SeaDrive won’t let me delete any files or folders. I always get an error message:

“Error 0x80070185: The cloud operation was unsuccessful”

I’ve already uninstalled SeaDrive completely, deleted the root_folder, rebooted and installed SeaDrive again. Multiple times. I also upgraded SeaDrive permanently and now it’s on the actual version 3.0.11.

The seadrive-gui.log says:

[09/12/24 00:43:06] failed to read request from shell extension: Die Pipe wurde beendet.

The seadrive.log says:

[09/12/24 00:43:17] removing blocks for repo a681afdc-b252-41e9-af6d-d385f88d3d32
[09/12/24 00:43:17] Repo ‘REPO_NAME’ sync state transition from ‘uploading’ to ‘get sync info’.
[09/12/24 00:43:17] Repo ‘REPO_NAME’ sync state transition from ‘get sync info’ to ‘synchronized’.
[09/12/24 00:43:20] Failed to parse path by /$RECYCLE.BIN/S-1-5-21-3118154539-253935935-350606491-1001/$RS2N958
[09/12/24 00:44:13] Failed to parse path by /$RECYCLE.BIN/S-1-5-21-3118154539-253935935-350606491-1001/$RCBAL2X
[09/12/24 00:44:16] Failed to parse path by /$RECYCLE.BIN/S-1-5-21-3118154539-253935935-350606491-1001/$R5KS8B2

This error haunts me since 2023 and I ignored it until now, but I need to get it to work. I’ve read that this bug should have been fixed 2 years ago or so… So… What can I do to solve this issue?

2

Hi,

The cause for failing to delete a placeholder file in SeaDrive is usually due to system issues. You can try to enable periodic scanning feature in Windows Defender. We have some users solve this issue by doing so.

3

Can you explain this a little more in detail?
How is that supposed to help with it?

What else can I do to get rid of this problem?
If I hit “Free Up Space” before deleting a file, it works.
But it doesn’t work with folders.

4

The exact cause is unknown. Some OneDrive users reported the same issue on MS forums and we found the solution there. It’s related to the deletion callback function we register.