HCS_E_CONNECTION_TIMEOUT on i9-14900HX (Legion) after resolving Component Store Corruption (14098)

[pflodin631]

I am unable to install or register any WSL2 distribution (specifically Ubuntu-24.04). The installation consistently downloads but then sits at 0% when installing before failing with HCS_E_CONNECTION_TIMEOUT.

appxpackage.txt
bcdedit.txt
HKCU.txt
HKLM.txt
optional-components.txt
P9NP.txt
windows-version.txt
Winsock2.txt
wpr.txt
wslservice.txt
wslsupport-impl.txt
wslsupport-proxy.txt

Windows Version: Windows 11 (Image Version: 10.0.26200.8037)

WSL Version:
WSL 2 (Default Version set to 2)

Kernel Version:
5.15.153.1 (or latest available)

Hardware:

CPU: Intel Core i9-14900HX (24 Cores / 32 Threads)

GPU: NVIDIA GeForce RTX 4080 Laptop GPU

System: Lenovo Legion Pro 7i

Steps taken to troubleshoot:

Enabled VT-x and VT-d in BIOS.

Disabled Undervolt Protection in BIOS.

Enabled "Virtual Machine Platform," "Windows Subsystem for Linux," and "Windows Hypervisor Platform" in Windows Features.

Ran dism /online /cleanup-image /restorehealth and sfc /scannow (fixed initial 14098 error).

Attempted netcfg -d and Winsock resets to fix the virtual switch.

Attempted manual .appx installation of Ubuntu-24.04.

Disabled "Memory Integrity" (HVCI) and confirmed VBS is off via bcdedit /set hypervisorlaunchtype off (tested both 'off' and 'auto').

Actual Behavior:
Every attempt to register a distro results in:
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS_E_CONNECTION_TIMEOUT

Additional Context:
This is a fresh high-end Legion setup. There are no third-party firewalls or antiviruses installed besides Windows Defender. Docker Desktop was previously installed but has been fully disabled/quit during troubleshooting.

[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'.