> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/update-snapper.md).

# Update Snapper

Update an existing Snapper installation.

Use the Snapper installer to update an existing Snapper installation on a Windows device.

## Before you begin

Make sure you have:

* The current Snapper installer from your partner or regular AnywhereNow contact.
* Latest .NET Framework 4.x, with minimum version 4.6.2.
* Microsoft ASP.NET Core Runtime and .NET Desktop Runtime versions required by the selected Snapper build.
* Both runtimes installed with the architecture matching the Snapper installer: `x64` or `x86`.
* Local rights to run the installer on the device.

{% hint style="warning" %}
.NET 6.0 is end of life. Microsoft .NET 8.0 is nearing end of life, which will affect support for Snapper builds that use it. See [Microsoft .NET downloads](https://dotnet.microsoft.com/en-us/download/dotnet).
{% endhint %}

Snapper running on .NET 10.0 is available on request through [AnywhereNow Support](https://support.anywhere.now/csm). This does not mean every bundled Snapper installer uses .NET 10.0.

For the requested .NET 10.0 build, download and install both **ASP.NET Core Runtime 10.0** and **.NET Desktop Runtime 10.0** from [Microsoft .NET 10.0 downloads](https://dotnet.microsoft.com/en-us/download/dotnet/10.0). Select `x64` for an `x64` Snapper installer or `x86` for an `x86` installer.

Snapper is in maintenance mode. Replace it with [WebAgent](/use/handle-conversations/webagent.md) for agent interactions and [Dialogue Workspace](/use/monitor-and-report/dialogue-workspace.md) for real-time supervision and dashboards.

## Update Snapper

1. Run `Setup.msi`.
2. Select **Next**.
3. Read and accept the license agreement.
4. Confirm the available feature, **Anywhere365 Snapper**.
5. Select **Next**.
6. Select **Install**.
7. Wait for the update to finish.
8. Select **Finish**.
9. Start Snapper from the shortcut.
10. If the device uses the New Microsoft Teams client, change the client type to **New Teams** or **New Teams Direct Routing**.

## Verify the update

1. Start Snapper.
2. Confirm that Snapper opens without installer prompts.
3. Confirm that the selected client type still matches the Microsoft Teams client used on the device.
4. Confirm that the user can connect to the expected UCC.

## Related tasks

* [Install Snapper](/platform-administration/maintenance-mode-applications/snapper/install-snapper.md)
* [Unattended installation](/platform-administration/maintenance-mode-applications/snapper/unattended-install-snapper.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://atlas.anywhere.now/platform-administration/maintenance-mode-applications/snapper/update-snapper.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.