I've added the PowerShell 7 executable to ProtonVPN's split tunneling include list, but Invoke-RestMethod fails with a requested address error. Running curl.exe from PowerShell shows my ISP IP instead. qBittorrent works when included, and PowerShell works when split tunneling is disabled.
I'm on Windows 10 using ProtonVPN 5.1.5 and PowerShell 7.6.3. Is there something else I need to include?
curl.exe is a separate program, even when you launch it from PowerShell. Add its executable to the include list if you want that traffic to use the VPN too. Its ISP IP result doesn't tell you whether the PowerShell process itself is being tunneled.
First check that the running process is actually the PowerShell 7 executable you added, rather than Windows PowerShell 5.1 or another installation. You can run $PSVersionTable and $PSHOME in that session, then compare the executable location with the entry in ProtonVPN.
That won't necessarily fix the address error, but it rules out a path mismatch before you dig further.
Invoke-RestMethod uses .NET networking, so the error could involve how the VPN's split tunneling interacts with that network stack. The details of ProtonVPN's implementation aren't established here, though, so I wouldn't assume a particular .NET version is the culprit.
Since it works with split tunneling off, this is worth sending to Proton support with the exact error, executable path and version information. Include the fact that another app works in include mode.
Exclude mode is a possible workaround if it works on your setup. The tradeoff is that it reverses the policy: apps use the VPN unless you exclude them, rather than only the selected apps using it. That may not match your original goal.
c.29~foghorn:
Exclude mode does work here, so I'll use that for now and start by excluding the browser.
Answers are reviewed before publication.
c.29~foghorn:
That explains the curl result. The cmdlet error is still the confusing part, though.