DBCS characters appear garbled when you run some PowerShell scripts in EMS in an Exchange Server 2013 environment

Assume that Microsoft Exchange Server 2013 is installed on a computer that is configured to use a display language that uses Double-Byte Character Set (DBCS) characters, such as Japanese. Then, you run one of the following scripts in Exchange Management Shell (EMS):

• Disable-AntimalwareScanning.ps1
• Enable-AntimalwareScanning.ps1
• FilterringConfigurationCommands.ps1
• StoreTSLibrary.ps1
• Update-MalwareFilteringServer.ps1

In this situation, the DBCS characters appear garbled. More specifically, the characters resemble the following:

This issue occurs because the *.strings.psd1 files that correspond to the scripts use the American National Standards Institute (ANSI) format instead of the 16-bit Unicode Transformation Format (UTF-16).

To resolve this issue, install the following cumulative update: 

To work around this issue, save the *.strings.psd1 files in the UTF-16 format in the language specific subfolders in the Scripts folder.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the ANSI format and the Unicode format, go to the following Microsoft website: