Broadcom provides ARM64/aarch64 installers for specific Linux distributions, managed through the (SEP Linux Packager) tool.
While the journey has involved gradual feature rollouts across different SEP versions (14.3 RU2 for M1, RU5 for M2, and RU8 for M3, for example), the current state of support is mature and enterprise-ready. The key to success lies in using the right version of the SEP client for your specific operating system, leveraging tools like the SES cloud console for Windows deployments and the seplpkg tool for Linux.
[HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\AV] "DisableDriverLoadCheck"=dword:00000001 "ForceEmulationMode"=dword:00000001
: Supported starting via Symantec Agent for Mac build 14.3 RU1 and evolved natively into modern versions like SEP 16 for Mac / Endpoint Security Agent (ESA) . Management follows the cloud-only paradigm through the cloud console. Feature Parity and Feature Gaps on ARM64
Navigate to the or Installation Packages tab. Choose to download a new creator package. symantec endpoint protection arm64 work
The introduction of dedicated ARM64 clients in SEP 14.3 RU8 and the full integration into SEP 16 signals Broadcom’s commitment to the ARM ecosystem. The fact that DLP 25.1 also added ARM64 support further reinforces this direction.
Before installing Symantec Endpoint Protection on an ARM-based PC, the system must meet these foundational baselines:
: Intrusion Prevention Policies tailored specifically for legacy configurations of Internet Explorer or Firefox are omitted.
When installing SEP on an ARM64 machine, the native installer automatically negotiates with the operating system. If you enable the policy, the client automatically deactivates Windows Defender Firewall to prevent conflicting dual-filtering latency. If you do not deploy the Symantec Firewall module, Windows Defender remains active alongside Symantec's core antivirus agent to protect network vectors. Microsoft Trusted Signing Requirements Choose to download a new creator package
| Metric | x64 Native (Intel/AMD) | ARM64 via Emulation (SEP) | Native ARM64 AV (e.g., Defender) | | :--- | :--- | :--- | :--- | | Boot time impact | +4 seconds | +8-10 seconds | +3 seconds | | ZIP file scan (1GB) | 12 seconds | 19 seconds | 9 seconds | | CPU during idle scan | 8% | 22% | 5% | | Kernel driver stability | Excellent | Moderate (rare BSODs reported) | Excellent |
Deploying SEP to ARM64 fleets requires a modern management approach (Mobile Device Management or MDM).
All core protection features are available, though some nuances exist.
Active Directory obfuscation and lateral movement defenses are restricted on the local client. you should stress-test heavily.
However, the user-mode components and the core antivirus engine can run via Microsoft’s emulation layer on Windows 11 ARM64 (version 22H2 and later).
Symantec Endpoint Protection does work on ARM64, but successful deployment requires careful planning around management models and feature expectations.
Explicit support for ARM-based processors like the Apple M1, M2, and M3 series (for macOS) and Windows 10/11 ARM devices. Implementation Steps
For a road warrior with a Surface Pro X, SEP is usable but sluggish. For a virtual desktop (VDI) on Azure ARM64, you should stress-test heavily.