Skip to content
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

WSL1 problems after Windows 11 24H2 Upgrade #12415

Closed
1 of 2 tasks
WiredWonder opened this issue Dec 27, 2024 · 7 comments
Closed
1 of 2 tasks

WSL1 problems after Windows 11 24H2 Upgrade #12415

WiredWonder opened this issue Dec 27, 2024 · 7 comments
Labels

Comments

@WiredWonder
Copy link

Windows Version

Microsoft Windows [Version 10.0.26100.2605]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

n/a

Distro Version

n/a

Other Software

n/a

Repro Steps

I run WSL1 for some basic linux stuff that does not warrant the WSL2 hyper-v solution.

  1. Install WSL1 on Windows 11
  2. Upgrade to 24H2

Expected Behavior

WSL1 works

Actual Behavior

WSL Doesn't work. When I attempt to start any WSL instance:

` Windows Subsystem for Linux must be updated to the latest version to proceed. You can update by running 'wsl.exe --update'.

For more information please visit https://aka.ms/wslinstall

Press any key to install Windows Subsystem for Linux.

Press CTRL-C or close this window to cancel.

This prompt will time out in 60 seconds. `

Diagnostic Logs

No response

Copy link

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-networking-logs.ps1, following the instructions here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@WiredWonder
Copy link
Author

/question

I am not that keen on posting logs publicly. What analysis is needed on which logs? Nothing stands out in the zip file created.

Copy link

Diagnostic information
Found '/question', adding tag 'question'

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 31, 2024

@WiredWonder: wsl is not part of the Windows image anymore. As the error message says you can download WSL by either running wsl --update, or pressing a key when the above error message is displayed.

@OneBlue OneBlue closed this as completed Dec 31, 2024
@WiredWonder
Copy link
Author

WiredWonder commented Jan 1, 2025

Thanks @OneBlue , will this install WSL1 or WSL2 as the message implies?

I would like to keep WSL1.

@WiredWonder
Copy link
Author

wsl --update immediately started installing WSL2 with no easy way to abort (no response to CTRL+C).

Can anyone tell me how to get WSL1 installed on 24H2?

@haodeon
Copy link

haodeon commented Jan 7, 2025

Encountered the same issue after upgrading to 24H2.

Ran wsl.exe --update as per the error message. It installed WSL and automatically enabled Windows feature Virtual Machine Platform. Then it requested to reboot.

Before rebooting I turned off Virtual Machine Platform Windows feature.

After the reboot the existing WSL1 distro starts as normal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants