---
type: Addressed
product: Prisma Access Agent
version: 25.6.2
---

## PANG-9620

Fixed an issue where the Prisma Access Agent would automatically
disconnect and remain disconnected without attempting to
reconnect, leaving users without network protection. The problem
occurred when the agent lost its connection to the endpoint
management server and failed to re-establish the connection
automatically as expected.

This occurred due to a DNS resolution timing conflict in certain
network environments where the primary DNS server was
unresponsive while the secondary DNS server was functioning
properly. The fix adjusts the DNS resolution process to ensure
proper failover occurs when the primary DNS server is
unavailable, allowing the agent to maintain connectivity and
automatically reconnect when network issues are resolved.

## PANG-9630

Fixed an issue where the Prisma Access Agent would become stuck
in a "Connecting" state after a network switch when attempting
to connect to an internal gateway. This problem occurred when
users experienced a network change that caused them to be logged
out from the tunnel, and while the Prisma Access Agent endpoint
manager web-socket would successfully reconnect, the Prisma
Access Agent app would remain stuck displaying "Connecting"
indefinitely.

## PANG-9276

Fixed an issue where the Spyder application would display
"Permission denied" errors and fail to work properly when Prisma
Access Agent was installed on the same computer. Users found
that Spyder would only function normally after completely
removing the Prisma Access Agent from their system, creating a
conflict between the two programs. The fix ensures that the
Prisma Access Agent no longer interferes with Spyder, allowing
both programs to run simultaneously without conflicts while
maintaining the agent's security protection for other
applications on the system.

## PANG-9220

Fixed an issue where users encountered "Server Enrollment
failure" errors after installing Prisma Access Agent version
25.4.0.29, preventing them from successfully connecting to their
organization's network. The problem occurred during the initial
setup process when the agent attempted to register with the
endpoint management server but failed with messages indicating
an invalid enrollment secret. This occurred due to a
compatibility issue between the agent's security enrollment
method and certain Windows system security components. When the
agent tried to use the primary secure enrollment process, some
Windows systems would reject the connection due to unsupported
security protocols, causing the entire enrollment to fail.

## PANG-9092

Fixed an issue where the Prisma Access Agent would freeze and
become stuck in a non-responding state. The problem occurred
when the application attempted to update multiple settings at
the same time from different parts of the program, causing
conflicts that would lock up the entire application. This
resulted in users being unable to interact with Prisma Access
Agent, as the interface would stop responding and the agent
would appear to hang indefinitely. The fix ensures that all
setting updates are now processed in a controlled, sequential
manner to prevent these conflicts and maintain application
responsiveness.

## PANG-9067

Fixed an issue where the Prisma Access Agent on macOS 15.6.1 failed to connect to external gateways when selecting Best Location and incorrectly switched to internal connectivity. This issue manifested in two specific scenarios:

1. After upgrading the operating system from macOS 15.6 to 15.6.1, Prisma Access Agent would incorrectly connect to an on-premises gateway instead of maintaining its connection to the external Prisma Access gateway that it was using prior to the OS upgrade.
2. When users selected Best Location from the Prisma Access Agent app, the agent would search through all available Prisma Access gateways but then inappropriately switch to Internal mode, even when connected to a home WiFi network where Internal Host Detection should not be triggered.

This occurred due to the improper cleanup of the on-premises tunnel routes during the Best Location selection process, which caused the system to incorrectly determine that it was on an internal network and activate the Internal Host Detection functionality. This resulted in users being unable to establish proper external gateway connections through Prisma Access Agent on the updated macOS version, forcing the agent into internal mode when external connectivity was required and available.