SEP’s kernel-mode drivers (e.g., sysfer.sys , eeCtrl64.sys ) are x64 binaries and fail to load on ARM64 systems unless explicitly signed for ARM64. Broadcom does not provide ARM64 driver signatures for most versions.
Broadcom has expanded Symantec Endpoint Protection (SEP) and Symantec Endpoint Security (SES) to support the , specifically targeting Windows 11 devices like the Surface Pro X and other Snapdragon-powered PCs. Core Support and Management
For a security admin, this creates a fragmented landscape: symantec endpoint protection arm64 work
Understanding ARM64 Compatibility for Symantec Endpoint Protection
: The cloud console may cancel policy imports if SEPM has groups with the same name but different capitalization (e.g., "GroupName" vs "groupname"), as the cloud console is more restrictive. If you're planning a rollout, I can help you: SEP’s kernel-mode drivers (e
Due to the unique nature of the ARM64 architecture, certain legacy or specialized features are : Application Control and Exploit Protection. Threat Defense for Active Directory (AD).
If you ever need to completely remove the SEP client from a Mac—perhaps to perform a clean reinstall—you can use the official tool provided by Broadcom. Running this tool ensures that all Symantec files and folders are thoroughly removed from your system. Core Support and Management For a security admin,
Running non-native security software on ARM64 requires Windows to translate the code in real-time, which can lead to:
: Self-managed, standalone clients can be manually installed on individual ARM64 machines using the full installation package downloads. System Requirements for ARM64 Deployment
: ARM64 endpoints cannot be managed by an on-premises Symantec Endpoint Protection Manager (SEPM) . They must be managed via the Symantec Endpoint Security (SES) Cloud Console or remain unmanaged .