Symantec Endpoint Protection Arm64 Work -

Running non-native security software on ARM64 requires Windows to translate the code in real-time, which can lead to:

For traditional on-premise Symantec Endpoint Protection 14.4 and older versions, the support situation is different:

: Memory mitigation controls built specifically around x86/x64 memory layouts are excluded.

With compatibility confirmed, you can proceed with the installation. The method depends on your platform and chosen management solution. symantec endpoint protection arm64 work

: Support is available for cloud-managed (Integrated Cyber Defense Manager - ICDm) and unmanaged (self-managed) clients.

Consider these alternatives on ARM64:

Before diving into SEP’s status, it’s critical to understand Windows on Arm’s two operating modes: : Support is available for cloud-managed (Integrated Cyber

Select the Windows ARM architecture option when downloading the installation package from the SES Cloud console.

Broadcom introduced native ARM64 support for Windows in .

You cannot deploy ARM64 endpoints using an on-premises management system. Broadcom enforces specific control rules for ARM-based hardware architectures. Management Server Rule You cannot deploy ARM64 endpoints using an on-premises

Once installed, verify that the native security services are running on the system using the command line: Open an elevated Command Prompt ( cmd ).

Cannot restrict application execution paths or hash blocklists locally via standard SEP policies.

The system spends too many cycles translating code.

The ARM64 agent provides a wide array of protection features nearly identical to those on standard x64 workstations: