When adding, changing, or removing the uninstallation password for the agent, the required password might not match what was set in the console and it took up to 60 minutes for the change to be applied properly to the agent. In some cases, the agent might have been uninstalled without entering a password. (ESCL-8195)

The error message "Could not save policy. Please try again" appeared when you tried to save changes to a device policy. (ESCL-5116)

When using gold images for the OS, sometimes devices re-registered with Endpoint Defense and duplicate devices appeared in the console. (ESCL-5957)

When you change the Self Protection Level and Agent Logging Level settings for a device in the console, the settings were not reflected on the device. (EPCL-3282)

The Target Protect Version field was blank when version 3.4 of the Aurora Protect agent was installed. The agent version appeared correctly in the device details page. (EPCL-6517)

When a device was fully or partially locked down, there was a delay of 10 minutes before a device's online status is updated on the Alerts page. (ESCL-2271)

If automated responses were configured for Aurora Focus detection rules, the number of responses for those detections appeared as zero on the Detections page, even though the responses occurred and were successful. (ESCL-4425)

You couldn't lock down a device if the Remote Response setting was left as the default "OFF". (ESCL-4423)

When you tried to add a file to the Global List from the Alerts page, sometimes the "This file already exists in the global quarantine list" or "This file already exists in the global safe list" message appeared even though it was not already in the tenant's global list. (EPCL-6072)

When using the Devices grid as a Zone Manager role, other devices not part of your zone were visible but no actions could be performed against them. (UESRQ-900)

Some tenants in the AU and US regions received duplicate notification email messages from Aurora Endpoint Defense. (VENECS-2214)

In the Japanese version of the console, on the Protection > Threats screen, the "Abnormal" status was not translated properly in the Production Status column. (EPCL-5852)

If your browser was set to display the Endpoint Defense console in German, when you navigated to Protection > External devices, the add button was covered by a text pop-up. (EPCL-4666)

When you turned off "Enable automated device lifecycle management", the "Remove inactive devices" setting remained enabled. (EPCL-4244)

In Assets > Installed Applications, if you tried to sort a large list of applications by application name, a 504 error occurred and results did not display. (EPCL-1720)

If you edited a zone rule and cleared the option to "Remove devices automatically from this zone", instead of just displaying a prompt to save the zone rule, the confirmation message also included the following text that should not have been present: "Devices that do not match the criteria of the rule will be removed from this zone." (VENECS-2231)

If you tried to use the Endpoint Defense console to add an exclusion for an external USB mass storage device while your browser was set to display text in French, German, Italian, Portuguese, or Spanish, the exclusion was not added successfully. (EPCL-3833)

If a device’s OS data was not properly stored in the database, navigating to the device details screen produced an error and you could not view the device details. (EPCL-2725)

If you made changes to an existing zone, the modified date was not always updated as expected in the database. (EPCL-2051)

When there were too many device requests to update the Aurora Protect Desktop agent and updates were throttled by the console, after four attempts by the device, the device was temporarily blocked from receiving the agent update. (EPCL-2100)

When a device was automatically assigned another policy through a new zone rule, the Endpoint Defense audit log was missing information about which policy was applied to the device. (EPCL-1889)

When requesting a threat data report, the request was not automatically retried before it was finally determined to be unsuccessful. (EPCL-1718)

In the multi-tenant console, when you tried to import an exclusions .csv file for the External Device Control device policy, the "Sorry, something went wrong; please try again later" error message appeared. (EPCL-1632)

Some Aurora Focus rule categories were missing in the SAE1, EUC1, APNE1, and APSE2 regions and needed to be manually imported. (EPCL-471)

When you assigned a zone with devices to the “Test” or “Pilot” zone-based update rules, if the zone had devices with an update available, the target agent version for the device was not specified in the console properly. (EPCL-3)

On the Protection > Threats screen of the Endpoint Defense console, you could not add specific threats to the safe or quarantine list. (EPPCL-2588)

You could not authenticate users synchronized from Entra ID if the user's email address and UPN did not match. (EID-16967)

If the maximum session age specified in a client was less than the default setting used by Okta, users that completed Okta authentication were not prompted to reauthenticate until the session age set in Okta was reached. This was due to a known Okta issue. (EID-17965)

Router and proxy settings displayed in the BlackBerry Protect Connectivity Node were not applicable to Gateway. (UES-6396)