Aurora Protect agent version 3.5 Memory Protection exclusions are not being applied

Final update

The issue affecting Memory Protection exclusions within Aurora Protect agent version 3.5 has been fully resolved as of 10/07/26 14:08 UTC. All services are operating normally. Incident Window: 10/01/26 16:00 UTC - 10/06/26 22:45 UTC

1. Resolved · Oct 7, 15:53 UTC
   The issue affecting Memory Protection exclusions within Aurora Protect agent version 3.5 has been fully resolved as of 10/07/26 14:08 UTC. All services are operating normally. Incident Window: 10/01/26 16:00 UTC - 10/06/26 22:45 UTC
2. Monitoring · Oct 6, 19:59 UTC
   We have released an updated version of the Aurora Protect 3.5 agent that resolves the issue where some configured Memory Protection exclusions were not being applied. Endpoints with automatic updates enabled will receive the updated version. Subset of endpoints that installed an earlier version of Aurora Protect 3.5 may not be able to upgrade automatically. Steps to upgrade these endpoints to the updated version are available in this knowledge base article: [https://support.arcticwolf.com/hc/en-us/articles/56785626631579-Aurora-Protect-How-To-Upgrade-Aurora-Protect-3-5-1000-6704-to-Aurora-Protect-3-5-1000-7405] Until an endpoint is upgraded, the workaround in this knowledge base article continues to resolve the exclusions issue: [https://support.arcticwolf.com/hc/en-us/articles/56670927173531-Aurora-Protect-3-5-Memory-Protection-Exclusions-that-Specify-a-Specific-Violation-Type-Stop-Working] Our team is continuing to work on additional options to simplify the upgrade for affected endpoints. Next update: 10/07/26 16:00 UTC
3. Identified · Oct 6, 14:17 UTC
   We have released an updated version of the Aurora Protect 3.5 agent that resolves the issue where some configured Memory Protection exclusions were not being applied. Endpoints with automatic updates enabled will receive the updated version. Subset of endpoints that installed an earlier version of Aurora Protect 3.5 may not be able to upgrade automatically. Steps to upgrade these endpoints to the updated version are available in this knowledge base article: [https://support.arcticwolf.com/hc/en-us/articles/56785626631579-Aurora-Protect-How-To-Upgrade-Aurora-Protect-3-5-1000-6704-to-Aurora-Protect-3-5-1000-7405] Until an endpoint is upgraded, the workaround in this knowledge base article continues to resolve the exclusions issue: [https://support.arcticwolf.com/hc/en-us/articles/56670927173531-Aurora-Protect-3-5-Memory-Protection-Exclusions-that-Specify-a-Specific-Violation-Type-Stop-Working] Our team is continuing to work on additional options to simplify the upgrade for affected endpoints. Next Update: 10/06/26 21:00 UTC
4. Identified · Oct 5, 20:33 UTC
   We have released an updated version of the Aurora Protect 3.5 agent that resolves the issue. Endpoints with automatic updates enabled will receive the updated version. We have identified that some endpoints may not be able to receive the updated version automatically. Our team is actively investigating a fix for this. In the meantime, the workaround in this knowledge base article continues to resolve the issue: [https://support.arcticwolf.com/hc/en-us/articles/56670927173531-Aurora-Protect-3-5-Memory-Protection-Exclusions-that-Specify-a-Specific-Violation-Type-Stop-Working] Next update: 10/06/26 16:00 UTC
5. Identified · Oct 5, 15:51 UTC
   We have released an updated version of the Aurora Protect 3.5 agent that resolves the issue. Endpoints with automatic updates enabled will receive the updated version. We have identified that some endpoints may not be able to receive the updated version automatically. Our team is actively investigating a fix for this. In the meantime, the workaround in this knowledge base article continues to resolve the issue: [https://support.arcticwolf.com/hc/en-us/articles/56670927173531-Aurora-Protect-3-5-Memory-Protection-Exclusions-that-Specify-a-Specific-Violation-Type-Stop-Working] Next update: 10/06/26 16:00 UTC
6. Identified · Oct 2, 18:34 UTC
   We are aware of an issue affecting Aurora Protect agent version 3.5. Users may find that some configured Memory Protection exclusions are not being applied. This may cause previously excluded applications to be alerted on or blocked. We have identified the cause and a workaround. While a fix is being released, users can follow the steps in this knowledge base article to resolve the issue: [https://support.arcticwolf.com/hc/en-us/articles/56670927173531-Aurora-Protect-3-5-Memory-Protection-Exclusions-that-Specify-a-Specific-Violation-Type-Stop-Working] Next Update: 10/05/26 16:00 UTC