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

# Keeper Gateway 1.7.5

### Overview

The Keeper Gateway 1.7.5 fixes a few additional stability issues with the 1.7.3 and 1.7.4 release.

### Bug Fixes

* **PG-161**: Fixed an issue where the Windows Gateway uses too many file handles
* **PG-160**: Fixed a file descriptor leak from failed WebRTC session initialization
* **DR-1136**: Back tick symbol is added to the list of illegal passwords for rotations
* **DR-1137**: Password rotations fail immediately during initialization when Windows Performance Counters are corrupted or unavailable

### Update Instructions

Please visit the Keeper Gateway documentation for your specific platform:

{% content-ref url="/spaces/-MJXOXEifAmpyvNVL1to/pages/YVitXRsJWzo14VlLdwoR" %}
[Gateways](/keeperpam/privileged-access-manager/getting-started/gateways.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/enterprise/keeper-gateway/keeper-gateway-1.7.5.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.