I'm not sure this is the right place to report this,
When working with the Cloud Filter API, I encountered an issue that only reproduce on Win10 2004.
When user is deleting a 0KB sparse placeholder file, in the CF_CALLBACK_TYPE_NOTIFY_DELETE callback, if passing an unsuccessful CompletionStatus(e.g. STATUS_UNSUCCESSFUL) to the platform, in theory this should fail the user's delete action and prevent the file from being deleted, but on Win10 2004, file got deleted anyway.
On Win10 versions before 2004, it behaves as expected, error message popup, saying "The cloud operation is unsuccessful", and the file is left untouched.
The minimal changes to reproduce this issue based on the official CloudMirror sample can be found at:
https://github.com/wangfu91/Windows-classic-samples/pull/1/files
This seems like a bug of Win10 2004, very much like the ICopyHook bug in Win10 1803.