I second Ale here since I am someone who tried to do exactly that, got it actually working (see this forum post), and then realised although it’s cool and all, it’s not worth it for me (post). There are minor drawbacks and it is just kind of overkill since I already use Fort Firewall to block a lot of the ‘dumb’ telemetry that Microsoft puts in many of its services.
If you still want to try it, in the post link you can see how I made it work for me. The minor drawbacks though:
- You can’t set a custom DNS, e.g. Quad9, in Windows settings because it causes DNS “leaks” (which means non-Mullvad DNS) while the VPN is on. So you need to keep it at “DHCP (automatic)”, which means when you turn off the VPN you will be using your ISP’s DNS.
But just using Mullvad VPN without Portmaster allows you to configure it to Quad9 without problems, and Quad9 is only used as the DNS when the VPN is off. (Lol sorry if this is confusing but that was a genuine drawback I noticed in my workflow). - Website loading time increases. I think it’s the DNS that needs to go through a separate tunnel with the DNS query leaving from local IP, while with only Mullvad VPN the DNS is going simply through the same tunnel which is faster.