Windows agent supports only UTF-8 encoded configuration filesDescriptionThe Agent Client Collector running on a Windows host must use a UTF-8 encoded file (default). If any other encoding is used (UTF-8 BOM, UTF-16), the file may get corrupted.Steps to Reproduce Install an Agent, with MID Selection enabled, and then shut it downConvert the acc.yml file to "UTF-16 LE BOM" format (can be done with NotePad++)Start the Agent.Wait for Auto MID Selection to send down new configuration. You may have to run the "Update Mid List For All Agents" scheduled job to force the MID to update the mid selector list in acc.yml NOTE: The agent will write the "backend-url" parameter to the yml file incorrectly.WorkaroundThe solution is to keep the acc.yml file as 8-bit ASCII or UTF-8 to avoid the problem.Related Problem: PRB1604987