Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • WSL instances run under WindowsTerminal.exe, so you may try to exclude it, then run the WSL distribution.
    – harrymc
    Commented Dec 4, 2023 at 15:39
  • "Split tunnel" feature that allows me to select an application The problem is, traffics from VMs do not originate from a (local) "application" (unless the hypervisor provide the connectivity with something like "userspace NAT", which is not the case of Hyper-V or WSL). Network stack level IP forwarding is what is involved behind the scene. What you need would be alternate routing for some/all forwarded traffics. It is feasible in Linux. Not so sure about Windows.
    – Tom Yan
    Commented Dec 4, 2023 at 15:51
  • @harrymc I don't have Windows Terminal installed so WindowsTerminal.exe is not present in my machine.
    – rettiseert
    Commented Dec 5, 2023 at 15:00
  • 1
    You may exclude whatever is the executable. If unsure, get Process Explorer and drag the bullseye icon over the window.
    – harrymc
    Commented Dec 5, 2023 at 15:07
  • Could you explain how you've removed/prevented the installation of WindowsTerminal.exe? That is a core function of Windows now, and how you've modified your system may be relevant to finding the correct answer to this problem you're facing. Commented Dec 5, 2023 at 15:20