-
Notifications
You must be signed in to change notification settings - Fork 821
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
Incorrect version message installing WSL #9193
Comments
Please make sure your system satisfies the conditions
|
Thanks for the quick reply. So you're saying my version 10.0.19045.2251 is not "Build 19041 and higher"? |
That "Build 19041 and higher" condition is probably for system's own WSL. I am not sure about the requirement for that specific KB update. Maybe keep smashing the 'check for update' button in Settings :) |
I just got some "optional" update, now my version is 10.0.19045.2311 and WSL works fine. |
The message is correct, Due to the way Windows 10 is versioned (specifically, the feature-pack releases), 10.0.19045.2251 is indeed older than 10.0.19041.2311. Edit: On reflection, https://learn.microsoft.com/en-us/windows/wsl/install is also correct, as it suggests Perhaps the Store-based installation could give more information in its failure report, e.g., "Go to Windows Update and install this KB" (or even a hyperlink to take you there), but the state of "depends on a in-preview system update" will probably only remain the case for a couple of weeks. |
Hi, thanks for the explanation!
😖 I've probably bumped into issues related to that before, but I don't use this so often that it stick around in my head. Maybe something to address in Windows 12! 😄 |
Version
Microsoft Windows [Version 10.0.19045.2251]
WSL Version
Kernel Version
N/A
Distro Version
N/A
Other Software
No response
Repro Steps
Got excited about WSL now including WSLg on Windows 10 so I wanted to give it a try.
wsl --update
says:so I thought I'd get it from the Windows Store as recommended.
Expected Behavior
WSL working
Actual Behavior
WSL not working
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: