Running processes are not populated through Discovery if the XML contains special charactersIssue Running processes are not stored on certain Windows Servers ReleaseWashington DCCauseThis is mostly caused because of the XML formatting issue.In the ECC Queue input record of "Windows - Application Dependency Mapping", you would notice that the HTML encode is not decoded.(like <Name>System Idle Process<...)This can occur due to some invalid characters returned from the commands used in "Windows - Application Dependency Mapping" probe.Most of the scenario involved 'CommandLine' information of some running process, due to which the processing of the output didn't work out.ResolutionSwitch to OOB "output_format" probe parameter in "Windows - Installed Software" to "json". In case you still want to continue with "output_format" to "xml", you can mark WMI Field 'Win32_Process.CommandLine's (or any field which has special characters in it) active status to 'false' in 'Windows - Active Processes' probe. This will not be fetched, and so the unformatted data will not come. The script processing the change needs to accommodate it. Please change the script in "MultiSensor Scripts" of "Windows - Active Processes" WMI probe.