You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/team-and-resources/devices/warp/troubleshooting/known-limitations.mdx
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,21 @@ Below, you will find information on devices, software, and configurations that a
14
14
15
15
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.
16
16
17
+
## WARP disconnected on Windows ARM
18
+
19
+
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).
20
+
21
+
To work around this issue, you can temporarily remove the WARP network adapter:
22
+
23
+
1. Open the WARP client GUI and toggle WARP off.
24
+
2. In Windows, open Device Manager.
25
+
3. Select **View** > **Show hidden devices**.
26
+
4. Under **Network adapters**, find **Cloudflare WARP Interface Tunnel** and select **Uninstall device**.
27
+
5. Select **Attempt to remove the drive for this device**, then select **Uninstall**.
28
+
6. Toggle WARP back on.
29
+
30
+
WARP will now reinstall its network adapter, and the WARP client GUI should now show **Connected**.
31
+
17
32
## Managed network on legacy Windows Server
18
33
19
34
[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.
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.
0 commit comments