Skip to content

[ZT] WARP for Windows ARM #26381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2025
Merged

[ZT] WARP for Windows ARM #26381

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion ...flare-one/team-and-resources/devices/warp/troubleshooting/known-limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,21 @@ Below, you will find information on devices, software, and configurations that a

The WARP client does not run on Windows Server. Refer to the [downloads page](/cloudflare-one/team-and-resources/devices/warp/download-warp/) for a list of supported operating systems.

## WARP disconnected on Windows ARM

On Windows devices with ARM-based processors, the WARP client can sometimes get [stuck in a disconnected state](/cloudflare-one/team-and-resources/devices/warp/troubleshooting/common-issues/#unable-to-connect-warp) when you toggle on WARP (such as when installing WARP for the first time).

To work around this issue, you can temporarily remove the WARP network adapter:

1. Open the WARP client GUI and toggle WARP off.
2. In Windows, open Device Manager.
3. Select **View** > **Show hidden devices**.
4. Under **Network adapters**, find **Cloudflare WARP Interface Tunnel** and select **Uninstall device**.
5. Select **Attempt to remove the drive for this device**, then select **Uninstall**.
6. Toggle WARP back on.

WARP will now reinstall its network adapter, and the WARP client GUI should now show **Connected**.

## Managed network on legacy Windows Server

[Managed network detection](/cloudflare-one/team-and-resources/devices/warp/configure-warp/managed-networks/) will not work when the TLS certificate is served from IIS 8.5 on Windows Server 2012 R2. To work around the limitation, move the certificate to a different host.
Expand Down Expand Up @@ -159,7 +174,7 @@ Name: connectivity-check.warp-svc
Address: 127.0.2.3
```

## Windows App connection issue with WARP
## Windows App connection issue

When the WARP client is active on a local machine, users may be unable to connect to a Windows 365 PC using the [Windows App](https://aka.ms/WindowsApp). This issue does not affect browser-based connections to Windows 365.

Expand Down
2 changes: 1 addition & 1 deletion src/content/partials/cloudflare-one/warp/system-requirements/windows.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
| | |
| -------------------------- | ------------------------------------------------- |
| **OS version** | Windows 10, Windows 11, Windows 365 Cloud PC running Windows 11 |
| **Processor** | AMD64 / x86-64 |
| **Processor** | AMD64 / x86-64 or ARM64 / AArch64 |
| **.NET Framework version** | 4.7.2 or later |
| **HD space** | 184 MB |
| **Memory** | 3 MB |
Expand Down