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

# 6.2.0

Release Date: 2026-07-16

**What's New**

* Added proxy support: the installer and agent are now proxy-aware. Endpoints can install, register, and communicate through a HTTP proxy. Upgrades from pre-6.2.0 versions automatically retain their existing direct-connection behaviour.
* The agent now trusts the Windows certificate store enabling deployments behind TLS-inspecting proxies and environments using enterprise certificate authorities.
* New `tdcli re-register` command to re-register an endpoint without a full reinstall.
* Added Windows Server 2025 support and Security Configuration Assessment (SCA) policies to the HIDS component.
* Added native ARM64 Sysinternals tools on Windows-on-ARM endpoints.
* Upgraded Velo Module to latest stable release.
* Upgraded OpenSSL to latest LTS.

**Enhancements**

* Improved installer, service, and error-report logging for easier troubleshooting.

**Bug Fixes**

* Fixed upgrades leaving agent services unregistered or binaries missing.
* Fixed installer error 1316 during upgrades.
* Fixed the AUTOUPDATE installer property being ignored.
* Fixed incorrect error codes reported for some HIDS service failures.
* Fixed installation rollback, leaving pre-install files behind.

***

#### Checksums

**SHA1**:

`22d8a2df950fdb37100fba16e1f82d483679e4df`

**SHA256**:

`b1a0e4a06478f5cfce103242373ecae31e7b4f3abd00d3265dc7c9b1061b144b`

**MD5**

`cb96950270df6416253ea3a59c62571c`


---

# 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.threatdefence.com/endpoint-agent/release-notes/windows-agent/6.x/6.2.0.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.