ACC-M 3.16.1 Windows Performance Issue - Known Error

ACC-M 3.16.1 Windows Performance Issue Description In ACC‑M plugin version 3.16.1 replaces WMIC calls with PowerShell commands for default Windows checks (disk, memory, network, process). The PowerShell‑based checks consume excessive CPU, driving agents to 100 % utilization and generating “Check Process CRITICAL: error executing PowerShell command: exit status 1” events when a monitored process is not running. The issue appears on agents version 5.0.0 (or 6.0.1 without protection) and impacts data collection, causing host and MID‑server CPU contention.

Steps to Reproduce

1. Upgrade an ACC instance to Zurich (or later) and install ACC‑M plugin version 3.16.1. 2. Deploy an ACC agent version 5.0.0 (or 6.0.1) on a Windows host. 3. Enable the default Windows checks (disk, memory, network) and allow data collection to run. 4. Observe the host CPU usage rising to 100 % and frequent agent_protection events.

Workaround Option 1: Increase CPU Protection Threshold Raise the CPU protection limit in the agent configuration to allow higher CPU usage before protection kicks in:

Edit the agent configuration and increase cpu_percentage_limit from the default value of 5 to a higher value such as 10 or greater Restart the MID server so the updated configuration propagates to agents Verify that agent protection events reduce and CPU usage stabilizes Option 2: Disable Intensive Checks Reduce the frequency or disable the most CPU-intensive metric checks:

Edit the ACC.yml file OR modify the Windows OS Metrics policy Disable or reduce frequency of the most intensive checks (disk utilization, memory utilization, and network metrics) Restart the MID server to apply changes Verify performance improvement on Windows agent hosts Permanent Solution Upgrade ACC-M to version 3.17.1, which includes performance optimization.