-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wsl-vpnkit and wsl 2.0.14 #252
Comments
Appears to be the same issue from #234 |
I'm doing some additional testing to rule out some third party software impacting this. |
I believe 2.0.14 resolves the issue with wsl-vpnkit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
wsl 2.0.14 has been released.
This is supposed to resolve a recent issue running wsl-vnpkit as a systemd service (which emerged with wsl 2.0.5). Per the release notes:
Disable the 'NoRemoteImages' process mitigation policy since it breaks execution of windows executables (solves microsoft/WSL#10812)
I've upgraded to 2.014, installed a fresh Ubuntu instance and setup a new wsl-vpnkit (all fresh). I'm following the same steps I've followed dozens of times prior.
When I run systemctl status wsl-vpnkit I get the following (please see attachment)
The text was updated successfully, but these errors were encountered: