Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*Server execution failed* while updating WSL 1 to WSL 2 #6397

Closed
yuis-ice opened this issue Jan 3, 2021 · 3 comments
Closed

*Server execution failed* while updating WSL 1 to WSL 2 #6397

yuis-ice opened this issue Jan 3, 2021 · 3 comments

Comments

@yuis-ice
Copy link

yuis-ice commented Jan 3, 2021

Environment

Microsoft Windows [Version 10.0.19041.685]

lsb_release -r: cannot access to the WSL now

Whether the issue is on WSL 2 and/or WSL 1: You can say this issue is about both of the versions

Steps to reproduce

I'm updating WSL to WSL 2 wsl --set-version Ubuntu 2 and it's been two hours already. And when I type command wsl --list -v this shows me an error server execution failed. What does this mean??

Expected behavior

This updating process should ends within minutes since it says "Conversion in progress, this may take a few minutes..." and also, I don't want to get this mysterious error message server execution failed

Actual behavior

PS > wsl --list -v
server execution failed

@yuis-ice yuis-ice closed this as completed Jan 4, 2021
@starkizard
Copy link

why was this closed?

@norandomtechie
Copy link

norandomtechie commented Feb 14, 2021

why was this closed?

I assume they figured it out.

I noticed this issue only after I tried restarting LxssManager from Task Manager > Services, but now it just says "Stopping" forever. I've tried starting it again from there as well as the Services MMC snap-in, but neither one works. Only a full restart seems to solve the issue.

@yuis-ice
Copy link
Author

yuis-ice commented Mar 7, 2021

I closed the issue because no one seemed to answer.

I solved the issue long while ago by myself.

This is just my case, so remember that how to solve the error may depends on your environment scenario. you know how ambiguous the error message is. must be all sort of problems will lead the same error.

For me, I solved the issue by disabling Virtual machine platform. Not only Hyper-v.

(similar case)

Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. · Issue #5363 · microsoft/WSL

Run the below in admin cmd/psl and reboot:

$ dism.exe /online /disable-feature /featurename:VirtualMachinePlatform /norestart
$ dism.exe /online /disable-feature /featurename:Microsoft-Hyper-V /norestart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants