i have a howto guide, where i suggest possible workarounds.
https://forum.rclone.org/t/rclone-exe-is-a-virus-workarounds/26223
run rclone inside WSL.
notice that the dir is using windows file system /mnt/c/data/rclone
wsl rclone copy /mnt/c/data/rclone/zork.txt wasabi01:zork --config=/mnt/c/data/rclone/rclone.conf -vv
2023/02/13 10:42:31 DEBUG : rclone: Version "v1.61.1" starting with parameters ["rclone" "copy" "/mnt/c/data/rclone/zork.txt" "wasabi01:zork" "--config=/mnt/c/data/rclone/rclone.conf" "-vv"]
2023/02/13 10:42:31 DEBUG : Creating backend with remote "/mnt/c/data/rclone/zork.txt"
2023/02/13 10:42:31 DEBUG : Using config file from "/mnt/c/data/rclone/rclone.conf"
2023/02/13 10:42:31 DEBUG : fs cache: adding new entry for parent of "/mnt/c/data/rclone/zork.txt", "/mnt/c/data/rclone"
2023/02/13 10:42:31 DEBUG : Creating backend with remote "wasabi01:zork"
2023/02/13 10:42:31 DEBUG : zork.txt: Need to transfer - File not found at Destination
2023/02/13 10:42:31 INFO : S3 bucket zork: Bucket "zork" created with ACL ""
2023/02/13 10:42:31 DEBUG : zork.txt: md5 = c4ca4238a0b923820dcc509a6f75849b OK
2023/02/13 10:42:31 INFO : zork.txt: Copied (new)
2023/02/13 10:42:31 INFO :
Transferred: 1 B / 1 B, 100%, 0 B/s, ETA -
Transferred: 1 / 1, 100%
Elapsed time: 0.9s