Docker Desktop - WSL update failed even after updating wsl from comman line (windows)

[azegurb]

Description

wsl update failed: a manual wsl update is required

Reproduce

Finish setting up Docker Desktop (version 4.28.0 or 4.32.0) - Use recommended setting (requires adminostrator password) -> Finish it says wsl update failed: a manual wsl update is required and docker desktops stops running

Expected behavior

docker must run as regular

docker version

4.28.0
wsl update failed: a manual wsl update is required

docker info

4.28.0

Diagnostics ID

A078EEDA-C3A2-48AF-A544-7C0CCAB570BA/20240706190548

Additional Info

No response

[Zenwoh]

What does wsl --version give you ?

[Rohanmrao]

I just had this issue resolved. I'm running windows 11. The way I fixed it was by using an older version of docker desktop (switched from 4.3 to 3.6)

wsl -l -v returns

  NAME                   STATE           VERSION
* docker-desktop         Running         2
  docker-desktop-data    Running         2

And I'm guessing this means everything works fine. I can even run containers successfully.

[tintronic1]

Description

wsl update failed: a manual wsl update is required

Reproduce

Finish setting up Docker Desktop (version 4.28.0 or 4.32.0) - Use recommended setting (requires adminostrator password) -> Finish it says wsl update failed: a manual wsl update is required and docker desktops stops running

Expected behavior

docker must run as regular

docker version

4.28.0
wsl update failed: a manual wsl update is required

docker info

4.28.0

Diagnostics ID

A078EEDA-C3A2-48AF-A544-7C0CCAB570BA/20240706190548

Additional Info

No response

I'm having this same issue. Just installed latest Docker version for Windows on a Windows 10 Professional OS. Each time I launch "Docker Desktop" the "Finish setting up Docker Desktop" version 4.31.1 (153621) prompts. I select "Use recommended settings) but get the "Dockder Desktop - WSL update failed" error with details:

wsl update failed: update failed: updating wsl: exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --update --web-download: %1 no es una aplicación Win32 válida. Error code: Wsl/CallMsi/Install/0x800700c1 : exit status 0xffffffff

I run diagnostics, got Diagnostic ID: B7059B34-D269-4091-99E7-2546388B5C66/20240709235224

running wsl --update responds with (spanish language) "%1 no es una aplicación Win32 válida. Error code: Wsl/CallMsi/Install/0x800700c1"

wsl --version gets me the same response.

[Rohanmrao]

@tintronic1 maybe try a downgrade of your Docker Desktop version ?

[Zenwoh]

I'm having this same issue. Just installed latest Docker version for Windows on a Windows 10 Professional OS. Each time I launch "Docker Desktop" the "Finish setting up Docker Desktop" version 4.31.1 (153621) prompts. I select "Use recommended settings) but get the "Dockder Desktop - WSL update failed" error with details:

wsl update failed: update failed: updating wsl: exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --update --web-download: %1 no es una aplicación Win32 válida. Error code: Wsl/CallMsi/Install/0x800700c1 : exit status 0xffffffff

I run diagnostics, got Diagnostic ID: B7059B34-D269-4091-99E7-2546388B5C66/20240709235224

running wsl --update responds with (spanish language) "%1 no es una aplicación Win32 válida. Error code: Wsl/CallMsi/Install/0x800700c1"

wsl --version gets me the same response.

@tintronic1 First Docker Desktop install ever or an update ? If it's the first install it seems to me that WSL is not installed on your machine, please visit this page to help you install WSL on Windows.

Not sure if those Win32 warnings have anything to do with Windows 32bit, but if you're running your OS in 32bit WSL won't work it seems.

[tintronic1]

I'm having this same issue. Just installed latest Docker version for Windows on a Windows 10 Professional OS. Each time I launch "Docker Desktop" the "Finish setting up Docker Desktop" version 4.31.1 (153621) prompts. I select "Use recommended settings) but get the "Dockder Desktop - WSL update failed" error with details: wsl update failed: update failed: updating wsl: exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --update --web-download: %1 no es una aplicación Win32 válida. Error code: Wsl/CallMsi/Install/0x800700c1 : exit status 0xffffffff I run diagnostics, got Diagnostic ID: B7059B34-D269-4091-99E7-2546388B5C66/20240709235224 running wsl --update responds with (spanish language) "%1 no es una aplicación Win32 válida. Error code: Wsl/CallMsi/Install/0x800700c1" wsl --version gets me the same response.

@tintronic1 First Docker Desktop install ever or an update ? If it's the first install it seems to me that WSL is not installed on your machine, please visit this page to help you install WSL on Windows.

Not sure if those Win32 warnings have anything to do with Windows 32bit, but if you're running your OS in 32bit WSL won't work it seems.

Hi @Zenwoh Thanks for your reply.

Yes, this is my first Docker Desktop install ever.

WSL is installed. I even manually downloaded the latest WSL (version 2.2.4) as suggested in an older post about this issue. However, running the install file says WSL version 2.2.4 is already installed. Using the Reinstall option had no effect.

[rfay]

I have this. Have current latest stable WSL, 2.2.4.0. Tried to install Docker Desktop 4.33.1. Manually updated WSL2 (but there's nothing to update). Still has the same thing. (Annoyingly, it refuses to downgrade back to 4.32.0, where it came from, saying it's up-to-date, so have to uninstall first.) Reverting to 4.32.0 seems to have solved the problem. DDEV test runner can run again.

Diagnostics ID: 714965AA-305C-4811-B395-B1F87D1BCF18/20240731225120

[valorisa]

Same here :

https://pastebin.com/WuGfRb6U [Diagnostics log]

[rfay]

The question I have is this:

Why does Docker Desktop think it has the right to update WSL for me? I didn't ask it to own my system. I don't think this is a correct design decision. I'll be happy to open a new issue. But why is it updating WSL?

[dahool]

I'm having the same issue with 4.33.1, the first start throw this error. second time it works.

I agree with @rfay tho, why Docker thinks it has the right to update wsl?

[vtsugi1]

Same issue for me. It only happens when Docker Desktop first launches upon startup. Then I have to close it and open it again, and it works fine. When I run as admin, it opens fine but not as a user. Seems like it's trying to do wsl --update or something that requires admin permissions every time it starts up?

Windows 11 x64, Docker Desktop 4.33.1 wsl -v WSL version: 2.2.4.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.61 MSRDC version: 1.2.5326 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26091.1-240325-1447.ge-release Windows version: 10.0.22621.3880

wsl --update Checking for updates. The most recent version of Windows Subsystem for Linux is already installed.

[tintronic1]

Well, since I was unable to make Doker Desktop run and could not find a solution, I stopped trying. A few weeks ago, while explaining the situation to a colleage I opened Docker Desktop to send him a prtscr, but it opened without issue!

I opened it again today and it is running. I did nothing docker-related inbetween. No update, no tinkering, nothing. There wasn't even a startup waiting time for some update, it just loaded without an issue.

To other people having this isse, is it still present or does it now load trouble-free?

[Zenwoh]

I opened it again today and it is running. I did nothing docker-related inbetween. No update, no tinkering, nothing.

Maybe windows updated WSL on it's own and that solved the issue for you (somehow) ?

[dahool]

Well, since I was unable to make Doker Desktop run and could not find a solution, I stopped trying. A few weeks ago, while explaining the situation to a colleage I opened Docker Desktop to send him a prtscr, but it opened without issue!

I opened it again today and it is running. I did nothing docker-related inbetween. No update, no tinkering, nothing. There wasn't even a startup waiting time for some update, it just loaded without an issue.

To other people having this isse, is it still present or does it now load trouble-free?

I'm still experiencing the same issue. I just stopped using docker desktop and started using it directly on wsl.