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 update crashed Windows error after reboot Class not registered Error code: Wsl/0x80040154 #9064

Closed
1 of 2 tasks
pbolduc opened this issue Oct 24, 2022 · 24 comments
Closed
1 of 2 tasks

Comments

@pbolduc
Copy link

pbolduc commented Oct 24, 2022

Version

Microsoft Windows [Version 10.0.22621.674]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

Unable to fetch due to class not registered error.

Distro Version

Unable to fetch due to class not registered error.

Other Software

image

Docker Desktop 4.13.0

Repro Steps

I ran wsl.exe --update today and it caused Windows 11 to crash/reboot. No blue screen, just reboot. Now when I try to run any WSL item (docker desktop, Ubuntu shell, wsl.exe) I get the following error.

C:\Users\Phil>wsl
Class not registered
Error code: Wsl/0x80040154

I see Windows Subsystem for Linux Preview in Windows Store "Modified minutes ago". However, trying to open from the store also give the same error code.

Class not registered
Error code: Wsl/0x80040154
Press any key to continue...

Expected Behavior

Expected the wsl.exe --update to install correctly.

Actual Behavior

WSL is broken. I suspect the old WSL was uninstalled and the installer crashed before the new install completed.

Diagnostic Logs

  • confirmed "Windows Subsystem for Linux" is still turned on in Windows Features
  • WSL is configured for 64 GB of RAM which is half of the installed RAM of 128GB.
  • WSL is configured for 8 CPU which is half of my Threadripper 16 Core, 32 Thread CPU
  • WSL has been installed and working fine for a year and half

WSL logs attached

WslLogs-2022-10-24_10-16-10.zip

@pbolduc pbolduc changed the title Update crashed Windows error after reboot Class not registered Error code: Wsl/0x80040154 WSL update crashed Windows error after reboot Class not registered Error code: Wsl/0x80040154 Oct 24, 2022
@pbolduc
Copy link
Author

pbolduc commented Oct 24, 2022

Seems to be the same error as #8746

@mshumsky
Copy link

Getting the same error since running wsl --update and was bluescreened.
Repair button doesn't help whatever on WSL or distro app.

@mshumsky
Copy link

mshumsky commented Oct 24, 2022

Getting the same error since running wsl --update and was bluescreened. Repair button doesn't help whatever on WSL or distro app.

Found the trick.

  1. Uninstall Windows Subsystem for Linux Preview app from Microsoft Store [settings (win+i) > app]
  2. Run wsl command in cmd (run as administrator)

@pbolduc

@pbolduc
Copy link
Author

pbolduc commented Oct 24, 2022

@mshumsky Thank you. I will delay this fix for one day to give the WSL team a chance to request additional diagnostic information from my system. However, tomorrow, I will need Docker and WSL working.

@L1ghtman2k
Copy link

Just happened to mee too :/. Blue screen into, into:

wsl --update
Class not registered
Error code: Wsl/0x80040154

@OneBlue
Copy link
Collaborator

OneBlue commented Oct 24, 2022

Thank you for reporting this @pbolduc and @L1ghtman2k.

Uninstalling and reinstalling the app would be the best way to solve this, but I'd still be curious to know why your machines crashed.

Can you please follow the 9) Collect WSL logs with Feedback hub section and share the feedback hub link so we can have a look ?

@pbolduc
Copy link
Author

pbolduc commented Oct 24, 2022

Thank you for reporting this @pbolduc and @L1ghtman2k.

Uninstalling and reinstalling the app would be the best way to solve this, but I'd still be curious to know why your machines crashed.

Can you please follow the 9) Collect WSL logs with Feedback hub section and share the feedback hub link so we can have a look ?

I have collected WSL logs with Feddback hub and submitted it.

@ghost ghost removed the needs-author-feedback label Oct 24, 2022
@OneBlue
Copy link
Collaborator

OneBlue commented Oct 25, 2022

Thank you for reporting this @pbolduc and @L1ghtman2k.
Uninstalling and reinstalling the app would be the best way to solve this, but I'd still be curious to know why your machines crashed.
Can you please follow the 9) Collect WSL logs with Feedback hub section and share the feedback hub link so we can have a look ?

I have collected WSL logs with Feddback hub and submitted it.

Thank you. Can you please share the feedback hub link ?

@fsvenson
Copy link

I just ran into the same problem, added diagnostics to feedback hub here https://aka.ms/AAii1uw

@pbolduc
Copy link
Author

pbolduc commented Oct 25, 2022

Feedback link: https://aka.ms/AAij3rb

@benhillis benhillis added the failure-to-launch failure to launch label Oct 25, 2022
@chkzack
Copy link

chkzack commented Nov 18, 2022

I got the same issue too. I used command wsl --update and it crushed.And It just worked after i uninstall the newly installed 'windows subsystem for linux'.

@OneBlue
Copy link
Collaborator

OneBlue commented Nov 19, 2022

Thank you @pbolduc.

Can you please follow 10) Reporting a Windows crash (BSOD) the section to share a kernel dump ?

@mikekol
Copy link

mikekol commented Nov 20, 2022

@OneBlue This just happened on my machine as well. The instructions you link to ask for a full dump of a BSOD; I've got a minidump of it. Would that be good enough to send?

@OneBlue
Copy link
Collaborator

OneBlue commented Nov 21, 2022

Yes please @mikekol. If you have a minidump of the crash please send it

@ispy1
Copy link

ispy1 commented Nov 28, 2022

face the same issues. uninstall Windows subsystem for linux update preview and reboot it also show Error code: Wsl/0x80040154, how can i fix it?

@ispy1
Copy link

ispy1 commented Nov 28, 2022

face the same issues. uninstall Windows subsystem for linux update preview and reboot it also show Error code: Wsl/0x80040154, how can i fix it?
uninstall Windows Subsystem for Linux and run "wsl --update" it fix

Snipaste_2022-11-28_21-38-29

@mikekol
Copy link

mikekol commented Nov 28, 2022

@OneBlue Sorry for the delay - I've just sent it off. Thanks!

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 1, 2022

Thanks @mikekol.

I confirm that we received the dump. The root cause is the same as #9143.
The fix is on the way but hasn't been released yet.

@ghost ghost closed this as completed Dec 8, 2022
@ghost
Copy link

ghost commented Dec 8, 2022

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

@iourit
Copy link

iourit commented Jan 18, 2023

@OneBlue I looked at the minidump and there is a chance that this is a new issue. There is not enough data in the minidump to tell conclusively.
@mikekol Could you share a full kernel memory dump?

@iourit iourit reopened this Jan 18, 2023
@mikekol
Copy link

mikekol commented Jan 19, 2023

@iourit Unfortunately (for debugging purposes), I can no longer reproduce the issue.

@iourit
Copy link

iourit commented Jan 19, 2023

@iourit Unfortunately (for debugging purposes), I can no longer reproduce the issue.

@mikekol Did you upgrade the OS build since you had this issue? There was a related fix.

@ghost ghost closed this as completed Jan 26, 2023
@ghost
Copy link

ghost commented Jan 26, 2023

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

@benhillis
Copy link
Member

Fixed with https://github.com/microsoft/WSL/releases/tag/1.1.7.

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

No branches or pull requests

10 participants