Symantec Endpoint Protection (SEP) and Symantec Endpoint Security (SES) have expanded support for ARM64 architecture across Windows, macOS, and Linux. A critical requirement for ARM64 deployment is that clients must be unmanaged or cloud-managed via the Symantec Endpoint Security (SES) console; on-premises Symantec Endpoint Protection Manager (SEPM) does not currently support managing ARM64 endpoints. Platform Support Overview Platform Support Status Requirements / Versions Windows Native Support SEP 14.3 RU7 or newer; requires Windows 11 GA builds. macOS Native Support
If you are experiencing performance issues (overheating or CPU spikes) on an ARM device: symantec endpoint protection arm64 hot
The "hot" in the story isn't just about a patch—it's about the heat of a crisis. For two years, security teams had to choose between modern ARM hardware (Copilot+ PCs, MacBooks with Windows on ARM VMs) and enterprise-grade protection. They couldn't have both. Native support : SEP is optimized for ARM64
A major European bank had threatened to drop 50,000 licenses if Broadcom didn't deliver. The engineering team in Mountain View had been fighting two battles: rewriting their 1.5-million-line kernel driver for ARM’s different interrupt model, and getting Microsoft’s signature for the new ARM64 WHQL driver. The "hot" in the story isn't just about
Cloud-Managed Clients: You must select the Windows ARM architecture specifically when downloading the Symantec Endpoint Security (SES) package from the cloud console.
In SEP versions prior to 14.3 RU9, the ARM64 client had a bug where ccSvcHst.exe would repeatedly scan the same memory pages of translated x64 apps (like Office or Chrome). This created a "hot loop" that spiked CPU to 99% for minutes at a time. Solution: Apply hotfix KB-2024-03-ARM64 (available via Broadcom support portal).
Custom Application Behavior and Threat Defense for AD are currently unsupported on ARM.