---
title: "Change to default installation directory for Windows Custom Clients"
slug: "change-of-installation-directory-for-windows-custom-clients"
updated: 2025-12-09T11:59:25Z
published: 2025-12-09T11:59:25Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.anydesk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Change to default installation directory for Windows Custom Clients

**Starting 4 December 2025**, Windows custom clients downloaded from [my.anydesk II](http://my.anydesk.com/v2) will use a different default installation directory. If you install a new custom client from that date onward, it will default to a new path.

| **File Type** | **Old Default Installation Directory** | **New Default Installation Directory** |
| --- | --- | --- |
| **EXE** | `C:\Program Files (x86)\AnyDesk-ad_{prefix}` | `C:\Program Files (x86)\AnyDesk-{prefix}` |
| **MSI** | `C:\Program Files (x86)\AnyDesk-ad_{prefix}_msi` | `C:\Program Files (x86)\AnyDesk-{prefix}_msi` |

Only custom clients downloaded after this date are affected. Existing installations will remain unchanged.

---

## **Who is affected?**

You are affected by this change if you:

- Download and install a Windows custom client from [my.anydesk II](http://my.anydesk.com/v2) on or after December 4, 2025.
- Use the **default installation directory** during setup.

> [!TIP]
> 💡 **NOTE**
> 
> - Existing installations deployed before this date are not affected.
> - Portable AnyDesk clients are not affected.
> - AnyDesk clients for other operating systems are not affected.
> - Custom clients downloaded from [my.anydesk I](http://my.anydesk.com/login) are not affected.

---

## Why the change was made?

The previous installation directory format (`AnyDesk-ad_{prefix}`) caused issues with [URL handler](/v1/docs/url-handler) registration.

The updated format (`AnyDesk-{prefix}`) resolves these conflicts without requiring versioning changes or data migration.

---

## Installation behavior after December 4

When you install a new Windows custom client after December 4, 2025:

- The installer places the application in the **new default directory**.
- Because the path is different, Windows treats the installation as a **separate application**, not an upgrade.
- If an older version is already installed, **both versions will coexist** in separate directories.

If you install a new client while an older version exists:

- **Old installation:** `C:\Program Files (x86)\AnyDesk-ad_{prefix}`
- **New installation:** `C:\Program Files (x86)\AnyDesk-{prefix}`

Both installations share the **same configuration files, ID**, and **settings**, as the configuration directory is unchanged.

<editor360-custom-block data-preprocessing="true" data-sanitizationtags="div,h2,details,summary,h3,p,code,button,strong,h4,ul,li,a"><editor360-faq data-type="faq"><hr data-faq-hr="true"><div data-expand-collapse="expandFirst" data-faq-type="ai-faq" data-loading="false" data-type="faq-acc-wrapper"><h2 data-block-id="mit4e4q0-p79t86-108" data-faq-header="true">FAQ</h2><div class="details-wrapper details-wrapper_rendered" data-type="details-wrapper"><details data-opened="true" data-button-align="right" data-details-border="withBorder" data-expand-icon="arrow" data-lock="false" open="true"><summary><h3 data-block-id="mit45dtg-fgvbcs-062">What are the old and new default installation directories for EXE files?</h3></summary><div data-type="details-content"><p data-block-id="mit45dtg-i9xtyk-063">The old default installation directory for EXE files is <code>C:\Program Files (x86)\AnyDesk-ad_{prefix}</code>, and the new directory will be <code>C:\Program Files (x86)\AnyDesk-{prefix}</code>.</p></div></details><button class="details-arrow" type="details"></button></div><div class="details-wrapper details-wrapper_rendered" data-type="details-wrapper"><details data-opened="true" data-button-align="right" data-details-border="withBorder" data-expand-icon="arrow" data-lock="false"><summary><h3 data-block-id="mit46c63-bs8lbi-073"><strong>Will existing clients update automatically?</strong></h3></summary><div data-type="details-content"><p data-block-id="mit46bdw-vliv5y-072">No. Existing clients will <strong>not automatically migrate</strong> to the new format. Windows does not support updates across different installation directories. Installing a new client results in an additional installation.</p></div></details><button class="details-arrow" type="details"></button></div><div class="details-wrapper details-wrapper_rendered" data-type="details-wrapper"><details data-opened="true" data-button-align="right" data-details-border="withBorder" data-expand-icon="arrow" data-lock="false"><summary><h3 data-block-id="mit45dtg-dhrtqy-066">Do I need to uninstall the old installation to avoid having two versions?</h3></summary><div data-type="details-content"><p data-block-id="mit45dtg-e2ka0o-067">Yes, if you want to avoid having two installations. To remove the old version, manually uninstall the client located at <code>C:\Program Files (x86)\AnyDesk-ad_{prefix}</code> .</p></div></details><button class="details-arrow" type="details"></button></div><div class="details-wrapper details-wrapper_rendered" data-type="details-wrapper"><details data-opened="true" data-button-align="right" data-details-border="withBorder" data-expand-icon="arrow" data-lock="false"><summary><h3 data-block-id="mit48zvq-n9miib-082"><strong>Are configuration files, IDs, or settings affected?</strong></h3></summary><div data-type="details-content"><p data-block-id="mit49bvf-ishzxh-084">No. The configuration directory remains the same. The newly installed client continues to use the <strong>same AnyDesk ID and settings</strong>.</p></div></details><button class="details-arrow" type="details"></button></div><div class="details-wrapper details-wrapper_rendered" data-type="details-wrapper"><details data-opened="true" data-button-align="right" data-details-border="withBorder" data-expand-icon="arrow" data-lock="false"><summary><h3 data-block-id="mit4ac0p-ftubf2-088" data-start="3548" data-end="3595">Do I need to update scripts or integrations?</h3><h4 data-block-id="mit4ac0p-zn4yms-089" data-start="3597" data-end="3709"></h4></summary><div data-type="details-content"><p data-block-id="mit4ab3e-b9gcsr-087">Yes. If you use automation tools or integrations, you must update them to reference the new path. This includes:</p><ul data-block-id="mit4axmf-u1tp6p-091" data-start="3711" data-end="3930"><li data-block-id="mit4axmf-z3sjng-092" data-start="3711" data-end="3733"><p data-block-id="mit4axmf-o9yish-093" data-start="3713" data-end="3733">Hardcoded file paths</p></li><li data-block-id="mig7ip5o-nk2e2s-196"><p data-block-id="mit4bgmz-j3cxbi-102" class="p1"><a href="/v1/docs/command-line-interface-for-windows" target="_blank" translate="no" rel="noopener">Direct calls to the executable</a></p></li><li data-block-id="mig7ip5o-gksgc8-197"><p data-block-id="mit4bpnx-18fele-103" class="p1"><a href="/v1/docs/url-handler" target="_blank" translate="no" rel="noopener">URL handler integrations</a></p></li><li data-block-id="mig7ip5o-gksgc8-197"><p data-block-id="mit4bpnx-18fele-103" class="p1">Automated deployment scripts</p></li></ul><p data-block-id="mit4bpnx-18fele-103" class="p1">Ensure these references point to the updated installation directory: <code>C:\Program Files (x86)\AnyDesk-{prefix}</code></p></div></details><button class="details-arrow" type="details"></button></div></div></editor360-faq></editor360-custom-block>
