diff options
| -rw-r--r-- | docs/known-issues.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/known-issues.md b/docs/known-issues.md index 2e9a2887d1..1a43886bf5 100644 --- a/docs/known-issues.md +++ b/docs/known-issues.md @@ -196,6 +196,18 @@ Windows host that Mullvad use to prevent leaks). This means that if there is a V up and running, the Linux guest’s traffic will be sent via the VPN with no leaks! In the other states, the mitigation above is used to prevent leaks. +#### Windows Sandbox + +The Hyper-V-specific firewall rules unfortunately do not apply to traffic from Windows Sandbox. +As a consequence, traffic from Windows Sandbox will leak during secured states, e.g. while switching +servers, or when disconnected with "lockdown mode" enabled. Another known issue with Windows Sandbox +is that DNS traffic is blocked when connected on the host OS, unless local network sharing is +enabled. + +We suggest installing and running the VPN inside Windows Sandbox, which solves both the issues of +leaks and DNS. It is possible to also run an instance of the VPN on the host without any conflicts, +as long as there are enough devices available on the account. + #### Edge using Application guard When running the Microsoft Edge browser with Microsoft Defender Application Guard activated, |