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

Wsl stopped working after windows updates #12501

Closed
2 tasks
lucastmendoncaf opened this issue Jan 25, 2025 · 13 comments
Closed
2 tasks

Wsl stopped working after windows updates #12501

lucastmendoncaf opened this issue Jan 25, 2025 · 13 comments

Comments

@lucastmendoncaf
Copy link

Windows Version

Microsoft Windows [versão 10.0.22631.4751]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

Trying to start the WSL application or any distros

Expected Behavior

Should be able to start normally after 5 months without using it

Actual Behavior

If i use > wsl on cmd it takes a while and says the services doesnt exists .

if i try to install by using the .msi it says the older version cannot be removed.

Already tried to remove and add again on windows features

Image

but at the same time it shows on the startup menu.
Image

with nothing on it

Image

And the distro i had still shows.
Image

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!

Closed similar issues:

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

@lucastmendoncaf
Copy link
Author

The only thing that works is 'wsl --help'

Image

WslLogs-2025-01-25_19-19-40.zip

Copy link

Diagnostic information
Detected appx version: 2.3.26.0
Detected user visible error: Wsl/ERROR_SERVICE_DOES_NOT_EXIST
Detected user visible error: Wsl/ERROR_SERVICE_DOES_NOT_EXIST

@lucastmendoncaf
Copy link
Author

lucastmendoncaf commented Jan 25, 2025

wsl --version also works

Image

Very similiar problem to: #11757

wsl --unregister ubuntu did not resolve my problem

Image

@mrcsdf
Copy link

mrcsdf commented Jan 26, 2025

Was using Azurelinux3 and 2 after a fresh install on my Asus Tuf 15 gaming laptop I cannot get things working at all with Hyperv and Virtual platforms + wsl supposadly enabled.

Seem to have issues with NVIDIA drivers or chipset not clear logs attached.

WslLogs-2025-01-26_09-55-50.zip

@mrcsdf
Copy link

mrcsdf commented Jan 27, 2025

Was using Azurelinux3 and 2 after a fresh install on my Asus Tuf 15 gaming laptop I cannot get things working at all with Hyperv and Virtual platforms + wsl supposedly enabled.

Seem to have issues with NVIDIA drivers or chipset not clear logs attached.

WslLogs-2025-01-26_09-55-50.zip

Seems upgrading from Home to Enterprise resolved the issues, though begs the question, Insider edition enabled on Home does not mean the feature is actually there.

@lucastmendoncaf
Copy link
Author

Was using Azurelinux3 and 2 after a fresh install on my Asus Tuf 15 gaming laptop I cannot get things working at all with Hyperv and Virtual platforms + wsl supposedly enabled.
Seem to have issues with NVIDIA drivers or chipset not clear logs attached.
WslLogs-2025-01-26_09-55-50.zip

Seems upgrading from Home to Enterprise resolved the issues, though begs the question, Insider edition enabled on Home does not mean the feature is actually there.

You upgraded windows?
I remember making mine the 11 pro version, then it was home again, i upgraded to pro again and did not fix, i will try making it with the enterprise version

Copy link

Diagnostic information
Detected appx version: 2.3.26.0
Detected user visible error: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG
Detected user visible error: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG

@lucastmendoncaf
Copy link
Author

@lucastmendoncaf
Copy link
Author

Image

get-AppxPackage MicrosoftCorporationII.WindowsSubsystemForLinux | Remove-AppxPackage

and then wsl is removed from my system components

@justus-camp-microsoft
Copy link
Collaborator

It looks like your .msi is corrupt. Can you follow these steps to remove the old WSL install?

https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d

@lucastmendoncaf
Copy link
Author

So i deleted the wsl folder, and did some more things including installing wslupdate.msi and now i was able to install the wsl.msi successfully.

"wsl -l" showed my docker install and i was able to run docker again.

"wsl --install" gave me an error

Image

I consider this a great sucess because i think i only need docker for now, if it doesnt work i will uninstall using this tools again

@lucastmendoncaf
Copy link
Author

Image

I rebooted, did "wsl --unregister ubuntu" and "wsl --install" and it worked.

I think now everything is fixed. thanks.

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

No branches or pull requests

3 participants