wsl --install -d Ubuntu hangs at 0% installation, then error 0x8000000d and wsl --shutdown freezes

[Gassoumi-Mohamed]

Windows Version

Voici le rapport corrigé avec ces informations. Vous pouvez copier-coller ceci directement dans le formulaire GitHub. Title wsl --install -d Ubuntu hangs at 0% installation, then error 0x8000000d and wsl --shutdown freezes Windows Version Microsoft Windows [Version 10.0.22631.6199] (Windows 11 Famille 23H2) WSL Version 0.0.0.0 (cannot run wsl --version because WSL commands hang) Are you using WSL 1 or WSL 2? WSL 2 Kernel Version 5.4.72 (default, but unable to verify because distro fails to install) Distro Version Ubuntu 22.04 LTS (also tried Ubuntu 20.04 and 24.04 – same behavior) Other Software Docker Desktop 4.29+ (failed to start due to WSL issue) Repro Steps Open PowerShell as Administrator. Run wsl --install -d Ubuntu. Download completes successfully (100%). Installation starts but stays at [0,0%] indefinitely. Close the terminal. Try to launch Ubuntu from Start Menu → a black terminal opens with error: Error: 0x8000000d Une modification d'état illégale a été demandée. Run wsl --shutdown – command hangs forever (no output, must force close terminal). Try installing from Microsoft Store → same result (download OK, installation stuck at 0%). Expected Behavior Ubuntu should install completely, reach 100%, and then prompt for a username/password. WSL commands like wsl --list, wsl --shutdown should work normally. Actual Behavior Installation freezes at 0% progress. After killing the installation, any attempt to start a distribution gives error 0x8000000d (illegal state change). wsl --shutdown hangs indefinitely. Even after disabling/re-enabling WSL features via DISM and rebooting twice, the issue persists. Diagnostic Logs No logs available because WSL commands do not respond. The issue occurs on a fresh Windows 11 Home installation with no third-party antivirus, only Windows Defender. Conseil : Si vous le souhaitez, je peux aussi vous aider à rédiger un message plus court si le formulaire limite la longueur. Dites-moi.

WSL Version

Version WSL : 2.7.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.4.72 (default, but unable to verify because distro fails to install)

Distro Version

Ubuntu 22.04 LTS (also tried Ubuntu 20.04 and 24.04 – same behavior)

Other Software

Docker Desktop 4.29+ (failed to start due to WSL issue)

Repro Steps

Open PowerShell as Administrator.

Run wsl --install -d Ubuntu.

Download completes successfully (100%).

Installation starts but stays at [0,0%] indefinitely.

Close the terminal. Try to launch Ubuntu from Start Menu → a black terminal opens with error:
Error: 0x8000000d Une modification d'état illégale a été demandée.

Run wsl --shutdown – command hangs forever (no output, must force close terminal).

Try installing from Microsoft Store → same result (download OK, installation stuck at 0%).

Expected Behavior

Ubuntu should install completely, reach 100%, and then prompt for a username/password. WSL commands like wsl --list, wsl --shutdown should work normally.

Actual Behavior

Installation freezes at 0% progress.

After killing the installation, any attempt to start a distribution gives error 0x8000000d (illegal state change).

wsl --shutdown hangs indefinitely.

Even after disabling/re-enabling WSL features via DISM and rebooting twice, the issue persists.

Diagnostic Logs

No logs available because WSL commands do not respond. The issue occurs on a fresh Windows 11 Home installation with no third-party antivirus, only Windows Defender.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[chemwolf6922]

HI @Gassoumi-Mohamed , You could still collect the logs in this condition. Please follow the bot's suggested steps and share the log to help us triage this issue. Thanks.