Fixed an issue where the ADEM icon did not appear in the Prisma Agent interface and ADEM telemetry data was not available in the ADEM dashboard after upgrading to Prisma Agent 26.3 or 26.3.1. The ADEM service continued running on the endpoint but could not transmit telemetry data.

To address this issue, upgrade to 26.3.2 from a version earlier than 26.3 (such as 26.2) rather than upgrading from 26.3 or 26.3.1. If you are currently running 26.3 or 26.3.1, perform a fresh installation of 26.3.2.

Fixed an issue on macOS endpoints where, after upgrading macOS to 26.6.2, the Prisma Agent could not retrieve the client certificate from the macOS keychain and did not send a client certificate during gateway authentication. All gateway pre-logon attempts were rejected with a client certificate validation error. The agent now correctly retrieves certificates from the macOS keychain and authenticates to gateways.

Fixed an issue on Windows endpoints where Prisma Agent 26.3 repeatedly disconnected and reconnected when a third-party agent that uses a virtual network adapter was also running. Prisma Agent incorrectly identified the virtual network adapter's routes as the physical network interface, causing repeated connection interruptions. Prisma Agent now correctly identifies the physical network interface and maintains a stable connection when third-party agents with virtual adapters are active.

Fixed an issue on macOS endpoints where, after upgrading to Prisma Agent 26.3, users received repeated macOS keychain password prompts. The prompts appeared even when the agent was not connected to a gateway and affected other applications that accessed the keychain. The agent now correctly accesses macOS keychain entries without triggering repeated password prompts.

Fixed an issue on Windows endpoints where DNS resolution for internal domains configured as bypass traffic took significantly longer on Prisma Agent 26.3 compared to previous versions. In deployments where Prisma Agent handled internet access and a third-party agent handled internal traffic, DNS queries for bypassed internal domains were not correctly routed through the third-party agent, causing resolution delays that slowed access to internal applications. DNS queries for bypassed domains are now correctly routed.