blakeduffey

I appreciate your feedback about the -user scope. There appears to be a bug with the manifest that is also in play https://github.com/microsoft/winget-pkgs/issues/36878

> Unfortunately, the workaround doesn't let you just "winget install Amazon.AWSCLI" without needed admin. This really needs to be fixed in the installer. This is the correct solution. All winget...

> We have not made investments in this tool in a while and so have not investigated cases where --info and the tool differ. @Forgind has looked into the tool...

I was hoping the experimental features would remove the need for wsl-vpnkit (as solid as it is) when working with a corporate VPN. Unfortunately, we aren't on the dev version...

> I no longer need to use wsl-vpnkit when running WSL 2.0.x on Windows 11, September 2023 release, with `networkingMode=mirrored` in `.wslconfig`. using a VPN?

Fwiw - WSL 2.0 works with wsl-vpnkit (on Windows 10) Again, I'm not using the experimental features which aren't compatible with 10

@craigloewen-msft - After upgrading to 2.0.5, wsl-vpnkit no longer works. Same with 2.0.6, upgraded this morning.

@craigloewen-msft - Did an uninstall (back to whatever the base version of Windows) and upgraded to 1.2.5.0 Wsl-vpnproxy works now. Something definitely up with 2.0.5 and above

> @blakeduffey we turned on Hyper-V firewall by default in that latest build and perhaps this is affecting you. > > Could you try upgrading back to 2.0.6 and then...

Verified that wsl-vpnkit does NOT work with 2.0.9.0