search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.48k stars 822 forks source link

KB5043145 breaks WSL2 #12090

Open wlvchandler opened 1 month ago

wlvchandler commented 1 month ago

Windows Version

Microsoft Windows [Version 10.0.22631.4249]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.153.1-2

Distro Version

Any

Other Software

No response

Repro Steps

Expected Behavior

Expected to see a normal boot into WSL2

Actual Behavior

wsl --install ubuntu Ubuntu is already installed. Launching Ubuntu... Installing, this may take a few minutes... WslRegisterDistribution failed with error: 0x80370109 Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.

Press any key to continue...

Diagnostic Logs

No response

github-actions[bot] commented 1 month ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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.

OneBlue commented 1 month ago

Thank you @wlvchandler. We're currently investigating this issue.

Can you share which processor model you have ? One of our theory is that this regression only hits on certain CPU's.

wlvchandler commented 1 month ago

I'll provide diagnostic logs later if possible - I had to recover quickly to keep working

And yeah certainly @OneBlue, it's an AMD Ryzen 9 7950X 16-Core. Processor(s): 1 Processor(s) Installed. [01]: AMD64 Family 25 Model 97 Stepping 2 AuthenticAMD ~4201 Mhz BIOS Version: American Megatrends Inc. 1636, 7/28/2023

Rurigok commented 1 month ago

@OneBlue I have a similar CPU and I can also confirm I'm experiencing the same issue noted here and in #12087 after the update: image

gab9281 commented 1 month ago

Thank you so much ! it's been 7h that im trying everything to make it work and uninstalling the update fixed it ! Thanks ! image

barnumbirr commented 1 month ago

Same issue here, uninstalling the update allows WSL to start again.

Screenshot 2024-09-28 045720

identityope commented 1 month ago

just got the same issue here after update windows image

pappleby commented 1 month ago

Same issue, same fix, similar processor. Think something else on my machine depends on wsl too, because if I waited too long after startup, things would stop working (could still move windows around, but taskbar broke, task manager stopped getting new data, even restarting hung). All of which was fixed once KB5043145 was uninstalled. {B42CA510-2895-42D3-9788-3E13C08C385B}

identityope commented 1 month ago

Yeah I've fixed the issue by uninstalling KB5043145 update

xoofx commented 1 month ago

Yeah I've fixed the issue by uninstalling KB5043145 update

I confirm that it is also fixing the issue with WSL by uninstalling this update.

abferm commented 1 month ago

Same issue with a Ryzen 7 7700X, was resolved by uninstalling update KB5043145

image

daryllmoya commented 1 month ago

image image Anyone here can share how to uninstall that update? I can't seem to do so, this is frustrating.

hphuc613 commented 1 month ago

Thank you @wlvchandler. We're currently investigating this issue.

Can you share which processor model you have ? One of our theory is that this regression only hits on certain CPU's.

Hi @OneBlue, I hope you fix this issue asap. This greatly affects my work. Try your best and thank you!

hphuc613 commented 1 month ago

image image Anyone here can share how to uninstall that update? I can't seem to do so, this is frustrating.

Below way work with me: Go to Setting > Recovery > Fix problems using Windows Update > Click Reinstall Now and Reinstall version of Windows update. After reinstall successfully You go to Setting > Windows Update > Update History > Uninstall Updates and Uninstall KB5043145

daryllmoya commented 1 month ago

image image Anyone here can share how to uninstall that update? I can't seem to do so, this is frustrating.

Below way work with me: Go to Setting > Recovery > Fix problems using Windows Update > Click Reinstall Now and Reinstall version of Windows update. After reinstall successfully You go to Setting > Windows Update > Update History > Uninstall Updates and Uninstall KB5043145

Thanks @hphuc613 , I did this also yesterday; it was the way that worked for me as well.

pmaxhogan commented 1 month ago

Thank you @wlvchandler. We're currently investigating this issue.

Can you share which processor model you have ? One of our theory is that this regression only hits on certain CPU's.

On a Ryzen 9 7900X here. Like the others, rolling back KB5043145 fixed it for me.

draco commented 1 month ago

I’m on 7600X, rolling back works (WSL can start now) but my file explorer keeps crashing. Anyone experiencing the same?

OneBlue commented 1 month ago

Sharing the instructions I posted https://github.com/microsoft/WSL/issues/12087. If you hit this issue, please:

For this to work, the dump must be captured while WSL is in that "hung" state (once the error is displayed, you need to start wsl.exe again)

pmaxhogan commented 1 month ago

Below way work with me: Go to Setting > Recovery > Fix problems using Windows Update > Click Reinstall Now and Reinstall version of Windows update. After reinstall successfully You go to Setting > Windows Update > Update History > Uninstall Updates and Uninstall KB5043145

@draco I experienced weird issues with Microsoft apps after rolling back, and doing the "fix problems using windows update" step after rolling back seemed to help a bit.

If you still have crashes with Microsoft programs after the windows update fix, you should try creating new a local user account on your computer to see if they still crash there. For me, my start menu would crash every time I tried to open it, but this did not appear in a new local (also administrator) account.

The only fix that worked for me was when I opened the registry editor as my normal account, poked around in HKEY_CURRENT_USER, and deleted registry entries that looked like they had to do with Microsoft explorer / shell / start menu customization. Had no idea what I was doing really but it seems to have fixed it now.

If your file explorer keeps crashing after the rollback and the 'fix problems' step doesn't help, I'm not sure I'd recommend deleting random registry stuff, but if you're desperate (and have backups) it's maybe worth trying.

hphuc613 commented 1 month ago

Below way work with me: Go to Setting > Recovery > Fix problems using Windows Update > Click Reinstall Now and Reinstall version of Windows update. After reinstall successfully You go to Setting > Windows Update > Update History > Uninstall Updates and Uninstall KB5043145

@draco I experienced weird issues with Microsoft apps after rolling back, and doing the "fix problems using windows update" step after rolling back seemed to help a bit.

If you still have crashes with Microsoft programs after the windows update fix, you should try creating new a local user account on your computer to see if they still crash there. For me, my start menu would crash every time I tried to open it, but this did not appear in a new local (also administrator) account.

The only fix that worked for me was when I opened the registry editor as my normal account, poked around in HKEY_CURRENT_USER, and deleted registry entries that looked like they had to do with Microsoft explorer / shell / start menu customization. Had no idea what I was doing really but it seems to have fixed it now.

If your file explorer keeps crashing after the rollback and the 'fix problems' step doesn't help, I'm not sure I'd recommend deleting random registry stuff, but if you're desperate (and have backups) it's maybe worth trying.

I also seen same situation with file exploder crashing. But my windows required update KB5043076, and after reboot the issue has been fixed. cc @draco

Wladastic commented 1 month ago

I have only similar issues, WSL does start but is restricted by Windows in some form I haven't figured out yet. There are couple Eventlogs indicating that some Socket connection is being reset randomly which breaks both IntelliJ and Docker, causing both to crash. Had this on my computer that runs on an Intel i7 155H as well as Ryzen 2700x and Intel i7-10750H, all of them have similar issues and should have completelly different update policies but received the update nevertheless.

gab9281 commented 1 month ago

Below way work with me: Go to Setting > Recovery > Fix problems using Windows Update > Click Reinstall Now and Reinstall version of Windows update. After reinstall successfully You go to Setting > Windows Update > Update History > Uninstall Updates and Uninstall KB5043145

@draco I experienced weird issues with Microsoft apps after rolling back, and doing the "fix problems using windows update" step after rolling back seemed to help a bit. If you still have crashes with Microsoft programs after the windows update fix, you should try creating new a local user account on your computer to see if they still crash there. For me, my start menu would crash every time I tried to open it, but this did not appear in a new local (also administrator) account. The only fix that worked for me was when I opened the registry editor as my normal account, poked around in HKEY_CURRENT_USER, and deleted registry entries that looked like they had to do with Microsoft explorer / shell / start menu customization. Had no idea what I was doing really but it seems to have fixed it now. If your file explorer keeps crashing after the rollback and the 'fix problems' step doesn't help, I'm not sure I'd recommend deleting random registry stuff, but if you're desperate (and have backups) it's maybe worth trying.

I also seen same situation with file exploder crashing. But my windows required update KB5043076, and after reboot the issue has been fixed. cc @draco

Same on my end : uninstalling the update caused my file-manager to crash + unable to install any programs. Reinstalling the update afterward didn't broke wsl afterward

michalzyka commented 1 month ago

Same here, fixed by uninstalling the update.

Bamgm14 commented 1 month ago

Same

datacompboy commented 1 month ago

fresh KB5044285 fixed the wsl issue. now both wsl and start menu is working again.

Bonfims commented 3 weeks ago

fresh KB5044285 fixed the wsl issue. now both wsl and start menu is working again.

This kb broke my WSL, like i dont have any distro installed

xunholy commented 3 weeks ago

fresh KB5044285 fixed the wsl issue. now both wsl and start menu is working again.

I'm on this version and WSL2 is still broken - however, menu and everything else appears operational