Thanks. The server response to "tags" query misses namespace:

A correct response (as sent by AWS) is:

---

I do not know why it works for you in some versions. It can actually be random to some degree. The 6.3.7 log you have posted does not even include the "tags" query. If you want us to investigate further, please post log that actually shows it.

Sorry for the late reply.
Since the language setting when acquiring the log was Japanese, the log was also output in Japanese.

File: 6.5.5_232xxxxxx93ELKHORDG9@s3.ap-northeast-1.amazonaws.com.log
Line 702

If the language setting is English, it will appear as "Unexpected response to AWS request (Tagging.)" as shown in the screenshot I sent.

※ Would you like me to re-acquire the log in English?

Thanks for your report. Though, did you post the right log files? I do not see the "Unexpected response to AWS request" in any of them.

Hello,
Since around February this year, I have been connecting to and using Wasabi with version 6.3.6 via the S3 protocol. Recently, I noticed that when I try to open the properties of a file or folder, the following error appears, preventing me from opening the properties. (This error did not occur until this summer, and there were no problems.)

Title: Error
Message: Unexpected response to AWS request (Tagging).

I also contacted Wasabi, but they could not identify the issue. After that, I noticed that the behavior differs depending on the WinSCP version.

ver.6.3.6: Cannot open properties due to error *
ver.6.3.7: Can open properties
ver.6.5.5: Cannot open properties due to error

*However, if you upgrade to 6.3.7 once and then revert back to 6.3.6, you are able to open properties.

Environment:
OS: Windows 11 Pro
Protocol: S3 (connected to Wasabi)
Using GUI (Explorer mode)

Please tell me how I can avoid this error.