Carbon Black Cloud: "APC Max Exe delay" set above 60 seconds not working
search cancel

Carbon Black Cloud: "APC Max Exe delay" set above 60 seconds not working


Article ID: 290170


Updated On:


Carbon Black Cloud Endpoint Standard (formerly Cb Defense)


  • Maximum delay on executable files while waiting on Avira Protective Cloud (APC) analysis never exceeds 60 seconds
  • Endpoint Standard Policy setting “APC Max Exe delay” with a value higher than 60 seconds is not honored on 3.7.x.x and earlier Sensors
  • Output of `repcli status` shows same value as Policy setting
    Example: "APC Max Exe Delay" set to 100 on Policy
    "C:\Program Files\Confer\RepCLI.exe" status | findstr MaxDelay
            APC[Enabled] RiskLevel[4] MaxSize[4194304 bytes] MaxDelay[100 sec]
  • Output of authenticated `repcli configprops` command shows value prior to being set higher than 60 seconds (default 45s)
    "C:\Program Files\Confer\RepCLI.exe" configprops | findstr ApcUploadMaxExeDelaySec
    40. ApcUploadMaxExeDelaySec=45


  • Carbon Black Cloud Console: All Versions
    • Endpoint Standard
  • Carbon Black Cloud Sensor: 3.2.x.x thru 3.7.x.x
  • Microsoft Windows: All Supported Versions


3.7.x.x and earlier Sensors not honoring "APC Max Exe delay" when set above 60 seconds


Upgrade to 3.8.x.x or higher Sensor when available

Additional Information

Prior to 3.8.x.x Sensor becoming available, please open a Support case to request assistance with setting “APC Max Exe Delay” to values higher than 60 seconds