ProtonVPN win-app: one OpenVPN config for every server, and a driver that answers SERVFAIL
Official ProtonVPN Windows app
At a glance
- What is it?
- The official Proton VPN Windows client, built as eighteen projects across C#, C++ and a Go submodule, shipping a patched OpenVPN, a patched TAP adapter and a kernel-mode callout driver. The component breakdown in its readme is unusually specific, and it explains what the app does that a tunnel alone would not.
- Who is it for?
- Use this repository when you want to understand or build the official Proton VPN Windows client, since it is the whole product rather than a sample: a GUI, a Windows service, a tunnel process, a network adapter and a kernel driver. Two things to know before you build it.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- ProtonVPN/win-app2,616 ★ · +72
| Repository | 2026-09-30 | 2026-11-13 |
|---|---|---|
| ProtonVPN/win-app | 2.5k | 2.6k |
72 Stars in the last 44 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Three patch releases in four minutes
The three listed releases are 5.1.6, 5.1.7 and 5.1.8, and all three were tagged on 2026-09-22 within four minutes of each other, the last one at the same minute as the recorded push. That pattern is what a batch of rebuilds looks like rather than three planned releases, so the tag list says more about the release pipeline than about the product. Meanwhile the copyright line at the top of the readme still reads 2023, and the file is attributed to Proton AG. Nothing else in the visible text carries a year, so the notice is the only place a reader would look for one and it has not moved with the releases.
Five parts, two of them patched forks
The app is described as five interacting parts: the GUI application, the Proton VPN Service, OpenVPN, the TAP adapter, and the split tunnel driver. Two of those are not stock. The OpenVPN binary is built from official source with a patch applied to support the Proton specific TAP adapter, and the patch lives in its own repository. The TAP adapter itself, named TAP-ProtonVPN Windows Adapter V9, is likewise built from official source with a patch to give it a Proton specific name and identification, again in a separate repository. So a change to either the tunnel or the adapter is not made here but in the fork, and the two repositories have to be kept in step with this one.
The OpenVPN configuration is the same for every server
One sentence is worth pulling out of the OpenVPN section: the configuration file is static and does not change for each VPN server. The tunnel process itself is not static, since a new OpenVPN process is started on every connect and closed on disconnect, and communication with it is maintained through a TCP management interface. So server selection happens through that management channel rather than by rewriting the config file, which is why the config can stay fixed and why the file needs no per-server templating. The binary itself is installed into a Resources directory inside the versioned install path rather than being dropped into the system OpenVPN location.
DNS leak protection is a kernel driver that fabricates an answer
The callout driver is described as a kernel mode driver used for two things. The first is redirecting socket bindings when split tunnel is enabled, which is what decides which traffic goes into the tunnel. The second is preventing DNS leaks, and the mechanism is unusual enough to state exactly: for DNS requests made from interfaces other than the one Proton VPN is using, the driver sends a SERVFAIL response packet. So a query that should have gone to a resolver the tunnel does not cover is answered locally with a failure rather than being allowed to resolve. The driver is installed as a system service and is started on connect and stopped on disconnect by the Proton VPN Service, not by the GUI.
A Debug-only config file can turn off certificate pinning
The GUI application section describes a configuration file named ProtonVPN.config that sits in the app directory, is read by a build using the Debug configuration, and is not deployed during installation. If it is missing or holds invalid values, the app saves the defaults it is already using. The readme then explains how to monitor HTTP traffic with Fiddler or another tool, which may require disabling TLS certificate pinning, and gives the value to put in the file for that: an empty pinning configuration object.
...
"TlsPinningConfig": {}
...The scope is limited in two ways. The file is only read by Debug builds, and it is not shipped by the installer. That makes it a development affordance rather than a production one, and it is the sort of switch worth knowing about when you audit a build you did not produce.
Two log directories and two levels of privilege
The GUI app writes to a per-user path under the local application data directory, while the service writes to a machine-wide path under the all users profile. That split follows from who runs each process. The service executable also accepts install and uninstall as command line arguments, and the readme says plainly that this method does not configure service security settings, which is the reason the installer sets the service to be started and stopped by unprivileged interactive users instead. The service owns the interaction with OpenVPN, the Windows firewall and the split tunnel driver, so it is the component that decides when the tunnel and the driver exist at all.
Eighteen projects and a Go submodule
The solution is C# and C++ on WPF with MVVM, and the project list is where the structure shows. There is the main app project holding startup logic, views and view models; a callout driver project in C++; a shared common library; the core business logic; an error message project that builds to its own executable for when the app cannot run at all; installer action projects in C++; two firewall libraries, one in C++ and a C# wrapper around it; a C# wrapper around Windows system libraries; a network configuration library in C++; a Windows service and its contract; a TAP install action; a command line utility that verifies the VPN server certificate; and the update module with its own Windows service and contract. One folder is a surprise: the source tree holds a git submodule of a Go library from a mail client project, for the secure remote password protocol.
Two documented folders are not in the tree, and CI is not GitHub
The folder structure section describes a ci folder with continuous integration scripts, a packages folder holding NuGet packages of the solution, a Setup folder, src and test. The repository root holds the Setup and ci directories and src, but no packages folder and no test folder, so at least one of the two is generated rather than committed, which the text does not say. The Setup folder is the interesting one: it holds an installer project, its resources, built installers, and three subfolders for images, built TAP adapter installers and the split tunnel driver, with a hard dependency stated in the readme that the latest successfully built TAP adapter installer is required before the app installer can be built. Continuous integration is GitLab, not GitHub, with a templates file beside the pipeline, and the security side has a scanner configuration file and a directory of its own.
Editorial conclusion
Use this repository when you want to understand or build the official Proton VPN Windows client, since it is the whole product rather than a sample: a GUI, a Windows service, a tunnel process, a network adapter and a kernel driver. Two things to know before you build it. The OpenVPN configuration is static and does not change per server, and the tunnel binary is built from upstream with a patch for the Proton adapter, so it is not stock OpenVPN. And the DNS leak protection is a callout driver that fabricates a SERVFAIL answer, which is a kernel component with its own start and stop lifecycle driven by the service.
Frequently asked questions
Does the ProtonVPN Windows app require a paid subscription?
The app is intended for every Proton VPN service user, paid or free, and supports all functionalities available to authenticated users. Signup happens on the website rather than in the app.
What are the five components of the ProtonVPN Windows app?
The GUI application, the Proton VPN Service, OpenVPN, the TAP adapter, and the split tunnel callout driver. OpenVPN and the TAP adapter are both built from official source with Proton specific patches.
Where does the ProtonVPN Windows app write its logs?
GUI application logs go to the Logs directory under the local application data path for ProtonVPN, and service logs go to the Logs directory under the all users profile path.
How does the ProtonVPN Windows app prevent DNS leaks?
With a kernel mode callout driver that redirects socket bindings when split tunnel is enabled and sends a SERVFAIL response packet for DNS requests made from interfaces other than the one Proton VPN uses.
How do I inspect ProtonVPN Windows app traffic with Fiddler?
Provide a configuration file with an empty TlsPinningConfig value, written as "TlsPinningConfig": {}, to disable TLS certificate pinning. That file is only read by Debug builds and is not deployed during installation.
Which continuous integration does the ProtonVPN Windows app use?
GitLab CI. The root holds a pipeline file and a pipeline templates file, and the solution uses the newer XML solution format with a separate license header file beside it.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/protonvpn-win-app)Star history chart for your README
[](https://hysenlabs.com/projects/protonvpn-win-app)Was this useful?