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

# Windows Agent v6.6.2

This release adds token-based agent registration and safeguards agent data during uninstallation.

### What's new

#### Token-based installation and registration

The installer now supports `register-with-token`. This option registers an agent with a Cloud-generated token and an email-format username.

The agent calls the enrollment API to obtain its certificate. Tray app login authentication is skipped. After installation, the user selects **Sign in** the tray app to register the agent. No login is required for the user.

#### Safer uninstallation

The installer now backs up agent database files and registry keys before uninstalling. It validates the backup operation's exit code.

Database backups are stored in `C:\Users\Public\FenixPyreSetupLogs`.

If the backup fails, the uninstall stops. Use force mode only when you must continue without a successful backup.

### Update to v6.6.2

{% hint style="info" %}
Complete the [prerequisite checklist](/fenixpyre-for-admins/fenixpyre-windows-agent/prerequisites-for-fenixpyre-windows-client-installation.md) before installing the FenixPyre Windows Client.
{% endhint %}

#### Automatic update

Admins can set v6.6.2 as the default installer in **Admin Dashboard** → **Installers**. Users can also update from the system tray app. Select **Actions** → **Check and Install Updates**.

> For update management details, see [Auto Update and Upgrade Management of FenixPyre Windows Client](/fenixpyre-for-admins/admin-dashboard/installers/fenixpyre-windows-client/auto-update-and-upgrade-management-of-fenixpyre-windows-client.md).

#### Manual update

For agents running v6.0.0 or later, run `FPUpdater.exe` from the v6.6.2 zip file. The updater uninstalls the current version, restarts the PC, installs v6.6.2, and restarts again. Users must sign in after the final restart.

For agents running a version below v5.0.0:

1. [Manually uninstall](/fenixpyre-for-users/windows-agent/how-to-un-install-fenixpyre-windows-client.md) the current version.
2. Restart the PC.
3. Install v6.6.2 using **FPInstaller.exe**.
4. Restart the PC and sign in.

### Resources

* [Download FenixPyre Windows Agent from the Installers page](/fenixpyre-for-admins/admin-dashboard/installers/fenixpyre-windows-client/how-to-download-fenixpyre-windows-agent-from-installers-page.md)
* [Install FenixPyre Windows Desktop Client](/fenixpyre-for-admins/fenixpyre-windows-agent/how-to-install-fenixpyre-windows-desktop-client.md)
* [Uninstall FenixPyre Windows Client](/fenixpyre-for-users/windows-agent/how-to-un-install-fenixpyre-windows-client.md)


---

# 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.fenixpyre.com/release-notes/fenixpyre-windows-client-releases/windows-agent-v6.6.2.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.