WSL2.x 100% impossible to install on Windows home. even when fully updated everywhere.

[andemiddleton-web]

Windows Version

Microsoft Windows [Version 10.0.26200.7840]

WSL Version

Doesnt report properly. Only Version 2

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

WSL version: 2.6.3.0 Kernel version: 6.6.87.2-1 WSLg version: 1.0.71 MSRDC version: 1.2.6353 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26200.7840

Distro Version

NO WAY TO TELL

Other Software

NVIdia AI Workbench for Windows 64

ai-workbench-error-report-Owner-20260224-180313.zip

Repro Steps

Update Bios to latest version
Update windows to latest version
Purge system of EVERYTHING NVidia that may interfere with install
Verify the Window Features ON OFF settings to be correct as per EVERY SINGLE ONLINBE REFERENCE.
Powershell Purge the WSL via CLI under Admin.... and registry + App DATA locations (3) deleted.
Ensure every trace of the installers for both WSL LINUX aND nVIDIA AI Workstation is gone
Start windows with a clean NON FAST BOOT.
Reinstall WSL via CLI Admin and regular.
Ensure it is running
Verify every possible condition is met to facilitate install
Install Nvidia AI Workstation.
Installer runs.
Allow to Make changes to system. ok
installer runs.
Installs
Location manager pops up
Prompt to install a location.
Choose FULL LOCAL INSTALL
ADD LOCAL pops up (Use your local compute with AI Workbench
Will install and configure a container runtime and other dependencies. Learn more)
System verification test
Ready for full local installation...Click “Next” to select a container runtime
Click Next
Choose Either Docker Desktop or Podman
Click Next
Waiting for Administrator Privileges
Distribution Import Failed
Description
The distribution NVIDIA-Workbench is not installed, running the WSL import command failed

Re-run the installation flow
Source Error
View Log File
Failed to import distro

Error Code
0x1000000D
Re Running it makes no differencxe
Installing the linux distro from Microsoft store fails too

Expected Behavior

A working environment that supports WSL2 on MY system

Actual Behavior

A NONworking environment that supports WSL2 on MY system

Diagnostic Logs

WslLogs-2026-02-24_16-03-41.zip

[github-actions]

No logs.etl found in the archive. Make sure that you ran collect-wsl-logs.ps1 as administrator and that the logs.etl file is in the archive.

Diagnostic information

Multiple log files found, using: https://github.com/user-attachments/files/25532842/ai-workbench-error-report-Owner-20260224-180313.zip
appxpackage.txt not found
optional-components.txt not found
No logs.etl found in archive.
Error while parsing the logs. See action page for details

[andemiddleton-web]

Obviously This is broken too according to your GITHUB actions.
I followed instructions to the letter

[andemiddleton-web]

What?

[andemiddleton-web]

Im confused now

[andemiddleton-web]

I did what u asked now what?

[benhillis]

The trace should be started before you reproduce the issue, and stopped afterwards. If you are doing that and there are no WSL events in the log, that is odd. Have you already reported this to NVIDIA?

[Radu13]

I am using windows 10 home as well and I cannot install WSL properly with the .msi file
It loads some green bars etc. but no installation done confirmation at the end, why is this happening????

[Radu13]

Yeah it just closes itself at some point, this doesn't make any sense

[andemiddleton-web]

Turns out Windows T.P.S.(m) chip.... Y'know that totally useless chip microshaft plopped on to our new boards? The one that forced us to Upgrade from 10? It is part of the problem. Between it and WSL2.x being broken plus a known Windows kernal error on some installations (Canary build = mine :( ) You wont have a chance in hell of it ever working. Even when you install the four hour fix recommended by Windows. I have Queried NVidia Forums, TUFF Gaming Z series forums, Gemini LLM, Co Pilot LLM, Gemini Pro Tier LLM, Chat GPT LLM. There are no solutions. "Buy a new workstation or return the one you have." YUP! That's what they all ultimately said. *There is no solution online*. I went to Best Buy (Where I had my workstation assembled) to request help from the Geek Squad. The guy looked at me strangely, shrugged and handed me a 1-888 phone number to call. Clueless..... It is 2/26/26 @ 4pm PST as I write this. I plan to contact whoever is at that number tomorrow morning. It's gonna take all day or 2 mins. I just know it. If any body else has suffered this peril, please, be loud about it. It's messed up.

…

On Wed, Feb 25, 2026 at 2:58 AM Radu13 ***@***.***> wrote: *Radu13* left a comment (microsoft/WSL#14266) <#14266 (comment)> Yeah it just closes itself at some point, this doesn't make any sense — Reply to this email directly, view it on GitHub <#14266 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2N2QLC5QASRNAREVJWMQWD4NV55DAVCNFSM6AAAAACV6UB7X6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNJYGQ2DQNZRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[OneBlue]

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

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.

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.

Thank you!