WSL: WSL2: error 0x80370109 while installing ubuntu on wsl2

  • Your Windows build number: 10.0.19041.208

  • What you’re doing and what’s happening: I installed ubuntu from microsoft store, when I first run, I got this error:

    Installing, this may take a few minutes...
    WslRegisterDistribution failed with error: 0x80370109
    Error: 0x80370109 ???????????????????
    
    Press any key to continue...
    

    image

    I’m using Surface Pro with Windows 10 Home Edition,The language on my system is simplified Chinese and the country in my system is People’s Republic of China.

    I also installed docker desktop edge and it works perfect.

  • What’s wrong / what should be happening instead:

    The error message should be correct displayed.

I couldn’t see the detail error message, I don’t know if this issue is duplicated to #4103

logs.zip

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Comments: 46 (1 by maintainers)

Most upvoted comments

For others coming across this while previewing Sun Valley / Windows 11, I also had to run wsl --update before I could get unblocked here.

I had the same experience, I tried enabling and disabling multiple times, fresh installs of WSL. I got it working finally by going into the services.msc and turning off and restarting the Hyper V compute service. This caused my docker desktop to crash and I restarted it once I had restarted the Hyper V compute service. I then ran the ubuntu 20.04 installer with WSL default version set to 2. IT FINALLY loaded and prompted me for a new Unix user. I am not entirely sure why this worked, something I found was the folder that holds the ubuntu defaulted to the compression attribute, I kept seeing the error op had mixed with a compression error the first time I tried to run after reboot. This is located in /Users/$User/Appdata/Local/Packages/CanonicalGroupLimited. Under properties and advanced attributes, unchecked the compression. Doing this alone did not solve it for me, I had to restart the Hyper V Compute Service. I hope that this may help someone. Was very frustrating… but yay WSL 2.

i have no clue if this is gonna help anyone else, but just in case, i’ll post what fixed it for me:

i was struggling with this issue for a long time and it was absolutely frustrating. none of the solutions online helped at all. just a few moments ago, however, i stumbled upon my old .wslconfig file that i had made 2 years ago and completely forgot about.

after opening it up in notepad, i immediately remember what i had done here: the last time i had WSL up and running, i felt that by default it was using too much ram for my taste, and i wanted the bare minimum to be able to run some minor things on it (which was AFTER the installation of a distro)

i had the RAM limit for WSL set to 256MB of RAM. which, unsurprisingly, was causing all subsequent attempts at distro installations to fail. upping that limit to 6144MB / 6GB immediately fixed the issue and I was able to finally install distros.

for reference, here is what my .wslconfig looks like now:

[wsl2]
memory=6144MB
processors=8

even if you don’t already have this file in your user folder, maybe you could try creating this file (put it in C:\Users\YourProfile) and seeing if it makes any difference (of course adjusting these based on your actual system specs) but at minimum i would set it to whatever the official minimum RAM requirement is for the distro you’re wanting to install

Trying to install wsl on Windows 11 running in a VM. Have run the following to enable nesting VMs:

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

I ran wsl --install and I think it completed successfully.

I then run wsl -l -v, which tells me:

Windows Subsystem for Linux has no installed distributions.

So, I run wsl --install -d Ubuntu and get:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370109
Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.

Press any key to continue...

What am I missing? Is this scenario also covered by the inbound fix?

wsl_0x80370109

I’m using Windows 10 Home Edition,there is no Hyper-V…

Nothing of aforementioned helped to me.

Weirdly enough, I did run

wsl --shutdown <my_distro_name>

And then I could run that distro again!

can confirm that running wsl --update fixes it. Despite it saying “no updates available”, running the ubuntu app (which registers ubuntu) works after that

I wast times with this issue. Next I just run Ubuntu app under administrator. Who would have thought! It works!

Can confirm that uninstalling KB5043145 fixed the issue (which started after it was installed).

Win 11 device(Surface Laptop Studio) wsl --update fixed the issue

Same as OP here. Windows 10 Pro, Hyper-V enabled, Virtual Machine Platform enabled. Went through everything suggested in https://github.com/MicrosoftDocs/WSL/issues/404 too.

Tried uninstalling by unticking Windows Subsystem for Linux, reboot, tick it again, reboot. Same error.

I have got it to work by opening Ubuntu_2004.2020.424.0_x64.appx with 7Zip, extracting install.tar.gz, and installing it using wsl --import from an adminstrator cmd.

The only slight issue is that the script that creates a user didn’t run so when I run bash I am ‘root’. I created a user in linux using useradd but I can’t see how to make new bash sessions default to that user.

My problem was resolved

1). Resolved after uninstalling the cumulative update for Windows 11, KB5043145. https://github.com/microsoft/WSL/issues/12087

2). Other option: wsl.exe --set-default-version 1 wsl.exe --install -d Ubuntu wsl.exe --set-default-version 2

It still doesn’t work with Docker, but at least WSL responds and works.

Updating to the pre-release version (1.3.15) works for me. Nothing else worked on Windows 11 (10.0.22621.1992), updated to July 2023.

> wsl --update --pre-release
Checking for updates.
Updating Windows Subsystem for Linux to version: 1.3.15.

Thank you @dbaileyut, updating to prerelease 2.0.7 and then launching Ubuntu as Administrator worked for me when nothing else worked.

Updating to the pre-release version (1.3.15) works for me. Nothing else worked on Windows 11 (10.0.22621.1992), updated to July 2023.

> wsl --update --pre-release
Checking for updates.
Updating Windows Subsystem for Linux to version: 1.3.15.

@prism2001 Thank you so much. I tried everything online but your answer was the only thing that helped. I just realized that I had created a .wslconfig file and had put memory=4 which caused wsl to produce the following error “The operation timed out because a response was not received from the virtual machine or container.” As soon as I removed it; BOOM! Everything started working normally.

Win 11 device(Surface Laptop Studio) wsl --update fixed the issue

this as well as stopping running instances and installing via wsl --install <>

Confirming that enabling Hyper-V got rid of the error. Then I got another error 0xc03a001a. That one got resolved by disabling compression as in https://github.com/microsoft/WSL/issues/4103#issuecomment-633773493.

Update: that error only occurred on older (~10 y.o. i7) computer. I also installed wsl2 on another computer - brand new Lenovo Yoga and the install succeeded without enabling hyper-v.