I replaced my paid VPN app with a feature Windows already had — and it works perfectly

My VPN app stopped working a few weeks ago. I'd been using Windscribe for a while, mostly for the occasional geo-unblock and the usual public Wi-Fi reasons. Then one evening, it just refused to connect. I switched protocols, restarted the app, restarted my PC, and tried every server location on the list, but nothing worked.

I was ready to uninstall it and shop around for a replacement when I remembered Windows has its own VPN client buried in Settings. I figured I'd plug my Windscribe server details into it as a temporary fix while I sorted out the app. That was a few weeks ago. I never went back to the app, and I haven't looked at another VPN provider since. If you don't have a paid VPN account, you can pair the built-in client with a free public VPN server and get the same result.

Windows has a built-in VPN client, and it's free

A native option that's been hiding in Settings since Windows 10

If you haven't noticed it already, Windows has shipped with a built-in VPN client since Windows 10. It's mainly aimed at corporate users connecting to a company network, which is probably why it doesn't get much attention in consumer circles. That doesn't mean it's useless for the rest of us, though.

If you already pay for a VPN service and just need an occasional connection, the built-in client saves you from running yet another background app. It also gives you faster access from the Quick Settings panel, so you can flip the VPN on or off without hunting for a tray icon. And if you only want to occasionally unblock a geo-restricted site or browse as a visitor from another country, it's a perfectly fine free option once you have server credentials to plug in.

You'll find it under Settings > Network & Internet > VPN. From there, click Add VPN, and you're walked through a small form where you enter the server, protocol, and sign-in details. The supported protocols are:

• IKEv2: A modern, fast protocol that handles network changes well, making it the best default for most setups.
• SSTP: A Microsoft-developed protocol that tunnels traffic over HTTPS, which helps it slip through restrictive firewalls.
• L2TP/IPsec: An older but widely supported option that pairs L2TP for tunneling with IPsec for encryption, configurable with a certificate or a pre-shared key.
• PPTP: The oldest of the bunch, fast but cryptographically weak, and best avoided unless nothing else is available.
• Automatic: Lets Windows pick a protocol from the list based on what the server accepts.

The one thing it doesn't support is the modern stuff: there's no WireGuard and no OpenVPN. That's a real limitation, and I'll come back to it in the final section.

You can plug in your own VPN server, or a free public one

Bring your own credentials from a paid provider or a free service

Microsoft doesn't run any VPN servers of its own, so the client is just an empty shell until you give it somewhere to connect. You have two practical options: use credentials from a VPN you already pay for, or grab them from a free public server.

I went with my existing Windscribe subscription. On the Windscribe website, I opened the Config Generators page, picked OpenVPN, and then realized Windows can't use those files directly. So I switched to the IKEv2 generator instead, chose a location, and clicked Get Credentials to reveal the username and password specific to my account. Those went straight into the Windows VPN dialog along with the server hostname, and the connection worked on the first try.

If you don't have a paid plan, two free services actually let you do this manually: VPN Gate and VPNBook. VPN Gate is run by the University of Tsukuba in Japan and lists hundreds of volunteer-run relays across many countries, with SSTP support that pairs nicely with the Windows client. To use one, copy a server hostname from vpngate.net, paste it into the Server name or address field, set the VPN type to Secure Socket Tunneling Protocol (SSTP), and use vpn as both the username and password. VPNBook works similarly but uses PPTP, with credentials posted directly on its homepage that refresh periodically. PPTP is older and weaker, so I'd treat VPNBook as a last resort.

Most other free VPNs don't qualify for this approach because they're app-only and never expose raw credentials. There's also a more advanced route, where you spin up a small VPS and use the popular hwdsl2/setup-ipsec-vpn script on GitHub to run your own server, but that's a project of its own and outside the scope of a quick switch.

It's not a full-fledged VPN client

Lighter and quieter, but missing the features that power users rely on

Switching to the built-in client cleared a surprising amount of clutter. There's no background process from a third-party app, no telemetry going to a vendor I have to trust, and no startup launcher quietly updating itself. If you went the free route, you also save the monthly fee. The Quick Settings integration is genuinely convenient, and because IKEv2 supports MOBIKE, the connection survives clean transitions between Wi-Fi and a phone hotspot without dropping.

That said, the built-in client only covers the VPN basics. It's not a full suite, so you'll find plenty of features missing that you'd normally expect from a dedicated VPN client. The biggest one is that there's no kill switch. If the tunnel drops, your traffic silently falls back to your regular ISP connection, which is exactly the kind of moment you'd want a VPN for. There's also no one-click server hopping, no built-in DNS leak protection, and no obfuscation for networks that actively block VPN traffic. Streaming services that the big VPN apps work hard to unblock will mostly see straight through this setup.

The protocol gap matters is another thing to consider. WireGuard is faster and more modern than anything Windows ships with, and its absence is the single thing I miss most. Leaning on free servers also brings its own risks. Sticking to free VPNs for everything is one of the common ways people end up using their VPN incorrectly, and the built-in client doesn't change that.

Still a very usable built-in VPN client on Windows

If you already pay for a VPN and only connect occasionally, the built-in client is a quiet, lightweight way to keep using what you've already bought without another app on your machine. It also works as a free option for casual geo-unblocking or basic privacy on public Wi-Fi, as long as you understand its limits.

If you stream constantly, torrent, or live somewhere with active VPN blocking, this may not be enough, and a proper client is still the right call. But for most everyday situations, some VPN is better than no VPN, and Windows already gives you one for free.