WireGuard is the fastest, simplest VPN protocol to run on a desktop, and the official WireGuard client for Windows turns a connection into a single click once it is set up. This guide walks through WireGuard on Windows end to end in 2026: installing the official client, importing or creating a tunnel, activating it, verifying the handshake, and fixing the issues people hit on Windows.
Black Friday 2026VPN prices read on 16 Nov: Proton VPN Plus $59.76 for 24 months, Surfshark €67.23 for 27 months, next to a self-hosted VPS. See the dated comparison
No server yet? See the options after the steps
What you need before you start
- Windows 10 or 11 (the official client supports both; it runs as a system service).
- A running WireGuard server with a reachable public endpoint. This is the half WireGuard on Windows does not provide - you supply it with a self-hosted server on a Contabo VPS or a home Raspberry Pi with a forwarded UDP port.
- The client details for this device: either a complete
.conffile the server generated, or - if you "Add empty tunnel" - the server's public key and endpoint so you can finish the[Peer]section. Give each device its own key pair; reusing one config across machines breaks the handshake because two peers then share a public key.
No server yet? The Windows client only connects to one, it never hosts it: a Contabo VPS at €5.50/month runs a personal WireGuard server for every device you own.
If you're new to the protocol, our what is WireGuard explainer covers the cryptography and why it's faster than OpenVPN.
Step 1 - Install the official client
Download the Windows installer from the official site, wireguard.com/install. It installs the WireGuard GUI plus the background service that actually runs tunnels. Avoid third-party "WireGuard" downloads - a VPN client sees all your traffic, so the publisher matters. After installing, launch WireGuard; you'll see an empty tunnel list with Add Tunnel at the bottom.
Step 2 - Get or create a tunnel config
You have two real paths in the client, both genuine features of the Windows app:
- Import a
.confyour server made. If your server already generated a per-device config, this is the simplest route - skip to Step 3. - Add empty tunnel. Click the arrow next to Add Tunnel → Add empty tunnel…. The client generates a fresh key pair and shows the new public key at the top. Copy that public key to your server (add it as a
[Peer]), then fill in the rest of the config below.
Building your own server, with no .conf on either side yet? Our free WireGuard config generator creates the key pairs in your browser (nothing is sent to us) and writes a matching pair of files: the server wg0.conf to paste on your VPS and this Windows device's .conf to import in Step 3, with Endpoint, AllowedIPs and PersistentKeepalive = 25 already consistent on both sides. If you use it, you can skip the manual [Peer] work below. The generator is free with no account, up to 250 devices, and its ZIP export holds every client .conf and its QR code as a PNG, handy to set up a whole office or family in one go.
Generate your WireGuard configs here
Type your server address, choose the number of devices, then scan each QR code from the app.
All keys are generated in your browser (Curve25519 / X25519). Nothing is sent to our servers - your config stays 100% private.
Public IPv4 or domain of the machine that will run WireGuard. No server yet? Leave it empty and add it later.
Free, no account: up to 250 clients, each .conf with its QR code, and one ZIP with every file.
Everything the device sends to the internet goes through your server.
Advanced settingsTunnel subnet, DNS, site-to-site LANs. The defaults work for most setups.
Optional. Enter the LAN subnet behind the server and/or behind a client that acts as a site gateway (a router, a Raspberry Pi, a NAS). The generator adds each LAN to the server's AllowedIPs, gives every peer the routes to the other LANs, and writes the forwarding rules on the gateways. Leave a field empty for a normal client.
What you download
wg0.conf
for the server
client1.conf
one per device
QR (sample)
for the phone app
Illustration only: the lines and the QR code are fictional, no real key. Your real files are generated in your browser when you click.
Anatomy of a WireGuard .conf
A config has two sections. Here is the shape, with explicit placeholders - never paste real keys from a guide; your own server and client generate these:
[Interface]
PrivateKey = <this-device-private-key>
Address = 10.0.0.2/32
DNS = <dns-resolver-ip>
[Peer]
PublicKey = <server-public-key>
Endpoint = <server-host-or-ip>:51820
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 25
What each field does:
[Interface] PrivateKey- this Windows device's private key (kept local; never shared). With "Add empty tunnel" the client fills this in for you.Address- the VPN IP this device takes inside the tunnel, assigned by your server's addressing plan.DNS- the resolver used while connected; set it to your server or a trusted resolver so lookups don't leak.[Peer] PublicKey- the server's public key (not yours). A mismatch here is the top cause of a silent failure.Endpoint- the server's reachable host/IP and UDP port (commonly51820). For a home server this is your public IP and the forwarded port.AllowedIPs- which destinations route through the tunnel.0.0.0.0/0, ::/0is a full tunnel (everything); a narrow range like10.0.0.0/24is split-tunnel (only that subnet).PersistentKeepalive = 25- keeps the path alive behind NAT; useful when the Windows machine is behind a home router.
Step 3 - Import the tunnel and activate
If you have a .conf file: Add Tunnel → Import tunnel(s) from file…, pick the .conf, and it appears in the list. Select the tunnel and click Activate. Windows may prompt for administrator permission the first time, because the client installs a background service. The status switches to Active and you'll see live transfer counters.
Step 4 - Verify it's working
A connected tunnel isn't proof the VPN is doing its job. Check three things:
- Latest handshake - the tunnel panel shows a recent handshake time (a few seconds/minutes ago), not blank. A handshake means the two peers actually authenticated.
- Your public IP changed - visit any "what is my IP" page; it should show the server's IP, not your ISP's.
- No leaks - run a WebRTC leak test and confirm DNS goes through the tunnel with our WireGuard DNS-leak prevention guidance.
Quick answer: Install the official WireGuard client from wireguard.com/install, then either import a .conf file your server gave you (Import tunnel(s) from file) or use Add empty tunnel to generate a key pair and paste the server's [Peer] details. Click Activate, confirm the Latest handshake updates, and you're connected. WireGuard on Windows is only the client - it needs a WireGuard server to point at. No .conf yet? Our free WireGuard config generator writes one in your browser.
Tip: if the tunnel refuses to connect, the cause is almost always the port. See our guide to WireGuard's default port (UDP 51820) and how to open, forward or change it.
No server yet? The client needs a WireGuard server to connect to; a HostPapa Unmanaged VPS Lite (affiliate link, 2.95 $ a month on a 3-year term, then the regular rate) or a Contabo Cloud VPS (affiliate link) runs one with its own public IPv4, from 5.50 € a month on a 24-month term as read on 17 October 2026. If you would rather have a US host with a 30-day money-back guarantee, Ultahost VPS Basic is 5.52 $ a month on a 24-month term (1 GB RAM, dedicated IPv4, read on 21 October 2026), enough for a WireGuard server for a few devices. Choosing a host? Compare the best VPS for a VPN and Contabo vs Hetzner vs OVH on the price actually billed. HostPapa's Lite plan is the smallest one here: 1 core, 1 GB RAM, 25 GB NVMe and 4 TB transfer, unmanaged (root SSH on Ubuntu or Debian, no control panel, you install WireGuard yourself), enough for a WireGuard server for a few devices, 30-day money-back guarantee, read on 28 October 2026.
Troubleshooting on Windows
Built the server yourself? Paste the server config and the .conf you imported into Windows below. The checker derives each public key from the other side's private key and compares ports, AllowedIPs and the Endpoint, all in your browser: nothing is sent anywhere.
Check both files together: server wg0.conf and client .conf
Most failed handshakes are two files that do not match. Paste both; the keys are compared in your browser and never sent or stored.
WireGuard port checkerRebuild both files with matching keys: WireGuard config generator
Paste your wg show output, get a verdict per peer
Run sudo wg show on either end and paste the whole output. It is read in your browser, nothing is sent or stored.
wg show prints (hidden) in place of the private key, so its output is safe to paste.
- No handshake (stays blank): wrong Endpoint IP/port, the server's UDP port not open (or no router port-forward for a home server), or a mismatched public key. WireGuard stays silent to unauthenticated packets, so there's no error - verify the server is listening and reachable. Deeper steps in our handshake troubleshooting guide. The free WireGuard port checker flags CGNAT and writes the port-forward and firewall rules for your server.
- Windows Defender Firewall blocks it: allow the WireGuard outbound UDP connection if a strict firewall or third-party security suite drops it.
- DNS doesn't apply / lookups leak: make sure the
[Interface] DNSline is set; without it Windows may keep using your ISP's resolver inside a full tunnel. - Connected but no internet: with
AllowedIPs = 0.0.0.0/0the server must forward and NAT your traffic - if it doesn't, pages won't load. Check the server side, and lower the interface MTU (e.g.1280) if some sites stall. The free MTU calculator writes the exactMTU =line from your ping test or link type. - Full tunnel vs split tunnel:
AllowedIPs = 0.0.0.0/0, ::/0sends everything through the server; a narrow range sends only that subnet - pick based on whether you want full privacy or just to reach a home LAN. To keep the LAN or one address out of a full tunnel, the free AllowedIPs calculator turns "everything except X" into the ranges to paste. - The "WireGuard service": if a tunnel won't activate, check the service exists and is running in
services.msc(WireGuardTunnel$<tunnel-name>).
Auto-start: the tunnel as a Windows service
There's no mobile-style "always-on" toggle on Windows - and you don't need one. Activating a tunnel installs it as a Windows service (WireGuardTunnel$<tunnel-name>) that reconnects automatically and starts with Windows, so an active tunnel comes back up after a reboot. You can inspect or stop it from services.msc. That service model is how WireGuard stays persistent on Windows.
Config fields at a glance
| Field | Section | Role |
|---|---|---|
PrivateKey | [Interface] | This device's secret key (kept local) |
Address | [Interface] | The VPN IP this device uses inside the tunnel |
DNS | [Interface] | Resolver used while connected (prevents leaks) |
PublicKey | [Peer] | The server's public key |
Endpoint | [Peer] | Server host/IP + UDP port to reach |
AllowedIPs | [Peer] | Destinations routed through the tunnel (full vs split) |
PersistentKeepalive | [Peer] | Keeps the path alive behind NAT |
Your VPN hides your IP. It does not hide your browser.
A correctly configured WireGuard tunnel replaces the address a site sees. It changes nothing about what your browser announces on its own: fonts, screen, time zone, graphics stack. That combination is often unique enough to follow you across sessions, tunnel or no tunnel.
Measure your own browser fingerprint, passive, no questions, no account, no email. It tells you how many browsers out of N look like yours, and which attribute makes you stand out.
The bottom line
WireGuard on Windows is a few-minutes setup: install the official client from wireguard.com/install, import a .conf (or "Add empty tunnel" and finish the [Peer]), click Activate, then confirm the handshake and your new IP. The one thing the Windows client can't give you is a server to connect to. A Contabo VPS at €5.50/month runs a personal WireGuard server comfortably, or a home Raspberry Pi does the job.
If you do not have a .conf yet, our free WireGuard config generator generates the keys in your browser and gives you a server config plus client configs you can import straight into the Windows client.
Editorial guide based on the documented behaviour of the official WireGuard client for Windows. Security depends on your server configuration and key hygiene. Commercial links carry the rel="sponsored nofollow" attribute; an affiliate commission may apply at no extra cost to you.
Related reading: WireGuard on macOS
This guide assumes you already have a server to connect to. If not, our cheapest-VPS comparison for WireGuard is the shortest way to pick one.
Affiliate link
★ Nuremberg GDPR datacenter · ✓ Dedicated IPv4 included · 200 Mbit/s port
Self-host your VPN on your own VPS → ContaboCloud VPS 4 · 5,50 €/mo · Card or PayPal · orders from outside the EU accepted→Price checked 17 Oct 2026, 24-month term


