Ошибка no such interface supported

$ wsl -l
No such interface supported
Error code: Wsl/0x80004002

Figuring it was about time anyway, I did «Reset PC» (reinstalled Windows, keeping personal files but removing all apps). This problem persists even after re-installing Windows!

I suppose there still could be something in my home directory (profiles) that is interfering with WSL, but it seems increasingly unlikely. Perhaps this is a hardware issue? FWIW I am using a Lenovo ThinkPad X1E, 1st Gen (Circa 2019).

Thanks for the logs, it looks like when the WSL msix package was installed, the interface for talking to wslservice.exe was not added. Could you try removing the WSL app and re-installing it from the store?

Thanks for the logs, it looks like when the WSL msix package was installed, the interface for talking to wslservice.exe was not added. Could you try removing the WSL app and re-installing it from the store?

I did try that with no effect.

Yesterday I did take the extreme step of wiping the drive and doing a fresh install of Win 11, keeping no files. After that, the WSL app installed and Initialized without error. Thus it is likely that something in my user profile was interfering with the WSL app. Perhaps an environment variable/user registry setting?

Likely something COM-related since that’s the interface that wsl.exe is trying to use. If somebody gets into this state I’d like to inspect some reg keys to see if the interface is actually registered.

i got the exact same issue.
had wsl installed, then installed kb5020030 (win10 19044.2311 (21H2)), started wsl and got notification to run wsl —update.
the update ran fine, then when i start wsl i get

No such interface supported
Error code: Wsl/0x80004002

wsl.exe command fails all the time with above error even «wsl /?» or «wsl —help» result in above error
Ideas how to fix it?

Same problem after upgrading

No such interface supported
Error code: Wsl/0x80004002

Which command to run to get diagnostics, like these registry keys/values?

Having the same problem, after Upgrading from Win11 21H2 to 22H2 via inplace upgrade. Same result with wsl.exe --upgrade or starting the install directly from the microsoft store.

«Could you try removing the WSL app and re-installing it from the store?»

I just found out that I get the same error for other Store Downloads. Just tried to install the update of «Windows Alarm & Clock», also Code 0x80004002… probably has nothing to to with WSL itself, but is rather a Store issue?

WSL package can be installed from release page with Add-AppxPackage command in Powershell.

WSL from appstore appears to be installed so i dont think thats the issue, also i have completely removed wsl by unregistering all dists, removing all wsl stuff from add/remove programs included Settings/apps and the optional windows components and then reinstalled it again via wsl —instal and get exactly the same issue

also side note, because this issue was closed i created a new one related to this #9202

WSL package can be installed from release page with Add-AppxPackage command in Powershell.

worked for me, thanks!

I had this same problem the other day too. It was a fresh install of Windows 10 Pro with 22H2, so there was almost nothing on it.

First, I installed WSL from the Windows Store. After that, I installed Ubuntu 22.04.1 LTS and got the same error message when trying to start Ubuntu:

No such interface supported
Error code: Wsl/0x80004002

Then I tried different iterations of installing/re-installing Ubuntu 20.04.5 and 22.04.1 from the Windows Store and through the terminal, downloading and installing/re-installing 1.0.3 and 1.0.0 from the aforementioned release page, downloading and installing/reinstalling WSL from the Windows Store, and no progress. I even tried enabling the «Windows Subsystem for Linux» option in the «Turn Windows features on or off» settings page and still nothing. I finally got Ubuntu 22.04.1 LTS spun up when I switched to WSL1:

wsl --set-default-version 1

As soon as I switched to WSL1, Ubuntu fired up immediately without any additional tinkering.

So it’s possible the issue may be with WSL2. This is probably not the ideal fix if you’re hard set on using WSL2, but if you want to just get a system up and running, switching WSL1 may work for you until a solution for WSL2 is found.

The message Error code: Wsl/0x80004002 comes from WSL Store version. So, installing/uninstalling a distribution would not work. Only installing/uninstalling the WSL Store version is the preferred way. Whereas WSL1 uses system WSL which is already registered.

I can think of some workarounds like registering WSL Store version after extracting in different directory or registering the COM interface manually. But those will be a concern from security standpoint.

I met the same issue too….

I run into the same issue right after a reboot, and I guess maybe some upgrade of the Windows mass up the WSL.
I really don’t want to reinstall the core because I have to install tons of things with a fresh WSL like docker, python, etc.
So I searched «wsl.exe» with my «Everything» and found there’s a «wsl.exe» under C:WindowsWinSxSamd64_microsoft-windows-lxss-wsl_31bf3856ad364e35_10.0.19041.2311_none_f7a4fa53841d8f4e
I started that wsl.exe and it worked. All the docker images are there.
But starting my debian from the StartMenu still gives me 0x80004002.

So if you are a lazy guy who don’t want a reinstall of WSL like me, try to search and execute every «wsl.exe» under C:WindowsWinSxSblablabla..

I hope that helps.

I had good luck fixing this by doing a wsl install this way:

I had good luck fixing this by doing a wsl install this way:

Are you sure this installs the latest version?
Can you check what «wsl —version» shows? (if anything)

I had good luck fixing this by doing a wsl install this way:

Still gives me Wsl/0x80004002

I had good luck fixing this by doing a wsl install this way:

Are you sure this installs the latest version? Can you check what «wsl —version» shows? (if anything)

wsl —status gives

Default Distribution: Ubuntu
Default Version: 2

Windows Subsystem for Linux was last updated on 3/25/2023
WSL automatic updates are on.

Kernel version: 5.10.102.1

Please, I need help too. Mine is still showing error

Open powershell as admin run this

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

Ensure that CPU virtualization is enabled in the BIOS. It’s dependent on your CPU and motherboard.

See this comment here: #9202 (comment)

This did the trick for me.

wsl --update will corrupt your wsl command.
Remove the Appxpackage that updating installed will get your wsl back.
Run Get-AppxPackage |? { $_.Name -like "*WindowsSubsystemforLinux*" } in powershell to get the package fullname, and remove it using Remove-AppxPackage -Package "<packag-full-name>"

Likely something COM-related since that’s the interface that wsl.exe is trying to use. If somebody gets into this state I’d like to inspect some reg keys to see if the interface is actually registered.

I’ve been having this issue for a while now… What reg keys do you need to inspect?