Skip to main content

Cloudflare One (Windows)

Overview​

Cloudflare One is the Zero Trust security agent that protects your device's internet traffic. This module covers downloading and installing the Windows client, and connecting it to the MCHMR network using your Tactical ID account.

note

This is the Windows desktop version. For the Android version installed through Watchtower's app catalog, see Cloudflare One (Android).

Prerequisites​

  • A Tactical ID account (username and password) — see New User Registration.
  • A Windows 10 or Windows 11 machine with admin rights to install software.
  • An internet connection.

Steps​

Part 1: Download and Install​

  1. Go to the Cloudflare One Client download page and click Download latest stable release under the Windows section.

    Step 1 - Cloudflare One Client Windows download page with system requirements and a Download latest stable release button

  2. Once the .msi file finishes downloading in your browser, click Open file to launch the installer.

    Step 2 - Browser download tray showing the Cloudflare_WARP .msi file with an Open file link

  3. Windows configures and installs Cloudflare One Client. This takes a few moments.

    Step 3 - Windows Installer dialog showing "Please wait while Windows configures Cloudflare One Client"

Part 2: First-Time Setup and Enrollment​

  1. When the client opens for the first time, it asks what you'd like to use it for. Select Cloudflare One Client (not Private Browsing) and click Continue.

    Step 4 - "What would you like to use the client for?" screen with Private Browsing and Cloudflare One Client options

  2. On the Enroll your device screen, enter mchmr as your team name and click Continue.

    Step 5 - Enroll your device screen with team name field filled in as mchmr

  3. Your default browser opens to the Tactical ID login page. Enter your Tactical ID username and password, then click Log in.

    Step 6 - Tactical Identity Platform login page with username field filled in

  4. After logging in, your browser asks to open Cloudflare One Client. Check Always allow mchmr.cloudflareaccess.com to open links of this type in the associated app, then click Open.

    Step 7 - Browser dialog asking to open Cloudflare One Client, with Always allow checked

Part 3: Connecting​

  1. Back in the client, you'll see a Login successful confirmation, then the Disconnected screen. Click Connect.

    Step 8 - Cloudflare One Client showing a Login successful toast over the Disconnected state

  2. The client briefly shows Connecting... while it validates your DNS configuration.

    Step 9 - Cloudflare One Client showing a Connecting state at 79 percent

  3. Once connected, the client shows Connected — your DNS queries and included routes are now protected.

    Step 10 - Cloudflare One Client showing a Connected state

The client remembers your enrollment, so you won't see the team name or login screens again — toggle Disconnect/Connect on the Home screen any time.

Understanding Split Tunneling​

By default, this connection uses split tunneling — only traffic to a specific set of addresses is routed through Cloudflare's network while you're connected. Everything else (general internet browsing, apps unrelated to MCHMR) bypasses the tunnel entirely and goes out through your normal network connection as usual. Being Connected does not mean all of your traffic is going through MCHMR — only what's on this list is.

To see the current list yourself, click Settings in the left navigation, then open Split Tunnel.

Split Tunnel settings dialog listing the addresses routed through Cloudflare's network

The list includes Cloudflare's own infrastructure ranges, plus the domains *.mchmr.ai and *.c2pcmobile.com.

Screenshots​

Inline above, next to each step.

Troubleshooting​

  • If the browser doesn't prompt you to open Cloudflare One Client after logging in, make sure the client is still running (check your system tray) and try logging in again.
  • If your team name doesn't work, confirm you entered mchmr exactly — this is case-sensitive.
  • If the client gets stuck on Connecting..., disconnect and reconnect. If it persists, verify your machine has a working internet connection.