Performing (ACC) Discovery on a non-english OS is failing due to non-english characters returned from netstat commandDescriptionWhen attempting a discovery of a non-English OS the script ("Windows - Active Connections" sensor) used to test active connections will look for the following values: ============================var connection = {};if (state == "LISTENING") {connection.type = "on";connection.ip = localIP;connection.port = localPort;connection.pid = pid;} else if (state == "ESTABLISHED") {connection.type = "to";connection.ip = remoteIP;connection.port = remotePort;connection.pid = pid;connection.local_ip = localIP;connection.local_port = localPort;============================ The target server running any other language but English will not display these values and will instead give a response in it's own language.Steps to Reproduce Attempt a Windows discovery aimed at a server that is not running English as the main language, once the pattern attempts the "Windows - Active Connections" step it will fail due to non-English charactersWorkaroundAt present, the only workaround is to set the Windows OS language to English. This can be done by 1 of two ways A) Select Start > Settings > Time & Language > Language. Choose a language from the Windows display language menu, or, under Preferred languages, select Add a language to install the one you want if it isn't listed. or B) Open command prompt and enter the following two commands: Set-WinSystemLocale en-USSet-WinUserLanguageList en-USRelated Problem: PRB1561583