> For the complete documentation index, see [llms.txt](https://docs.cloudbrink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudbrink.com/release-notes/brinkagent-14.5.1756-release-notes.md).

# BrinkAgent 14.5.1756 Release Notes

**September 2026**

### Fixed Issues in 14.5.1756

1. Wi-Fi DHCP change not detected, causing DNS failures
2. Post Agent installation/upgrade, BrinkApp UI not loading
3. DNS failure due to DNS leak using new adapter
4. BrinkAgent starting from a STOPPING state when user attempts re-login
5. BrinkAgent UI stuck after sleep/wakeup
6. BrinkAgent diagnostics page does not reflect latest diagnostic execution status
7. BrinkAgent logged out automatically even before token timeout
8. BrinkAgent UI not coming up after upgrade
9. iOS BrinkAgent support for User-IP mapping notification

### Known Issues in 14.5.1756

{% hint style="warning" %}
**BrinkAgent on Windows ARM devices.** After entering the username and clicking **Next**, the browser pop-up window that prompts for external authentication can occasionally appear as a blank white screen during login on Windows ARM devices. Close BrinkAgent completely and try again.
{% endhint %}

### Fixed Issues in 14.5.1592

1. In-Office Pass-through state changes not working when laptop has dual-home networks (Wi-Fi and Ethernet)
2. BrinkAgent traffic blocked due to URL notification failure
3. User selection of BrinkAgent 'X' will be remembered until next upgrade
4. Logout option needed apart from Quit option
5. Delay in migrating In-Office pass-through states during network change event
6. Auto-minimize Agent UI on restart when re-authentication is not required
7. Internet stopped working for users, watchdog service didn't restart brinkagent process
8. Watchdog restart attempts during sleep mode
9. User unable to reach backend resources, ICMP failure
10. Handling of DoH/DoT on CBNet interface creating access issues
11. DSPA AV check for "Any" and check for Blacklist apps failing
12. BrinkApp UI rendering issues related to Session Timeout notification
13. BrinkAgent icon does not appear on taskbar
14. Datapath thread deadlock issue blocking application traffic
15. Uninstall / upgrade procedures not cleaning up brinkapp (intermittent)
16. CBNet interface DNS server incorrect settings

### Fixed Issues in 14.5.1328

1. Device posture assessment checks implemented natively in place of Osquery lib
2. BrinkAgent startup time optimizations
   * Multithread route programming
   * Interface metric file writes
   * Move to async/thread logic in place of inline calls for adapter
   * Driver startup delays fixes
   * RPC calls infra optimization
3. BrinkAgent restart issues after quitting
4. BrinkAgent restart not working from watchdog service
5. BrinkSupport using higher CPU on macOS
6. BrinkAgent support for FQDN configurations on Enterprise-Service
7. Optimize BrinkAgent log-bundle size
8. In-office pass-through not working or delayed state transition during network switching
9. BrinkAgent login window hang issue when IDP login window is closed out-of-sync
10. Support for ARM (M2-based) macOS
11. DoT/DoH DNS traffic handling support
12. Windows BrinkAgent service control manager changes and issues fixed
13. BrinkAgent UI blank screen issues fixed
14. macOS BrinkAgent pfctl updates
15. DNS leaks fixed

### New Features in 14.5 Release

| #  | Feature                                                     | Description                                                                                                                                                                                                                                                                                                                                                         | 14.5 Agent | 14.5 Connector |
| -- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------: | :------------: |
| 1  | Users Collection                                            | Customers can add a Users Collection and add local users and group mappings. OTP authentication policy can be used to validate users from the Users Collection.                                                                                                                                                                                                     |            |                |
| 2  | Multi-group support                                         | When a user is part of multiple groups, Cloudbrink can combine all the resources from the resource templates across all these groups and provide access and security to the combined set of resources. This capability must be enabled explicitly by the MSP partner at the tenant level.                                                                           |            |                |
| 3  | Connector status on BrinkAgent UI                           | When users have datacenter access via Connector, BrinkAgent displays the connectivity status to the Connectors and the private IP assigned for this user session.                                                                                                                                                                                                   |     Yes    |       Yes      |
| 4  | End-to-end Visibility chart enhancements                    | Customers can now see the Device QOE stats from the same end-to-end visibility flow charts and get insight into user experience all from one place.                                                                                                                                                                                                                 |            |                |
| 5  | Connector deployment simplification for Proxmox and Hyper-V | In 14.4, deployment steps for ESX Connector were simplified. The same simplification steps are now supported for Proxmox and Hyper-V connectors. Admins can add Connector instances on the admin portal and download the deployment script. When this deployment script is run from the lab server, the Connector image and ISO file are automatically downloaded.  |            |       Yes      |
| 6  | UI Search improvements                                      | Admins can search for a user (email ID) from the search option at the top of the admin portal. The search results show the user's data, and admins can easily navigate to the user-specific visibility sections.                                                                                                                                                    |            |                |
| 7  | MSP Portal Whitelabel                                       | MSP partners can now upload their logo and color theme on the MSP portal. The MSP portal and the tenant portals that the MSP is managing show the MSP logo and color theme as selected.                                                                                                                                                                             |            |                |
| 8  | MAC addr in DHCP req option                                 | Customers can enable including the endpoint MAC address in the DHCP request so the same DHCP IP is always assigned to the endpoint.                                                                                                                                                                                                                                 |            |                |
| 9  | In-office pass-through mode                                 | To enable seamless roaming of users inside and outside the office network, In-office Pass-through mode is provided. BrinkAgent detects the location of the user and enters pass-through mode when the user is inside the office. When the user is outside the office network, BrinkAgent automatically connects and starts securing and optimizing enterprise apps. |     Yes    |                |
| 10 | EnGenius Multi-WAN support                                  | The EnGenius + Cloudbrink integration is enhanced to support EnGenius Multi-WAN capability.                                                                                                                                                                                                                                                                         |     Yes    |                |
| 11 | SCIM                                                        | Cloudbrink supports the SCIM protocol with Okta. Customers can sync Okta security groups with Cloudbrink for easier management of policies applied to the users belonging to these groups.                                                                                                                                                                          |            |                |
| 12 | BrinkAgent UI error message cleanup                         | The end-user facing error messages have been cleaned up to improve usability and give clear feedback to users.                                                                                                                                                                                                                                                      |     Yes    |                |
| 13 | Logout option on BrinkAgent                                 | Users can log out from BrinkAgent (instead of Quit); relaunching BrinkAgent starts the app immediately.                                                                                                                                                                                                                                                             |     Yes    |                |
| 14 | BrinkAgent close (X) behavior                               | When the user selects the Minimize or Quit option after clicking X on the BrinkAgent UI, the selection is remembered for the user until the next agent install.                                                                                                                                                                                                     |     Yes    |                |

### BrinkAgent Platform Support

The Cloudbrink solution consists of multiple components. The Brink App is installed on end-user desktops to provide secure connectivity and quality-of-experience features.

| Client Platform | Version Supported                              |
| --------------- | ---------------------------------------------- |
| Windows         | Windows 11, Windows 10                         |
| macOS           | macOS 26.x, 15.x, 14.x                         |
| Linux           | Ubuntu 24.04 LTS, 22.04 LTS; Kubuntu 22.04 LTS |
| FreeBSD         | FreeBSD 14.1 and above                         |
| iOS / iPadOS    | 18.x, 17.x, 16.x                               |
| Android OS      | 15.x, 14.x, 13.x                               |
| Chromebook      | ChromeOS 120 (LTS) and above                   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cloudbrink.com/release-notes/brinkagent-14.5.1756-release-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
