Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • It's not clear what you're trying to do here, or even what's happening. I know Kitty as a terminal emulator, so I'm guessing your trying to open a terminal between the host and the emulated Windows environment. I can't tell which direction you're trying to connect, or the nature of your problem. You need to clarify what you expect to happen here. Ideally, if you know what they mean, you should also use more specific terms to explain what's actually happening now, such as those here: kali.org/docs/wsl/win-kex. Commented Aug 21, 2023 at 4:32
  • 1
    Oh, @BryKKan, I'm so sorry. I was trying to use kali on wsl and trying to make it work like a native system (Cant' install kali as native system becasue need windows for engineering tools and have a little storage space). So the "issue " here was that kitty was oppening in other window and not "inside" the win-kex instance. I totaly forgot about the other win-kex modes . Launch a winkex instance on enhanced session mode solved the "issue". Thank you so much. I'll make an edit and add the answer that you gave me. Commented Aug 21, 2023 at 5:46
  • Great! You did great with the answer too! Just don't forget to edit a bit of the details from your comment back into the original question. Makes it a little more useful to others coming by later if they don't have to read the comments first to understand whether they're having the same problem. Commented Aug 21, 2023 at 6:50