Symantec Endpoint Protection Arm64 Work Link 🎯

Symantec Endpoint Protection on ARM64: Architecture, Compatibility, and Implementation

While the ARM64 client offers comprehensive protection, certain legacy and advanced features are not supported on this architecture:

"Looking into Symantec Endpoint Protection for ARM64 devices. SEP historically targets x86/x64; native ARM64 clients aren’t widely available. Emulation on Windows on ARM may let SEP run but can cause performance and driver compatibility issues and may not be supported. Recommended approach: open a support case with Broadcom, test on a small fleet, and consider endpoint solutions that provide native ARM64 agents if you need full feature parity. If anyone has recent hands-on experience with SEP on ARM64, please share specifics (version, OS build, gotchas)." symantec endpoint protection arm64 work

• No public commitment to a native ARM64 SEP client as of April 2026.
• Focus remains on x64 and Linux ARM64 (for servers), not Windows ARM64 endpoints.
• Recommendation: For new ARM64 deployments, migrate to Microsoft Defender for Endpoint (P2) with SEP’s management via MDE integration.

4.2 Installation Procedure (Manual Workaround)

Symantec Endpoint Protection (SEP)

If your organization relies on , you are likely asking: "Does Symantec Endpoint Protection ARM64 work?" No public commitment to a native ARM64 SEP

C. Permissions and Provisioning

Before diving into SEP’s status, it’s critical to understand Windows on Arm’s two operating modes: Symantec Endpoint Protection on ARM64: Architecture

| Metric | x64 Reference | ARM64 (emulated) | Delta | |--------|---------------|------------------|-------| | Boot time impact | +8 sec | +22 sec | +175% | | On-access scan (1 GB .zip) | 4.2 sec | 11.8 sec | +181% | | CPU usage (idle) | 0–2% | 5–9% | +250% | | Signature update (50 MB) | 12 sec | 34 sec | +183% |