WSL: "No such interface supported" after upgrade to windows store version of wsl
Version
Microsoft Windows [Version 10.0.19044.2311]
WSL Version
- WSL 2
- WSL 1
Kernel Version
No response
Distro Version
Ubuntu
Other Software
No response
Repro Steps
I had wsl2 working just fine then when i saw wsl 1.0 was released for win10 i wanted to give it a try. installed KB5020030 and then ran a “wsl --update” store version of wsl was downloaded and installed after this was done, any attempt to run wsl.exe results in
No such interface supported
Error code: Wsl/0x80004002
and then wsl doesnt work any more.
interesting side note: using a different account on the same computer that never used wsl before, i was able to get wsl started and installed, most likely using the pre-windows store version because linux kernel ended up being 4.4 instead of 5.10 something. on that account, running wsl --update makes wsl break with above “No such interface” error and uninstalling the store version from Settings -> Apps makes it work again and wsl session uses the same old 4.4 kernel.
Expected Behavior
A working startup of wsl like before
Actual Behavior
Error: “No such interface supported” and then it doesnt start
Diagnostic Logs
No response
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 4
- Comments: 27
I‘ve been hitting this issue recently. After some random effort, I can reproduce this and fix it quite easy. As @tjnsn said. run
wsl --updatewill corrupt your wsl command. Remove the Appxpackage that updating installed will get your wsl back. RunGet-AppxPackage |? { $_.Name -like "*WindowsSubsystemforLinux*" }in powershell to get the package fullname, and remove it usingRemove-AppxPackage -Package "<packag-full-name>"The actual wsl you’re using is probably in “Setting -> Application” called “Windows Subsystem for Linux Update”.I have found a workaround for the problem that does not require adding the “authenticated users” group to the “users” group. The problem is that WSL wants to run a process in the App Package folder, but the permissions for the System Account do not allow it because the permission inheritance has been broken.
If you start a CMD as System Account using PSEXEC (
psexec -i -s cmd.exe) and set the permissions of the folder with the commandicacls C:\ProgramData\Microsoft\Windows\AppRepository\Packages\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\PackagedCom /grant System:(OI)(CI)(X) /inheritance:dcorrected, WSL2 works with the latest release.Why the permissions in the directory are wrong, Microsoft would have to answer. However, this is a workaround, with which you can you don’t have to soften the company policy.
Probably you will have to correct the permissions again after each update.
same problem here. Can’t uninstall the “store app” - it seems like it’s in a bad state. Please help - this is a huge productivity killer for me. Also, it’s pretty shameful that you recommended people to perform this upgrade and it completely bricks their wsl environments.
This did the trick for me. Thank you very much @AZ-201
any update to this? the issue still happens with kb5021233 installed (the non preview version)
With the just released v2.0.0 preview version of wsl the problem appears to be solved. Upgraded a test computer from 1.2.5 to 2.0.0 and started wsl without adding authenticated users back and without adjusting the previously discussed folder permissions and it started just fine.
with the experimental dns tunneling (not tested it yet since it requries an insider preview version of windows) and the authenticated users problem my main two problems appear to finaly be solved.
now i just have to wait until next stable relase and hopefully some future windows update.
My workaround is to add back: “NT AUTHORITY\Authenticated Users” to the local Users group and then restart the service WslService This service is unfortunately listed with the name: ms-resource:AppName so it was not immediately obvious it is WSL related. (would be nice with a proper name for the service)
Would be nice with some input from microsoft about this, for example is it a must to have authenticated users in the users group or is there a way to make it work without it (prefered due to company policies) @OneBlue ?
I’m prety sure i know what is triggering this error for me. due to company policy many security related settings have been adjusted, one of them is removal of the default groups “interactive” and “authenticated users” from the local “Users” group.
this in turn causes something in wsl to fail, not sure what exactly, but i suspect it is some user related service or something, perhaps related to the integration of wsl and windows side. and then when you try to do somethign with wsl, all you get is “no such interface” and the error code. wsl --version works but wsl --list does not and errors
adding back the two groups plus a reboot makes it work again, but that is not realy a workabl solution in the long run.
@chrisjaquet This works for me absolutely. Thank you.
As another sample point I ran into also this issue after a fresh install of Windows 10. After installing Windows I installed the WSL from the Windows Store. After installation completed, running the
wslcommand would giveA reboot does not fix this.
Also, running
wsl --install ubuntuleads to the following output:which is the error mentioned here and at #9014.
To get things working I removed both WSL and the Ubuntu install using “Apps & Features”. Once that was done, from the command line I ran
wsl --install --no-distribution:After rebooting, I could install Ubuntu (and other distributions happily). It seems that when installing from the Windows Store directly it does not install the required dependencies:
I was not sure that it was installing the Windows Store version of WSL, but going into the Windows Store app it only has the option to “open” and running X apps works correctly, so I am assuming that it has installed the store version of the app.
any update to this? only the inbox version can running correctly. once install the store version then everything broken
Unfortuneately,
Get-AppxPackage |? { $_.Name -like "*WindowsSubsystemforLinux*" }did not return anything for me when ran in powershell as admin.