Fixed issues in the

macOS

agent

When you initiated a background scan from the command line, a warning message appeared before the scan started successfully. (EUS-1467)

If an MDM administrator tried to silently uninstall the

macOS

agent from a device, the device user was prompted to enter administrator credentials. (EUS-1191)

If you tried to uninstall the agent, a “Secure coding is not enabled” error message appeared. (EUS-1546)

When a file in the global quarantine list was detected and blocked, the block action was not reported to the management console if the file was deleted before the agent processed the event. (EPP-1709)

On

macOS

devices with the M1 chipset, the

CylancePROTECT Desktop

agent caused a kernel panic and rebooted when you tried to run an Xcode simulator. (EUS-1048)

On

macOS

devices with the M1 chipset, the

CylancePROTECT Desktop

agent was slow to shutdown during a device reboot when full disk access was enabled. (EUS-1019)

The

CylancePROTECT Desktop

macOS

agent did not load proxy auto-configuration (PAC) files properly. (EPP-1978)

When you installed or upgraded to the

CylancePROTECT Desktop

3.0.1000 agent on a device running

macOS

11 or later, the CyProtectDrvOSX kext was still found on the system, even though it was no longer required. (EPP-2942)

There are no fixed issues in this release.

On

macOS

Big Sur, a kernel panic would intermittently occur when running the agent. This was related to checking if a file is an executable and has been resolved. (CHP-8535, UD-1626)

On

macOS

Monterey, the agent stopped responding when closing a file when Memory Protection was enabled. (UD-1616)

On different

macOS

versions, memory usage increased. (EPP-1708)

On

macOS

Monterey, the CylanceSvc and CyUpdate services would not run. (EPP-1643)

On

macOS

Big Sur devices, the

CylancePROTECT Desktop

agent gave multiple Remote Allocation of Memory (OopAllocate) memory protect alerts for osqueryd. (UD-1266)