You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following WSL2 installation guide I get the following error while trying to convert WSL1 distro to WSL2.
the operation could not be started because a required feature is not installed.
Both VirtualMachinePlatform and Microsoft-Windows-Subsystem-Linux windows features are already enabled. I configured WSL2 as the default version and now even installing new distributions fail with the same error. And the GUI displays error "0x80370114", which I believe is the same as above. Detailed logs of the issue are attached. wsl2-log.zip
I believe there are many related and possibly duplicate open issues for installing/upgrading to v2 (including one I just closed #4573).
There doesn't seem to be access to more detailed errors/logs for the wsl2 installation/upgrade process and so problems which may have a shared set of root causes, can all show the same misleading message:
operation could not be started because a required feature is not installed
The catch-all response is quite unhelpful for addressing compatibility/install issues. Does anyone else think it would be worth while for me to open an "improved error messaging for wsl2 install" feature request ?
3, Click "Exploit protection settings" at the bottom
4, Switch to "Program settings" tab
5, Locate "C:\WINDOWS\System32\vmcompute.exe" in the list and expand it
6, Click "Edit"
7, Scroll down to "Code flow guard (CFG)" and uncheck "Override system settings"
8, Start vmcompute from powershell "net start vmcompute"
After doing the above Hyper-V Quick Create launched correctly.
I then went back and the command
wsl --set-version Debian 2
completed successfully.
Reacted by mtraudt, dvid, Licia, Liu Junnan, Yash Chamadia, Miguel Ortega Moreno, Joy Yeh, Peter W., Richard, Whitni Davis and 52 more
Reacted by Kunal Patil, Evgeniya Khasina, Marat Saidov, xukun, AnnareddyRaj, Wang Pin Shih, Chinnawat Wipawapat, Alexander Smirnov, Scott Harben, Léventé NAGY and 5 more
Reacted by Licia, aslaterhayes, Liu Junnan, Miguel Ortega Moreno, Joy Yeh, Richard, crusher, jude, Vincent, Qingsx and 14 more
Reacted by Vincent, Evgeniya Khasina, Marat Saidov, xukun, Wang Pin Shih, Alexander Smirnov, Scott Harben, xuanfengofo, Harish Anbalagan, Ultrasty and 2 more
After a recent Insider Slow Ring update the Code Flow Guard setting had reverted and WSL was refusing to start. I changed the setting again and then had to restart, after which it's working again.
I'm on 10.0.19025 Build 19025 - but I don't know if it's the most recent update that caused this.
Version 10.0.19033.1 - I am getting this error when I try to convert or try to run a wsl2 distro
wsl --set-version Ubuntu 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Error: 0xffffffff
and on a new distro (just installed through MS Store)
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0xffffffff
Error: 0xffffffff (null)
I've stopped DockerDesktop, checked for port 53 and it seems that dnscrypt-proxy.exe is using it.
I don't use docker or dnscrypt-proxy so I doubt anything in this issue is relevant. Reading around it seems that anything that binds to port 53 stops the WSL conversion process at least, so turn off anything using port 53 and see if that works.
Unfortunately I can't turn off dnscrypt-proxy.....or at least I haven't figured out how to do this. I stop the process, but it just restarts itself. I'm not sure which service is actually started it, but it appears that the logical one (DNS Client) is started via a trigger(?) so I can't stop/start/pause it in the services control panel app. Any ideas?
Had the 0xffffffff error on wsl --set-version Ubuntu 2. Had a service that used port 53. Confirm that after stopping the service the version update went ok.
Why does the Control Flow Guard keep resetting? It seems like every time I restart my machine, the setting reverts and I have to dig through the security settings again. How can I make this change permanent?
The conversion is underway, which may take a few minutes...
For information on the key differences with WSL 2, visit https://aka.ms/wsl2
There are no more endpoints available in the Endpoint Mapper.
The conversion is underway, which may take a few minutes...
For information on the key differences with WSL 2, visit https://aka.ms/wsl2
There are no more endpoints available in the Endpoint Mapper.
win10pro ver 19041.508
no idea
same issue 😕
OS version: 1909
OS build: 18363.1198
The conversion is underway, which may take a few minutes...
For information on the key differences with WSL 2, visit https://aka.ms/wsl2
There are no more endpoints available in the Endpoint Mapper.
win10pro ver 19041.508
no idea
Same deal here. Win10 x64 v19041.388.
I've been trying multiple things, most recently the instructions stated here, but sadly, nothing has worked.
Been craving to try WSL2 ever since I first heard of it back in September, when I brought up the problem in another existing issue post due to it supposedly having Linux like speeds as far as I heard, but it doesn't seem like someone who knows about WSL's inner workings will step in to lend us a hand anytime soon.
EDIT: I never edited this comment, but as I explained here, miraculously, the problem was solved when I reinstalled Windows 10 back in August 2021. It was the Version 2004 specifically. I'm currently on Windows 10 Version 21H2 and WSL2 is also working fine on it.
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.
Activity
[-]Failure converting WSL1[/-][+]Failure converting WSL1 distro to WSL2[/+]benhillis commentedon Oct 29, 2019
Awais Belal (@abelal) - Is virtualization enabled in your bios?
abelal commentedon Oct 30, 2019
Ben Hillis (@benhillis), yup.
benhillis commentedon Oct 30, 2019
Awais Belal (@abelal) - Does msinfo32 show virtualization is enabled?
ev-dev commentedon Oct 31, 2019
I believe there are many related and possibly duplicate open issues for installing/upgrading to v2 (including one I just closed #4573).
There doesn't seem to be access to more detailed errors/logs for the wsl2 installation/upgrade process and so problems which may have a shared set of root causes, can all show the same misleading message:
The catch-all response is quite unhelpful for addressing compatibility/install issues. Does anyone else think it would be worth while for me to open an "improved error messaging for wsl2 install" feature request ?
abelal commentedon Oct 31, 2019
I'm not sure which exact setting you want me to look at under msinfo32 but this is what I get through the task manager.

gajama commentedon Nov 13, 2019
Hi,
I had the same problem.
It occurred to me to see whether I could create a normal Hyper-V VM.
I had to disable and re-enable Hyper-V to get the Virtual Machine Management Service to run.
Once that was running I tried to use the Hyper-V Quick Create facility, as detailed here: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/quick-create-virtual-machine
But that failed to start correctly with a 'Not found' error. This led me to a Reddit post: https://www.reddit.com/r/HyperV/comments/9thubc/create_virtual_machine_returns_not_found_error/
With the following instructions:
After doing the above Hyper-V Quick Create launched correctly.
I then went back and the command
wsl --set-version Debian 2completed successfully.
mtraudt commentedon Nov 22, 2019
Gav Massingham (@gajama) Thank you so much! I tried the instructions you mentioned and they worked perfectly.
gajama commentedon Nov 22, 2019
mtraudt glad they worked for you too
gajama commentedon Nov 27, 2019
After a recent Insider Slow Ring update the Code Flow Guard setting had reverted and WSL was refusing to start. I changed the setting again and then had to restart, after which it's working again.
I'm on 10.0.19025 Build 19025 - but I don't know if it's the most recent update that caused this.
ssnyder commentedon Dec 4, 2019
Version 10.0.19033.1 - I am getting this error when I try to convert or try to run a wsl2 distro
I've stopped DockerDesktop, checked for port 53 and it seems that dnscrypt-proxy.exe is using it.
Any ideas?
gajama commentedon Dec 4, 2019
I don't use docker or dnscrypt-proxy so I doubt anything in this issue is relevant. Reading around it seems that anything that binds to port 53 stops the WSL conversion process at least, so turn off anything using port 53 and see if that works.
ssnyder commentedon Dec 4, 2019
Unfortunately I can't turn off dnscrypt-proxy.....or at least I haven't figured out how to do this. I stop the process, but it just restarts itself. I'm not sure which service is actually started it, but it appears that the logical one (DNS Client) is started via a trigger(?) so I can't stop/start/pause it in the services control panel app. Any ideas?
alexk111 commentedon Dec 13, 2019
Had the
0xfffffffferror onwsl --set-version Ubuntu 2. Had a service that used port 53. Confirm that after stopping the service the version update went ok.JudeLiu commentedon Mar 3, 2020
Great! gajama's solution works for me
2 remaining items
adpeyre commentedon Jun 19, 2020
I confirm, it works. Thanks! ;)
Sollace commentedon Aug 14, 2020
Can confirm, Gav Massingham (@gajama) 's solution works!
What's more, it appears to have also fixed Windows Sandbox.
fonnesbeck commentedon Sep 3, 2020
Why does the Control Flow Guard keep resetting? It seems like every time I restart my machine, the setting reverts and I have to dig through the security settings again. How can I make this change permanent?
xiaods commentedon Sep 11, 2020
even use the Gav Massingham (@gajama) steps. i also come across issue blow:
win10pro ver 19041.508
no idea
taseikyo commentedon Nov 13, 2020
same issue 😕
OS version: 1909
OS build: 18363.1198
LOuroboros commentedon May 18, 2021
Same deal here. Win10 x64 v19041.388.I've been trying multiple things, most recently the instructions stated here, but sadly, nothing has worked.
Been craving to try WSL2 ever since I first heard of it back in September, when I brought up the problem in another existing issue post due to it supposedly having Linux like speeds as far as I heard, but it doesn't seem like someone who knows about WSL's inner workings will step in to lend us a hand anytime soon.
EDIT: I never edited this comment, but as I explained here, miraculously, the problem was solved when I reinstalled Windows 10 back in August 2021. It was the Version 2004 specifically. I'm currently on Windows 10 Version 21H2 and WSL2 is also working fine on it.
ahminus commentedon Feb 24, 2022
I never would have figured this out without stumbling on Gav Massingham (@gajama)'s answer.
Those steps worked for me perfectly.
Thanks very much!
olegKusov commentedon Apr 22, 2023
Having same issue.
Windows 11 22621.1555
core i3 1215u
virtualization enabled
Halima-AddAndCo commentedon Jul 22, 2023
le dossier n existe pas qu es ce qu il y a d ecri dans le ficher
zulfanovita commentedon Apr 7, 2024
i want ask, what if there is no C:\WINDOWS\System32\vmcompute.exe. Should i add program to customize ?
oayoade commentedon Sep 26, 2024
same, did you find a fix?
tute123456 commentedon Nov 22, 2024
thx Gav Massingham (@gajama)
microsoft-github-policy-service commentedon Nov 27, 2025
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.
Thank you!