-
Notifications
You must be signed in to change notification settings - Fork 851
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
WSL stopped working now reinstall failing #10760
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
You can give me feedback by thumbs upping or thumbs downing this comment. |
#10467 had a request for the output of PS C:\WINDOWS\system32> bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
isolatedcontext Yes
flightsigning Yes
default {current}
resumeobject {b59f727f-bfef-11ed-998e-f36a29ed52a8}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {b59f7281-bfef-11ed-998e-f36a29ed52a8}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
flightsigning Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {b59f727f-bfef-11ed-998e-f36a29ed52a8}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto |
According to the discussion in #10754 I tried turning off the Hyper-V features and it still didn't work. I tried turning off Hyperviser Platform as well and reinstalling and still go tthe same error code: PS path> wsl --install
Windows Subsystem for Linux is already installed.
The following is a list of valid distributions that can be installed.
Install using 'wsl --install -d <Distro>'.
NAME FRIENDLY NAME
Ubuntu Ubuntu
Debian Debian GNU/Linux
kali-linux Kali Linux Rolling
Ubuntu-18.04 Ubuntu 18.04 LTS
Ubuntu-20.04 Ubuntu 20.04 LTS
Ubuntu-22.04 Ubuntu 22.04 LTS
OracleLinux_7_9 Oracle Linux 7.9
OracleLinux_8_7 Oracle Linux 8.7
OracleLinux_9_1 Oracle Linux 9.1
openSUSE-Leap-15.5 openSUSE Leap 15.5
SUSE-Linux-Enterprise-Server-15-SP4 SUSE Linux Enterprise Server 15 SP4
SUSE-Linux-Enterprise-15-SP5 SUSE Linux Enterprise 15 SP5
openSUSE-Tumbleweed openSUSE Tumbleweed
PS path> wsl --version
Invalid command line option: --version
...
Usage: wsl.exe [Argument] [Options...] [CommandLine]
...
PS path> wsl --upgrade
Invalid command line option: --upgrade
...
Usage: wsl.exe [Argument] [Options...] [CommandLine]
...
PS path> wsl --update
Installing: Windows Subsystem for Linux
Windows Subsystem for Linux has been installed.
PS path> wsl --version
WSL version: 2.0.9.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.23403.1001
PS path> wsl
Windows Subsystem for Linux has no installed distributions.
Use 'wsl.exe --list --online' to list available distributions
and 'wsl.exe --install <Distro>' to install.
Distributions can also be installed by visiting the Microsoft Store:
https://aka.ms/wslstore
Error code: Wsl/Service/CreateInstance/GetDefaultDistro/WSL_E_DEFAULT_DISTRO_NOT_FOUND
PS path> wsl --install Ubuntu
Installing: Ubuntu
Ubuntu has been installed.
Launching Ubuntu...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x8007000d
Error: 0x8007000d The data is invalid.
Press any key to continue...
The installation process for distribution 'Ubuntu' failed with exit code: 1.
Error code: Wsl/InstallDistro/WSL_E_INSTALL_PROCESS_FAILED |
I tried turning the Virtual Machine Platform off and on again in Windows Features, also turned off WSL because on a fresh computer it seems enabling that option isn't required now that WSL is distributed in the Microsoft store. Still isn't working but I will try uninstalling and reinstalling after another reboot. |
Still not working, can't get any distro to work. Always get: WslRegisterDistribution failed with error: 0x8007000d
Error: 0x8007000d The data is invalid. I am afraid I might need to reinstall windows or something catastrophic. |
/logs |
Sorry about the late reply. I fixed my notification settings so it won't happen again. Please reopen the issue. |
Thank you @ivanthewebber: Unfortunately you're hitting a hyper-V issue because your Windows build is too old. The only solution to resolve this would be to update to a newer Windows build. |
@OneBlue, this is a company-managed device that is consistently updated running Microsoft Windows 11 Enterprise Insider Preview. Are you sure that is the problem and there is not a data inconsistency (e.g. WSL cached the version when first installed a few years ago and I failed to uninstall it entirely before reinstalling)? |
Please reopen this issue, I am running the newest available build. |
Try installing latest WSL from here: https://github.com/microsoft/WSL/releases/ Fix found here: https://answers.microsoft.com/en-us/windows/forum/all/wsl2-not-working-wslregisterdistribution-failed/f6a82483-bad8-49aa-8b7e-ed891eca029e |
Windows Version
Microsoft Windows [Version 10.0.23403.1001]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
N/A
Other Software
WSL is not working, so Docker is not working. Docker is not working so Apache Spark and Apache Flink are not working.
Repro Steps
Had WSL. Got windows update and had a problem with Apache Spark that I traced back to Docker. Docker gave me an error about WSL.
Tried opening WSL and it gave me an error about data being invalid. I looked online and it seemed that uninstalling and reinstalling WSL would fix the problem. I followed recommended steps here to initially uninstall before finding Microsoft documentation. I uninstalled WSL and attempted to install it from the store. I tried uninstalling it and reinstalling it several times using the command line trying to make sure all settings and features were right, and I restarted between everything. Have not been able to avoid getting the same error:
I tried other distributions and at this point I am pretty stumped. I saw this possibly related issue, but I can't change my computer's system clock.
Expected Behavior
wsl --install
would succeed and afterwardswsl
would open Ubuntu's shell.Actual Behavior
Error code: 0x8007000d
The output varies slightly if I change turn the Windows features on or off, but I always end up getting the same error code.
Output of Ubuntu:
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: