Git Product home page Git Product logo

Comments (19)

DesktopECHO avatar DesktopECHO commented on May 25, 2024 2

Hi, looks like the bug is fixed in recent Beta/Insider builds and should show up in the next generally-available release. See here for details.

I've seen this BSOD corrupt a running WSL instance, that's likely why you can't RDP into the Linux instance anymore.
Uninstall+reinstall will clear this up, but may be best to run an Insider build for now, or wait for MS to release a fix.

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

Are you running Windows 11 inside a VMware VM?

from kwsl.

mfreeman-xtivia avatar mfreeman-xtivia commented on May 25, 2024

No. Straight Windows 11 directly on the platform

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

Hi Mike, is your BSOD always citing MEMORY_MANAGEMENT? Won't be able to dig into this for a while as I'm away, but I will look into it when I return home. What build of Windows 11 are you running?
Thanks,
D.

from kwsl.

mfreeman-xtivia avatar mfreeman-xtivia commented on May 25, 2024

Yes, the BSOD reason is always "MEMORY_MANGEMENT"....

Windows 11 Pro, 22000.132.
Windows Feature Experience Pack 1000.22000.132.0

Thanks for looking at this....

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

One other thing you can try while I'm away...
Just as an experiment, does Kali-xRDP work? It's based off the Kali image from the Windows Store as opposed to Ubuntu.

And one more question -- Did you happen to notice if kWSL or xWSL worked on earlier Windows 11 builds?

from kwsl.

mfreeman-xtivia avatar mfreeman-xtivia commented on May 25, 2024

I will give it a shot and let you know

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

Hi Mike,

Can you retry on Windows 11, 22000.168 and let me know if this issue persists?
I'm not seeing a BSOD anymore, not sure if it's extremely good luck on my end or if the issue has been resolved.

Thanks,
D.

from kwsl.

mfreeman-xtivia avatar mfreeman-xtivia commented on May 25, 2024

No joy unfortunately.

Confirmed that matches my current version of Windows 11, installed kWSL, and then was able to drive around the UI for about a half dozen operations before i encountered the same BSOD (MEMORY_MANAGEMENT)

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

Thanks for checking… I got a crash as well today. Still working on it!

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

Hi Mike, are you seeing this in build 10.0.22000.194 as well?

from kwsl.

mfreeman-xtivia avatar mfreeman-xtivia commented on May 25, 2024

I have not tried it lately. Should I?

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

The STOP error was very intermittent for me, seems to happen to you more often. But ok so far on my Windows 11 VM...

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

One more thing... try turning off audio redirection.

from kwsl.

mfreeman-xtivia avatar mfreeman-xtivia commented on May 25, 2024

what setting controls " try turning off audio redirection"?

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

Just from the remote desktop client:
image

from kwsl.

crramirez avatar crramirez commented on May 25, 2024

Hello,

It happened to me with a completely unrelated action. I was doing a dnf update in Oracle Linux in WSL1. I think that WSL1 has some problems with Windows 11

Regards

from kwsl.

letivalo avatar letivalo commented on May 25, 2024

Hi,

I'm having this same issue, but it doesn't look like this thread's been mentioned in a while.

Laptop blue screened citing MEMORY_MANAGEMENT a few moments after connecting to the remote desktop following me running the script for the first time. I've got the latest windows 11 updates, I have WSL2 set as my default, and a reasonably beefy laptop.

Any further discoveries regarding this issue? Also on a side note, I haven't been able to connect to the remote desktop since my laptop crashed, I've just been stuck trying to run the scheduled task command and connecting to it using the icon created on my desktop. Can't connect, even though I'd been able to connect to it and bluescreen after first running the script. Am I missing something?

from kwsl.

DesktopECHO avatar DesktopECHO commented on May 25, 2024

This issue has been resolved in the Windows 11 22H2 Release Preview.

from kwsl.

Related Issues (19)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.