Symantec Endpoint Protection Arm64 Hot [portable]

Symantec Endpoint Protection (SEP) supports Windows ARM64 (such as Surface Pro 9/X) primarily through cloud-managed installations. Broadcom support portal Key Compatibility Details Management Support : ARM64 endpoints are not supported

3. Incompatible Hardware Acceleration

SEP offloads signature scanning to AES-NI instructions. On some Qualcomm Snapdragon X Elite chips, these instructions are emulated instead of passed to the crypto engine, causing a 300% increase in scan time and thermal output. The real "hotfix": Disable "Enable hardware virtualization" in SEP policy > Advanced Settings > Performance. symantec endpoint protection arm64 hot

Operating System: Supported on Windows 11 GA builds (21H2, 22H2). Feature Limitations on ARM64 Elevated baseline CPU usage (8-12% vs

Feature Limitations: Most features are supported except for: Custom Application Behavior Threat Defense for AD Web and Cloud Access Protection Exploit Protection Legacy IE/Firefox Browser Protection macOS ARM Support Most standard security features are available, but several

• Elevated baseline CPU usage (8-12% vs. 2-3% for native AVs).
• Increased system temperature (MacBooks running SEP often hover at 70-80°C under light load).
• Battery drain (up to 20% faster discharge compared to native security tools).

Most standard security features are available, but several advanced "hot" protection layers are not supported on ARM64 as of early 2026: Application Control and Custom Application Behavior. Threat Defense for Active Directory. Web and Cloud Access Protection.

Why It’s “Hot” Right Now

• Windows ARM64: Full native support is here to stay. Expect SEP 15 (due 2026) to be ARM64-first.
• macOS ARM64: No native SEP client ever. Official recommendation: Migrate to Symantec Endpoint Security (SES) or Carbon Black. SEP for macOS is in maintenance mode.
• Linux ARM64 (Graviton, etc.): SEP 14.3 RU10 will introduce a headless ARM64 client for cloud servers. Beta available now.

2. The Memory Scan Loop (Windows ARM64)

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).