Japanese characters and later are not output in the file path of the Scan Log.

[Yukinobu]

Hi,

I placed a test txt file as shown below and let Scan Backup detect it.


No strings after Japanese characters are output in the file path.


I also checked the log file itself, but it is the same, and it seems that characters are not output in the first place, as shown below, rather than being garbled, etc.

Code: Select all

[09.07.2024 19:06:56.312]   <108> Warning (3)    Threat found. Antivirus output: ----------------------------- Threat information ------------------------------
[09.07.2024 19:06:56.312]   <108>    Info (3)    Threat                  : Virus:DOS/EICAR_Test_File
[09.07.2024 19:06:56.312]   <108>    Info (3)    Resources               : 4 total
[09.07.2024 19:06:56.312]   <108>    Info (3)        file                : C:\VeeamFLR\testwin2022_5047f966\Volume1\Users\Administrator\Downloads\
[09.07.2024 19:06:56.312]   <108>    Info (3)        file                : C:\VeeamFLR\testwin2022_5047f966\Volume1\Users\Administrator\Downloads\bbbb\
[09.07.2024 19:06:56.312]   <108>    Info (3)        file                : C:\VeeamFLR\testwin2022_5047f966\Volume1\Users\Administrator\Downloads\aaa
[09.07.2024 19:06:56.312]   <108>    Info (3)        file                : C:\VeeamFLR\testwin2022_5047f966\Volume1\Users\Administrator\Downloads\aaa\aaa.txt
[09.07.2024 19:06:56.312]   <108>    Info (3)    -------------------------------------------------------------------------------

I tried to refer to the file in Windows FLR, but the Japanese is also displayed without any problem, so it seems that the problem is only with the log output.


Do you have any information on this issue?

Veeam version is 12.1.2.172.
For Scan Backup, "Scan restore poiint with an antivirus engine" is selected, and Windows Defender is used because no additional installation and configuration was made.
Support case number: # 07335890

[david.domask]

Hi Yukinobu Asami,

Thank you for the detailed report -- let's allow Support some time to review the Veeam logging and check for known issues/unexpected behaviors.

For the Antivirus scan log, I think that is coming directly from the AV engine itself (Windows Defender in your case), and this is known behavior for cmd line utilities and Windows: https://learn.microsoft.com/en-us/troub ... -languages

While the article is for powershell, cmd is affected also, so I think that's why your cmd and the Defender scan results are likely not handling the japanese characters well.

Let's allow the Support Engineer time to finish reviewing the case however, there may be other elements I'm not aware of that may impact this.

[Yukinobu]

Thank you. I'll give it a try.