Issues Addressed in Prisma Agent 25.6.2
Focus
Focus
Prisma Agent

Issues Addressed in Prisma Agent 25.6.2

Table of Contents

Issues Addressed in Prisma Agent 25.6.2

Review the issues addressed in Prisma Agent 25.6.2.
The following table lists the issues addressed in Prisma Agent version 25.6.2.
Issue IDDescription
PANG-9620
Fixed an issue where users were unable to sign in after upgrading the Prisma Agent to version 25.6.1 on macOS 15.x Sequoia. The login window failed to render after upgrade, showing only a blank page, and sign-in could only be completed using SSO.
Users can now sign in using username and password after upgrading.
PANG-9630
Fixed an issue on Linux where the Prisma Agent failed to establish a connection to the gateway when no client certificate was configured and the connection relied on endpoint manager (EM) cookies for authentication. The agent now successfully connects when using EM cookies without a client certificate.
PANG-9276
Fixed an issue on Linux where the Prisma Agent would fail to reconnect after waking from sleep, requiring a service restart or device reboot to restore connectivity. The agent now reconnects automatically when the device wakes from sleep.
PANG-9220
Fixed an issue on macOS endpoints where, after a device resumed from sleep, the Prisma Agent failed to update its connection status in the UI. The UI showed an incorrect status that didn't reflect the actual connection state. The agent UI now correctly reflects the connection state after resuming from sleep.
PANG-9092
Fixed an issue on macOS endpoints where the Prisma Agent failed to automatically reconnect after network transitions (such as switching between Wi-Fi networks or going from Wi-Fi to LAN). Users had to manually reconnect. The agent now reconnects automatically after network transitions.
PANG-9067
Fixed an issue on Windows where the Prisma Agent failed to complete HIP data collection and upload a HIP report when:
  1. The HIP profile included a check for specific applications using the Running Processes criteria.
  2. The process list on the Windows endpoint was very large (greater than 450 running processes).
The agent now successfully collects and uploads HIP reports when checking for running processes, regardless of the number of processes on the endpoint.