Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
View 4wk-'s full-sized avatar
🍉
🍉

Block or report 4wk-

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. Clean uninstall then reinstall of WS... Clean uninstall then reinstall of WSL on Windows 10, with systemD support
    1
    # Uninstall then reinstall WSL on Windows 10 (clean way)
    2
    ## Background
    3
    I've been using `wsl` (version 2) with [`genie` mod](https://gist.github.com/djfdyuruiry/6720faa3f9fc59bfdf6284ee1f41f950) for years without issue, but one day, Windows 10 [finally catch up](https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/) on `wsl` Windows **11** features and gives us a way to use `systemD` natively. 
    4
    
                  
    5
    I wanted to use the new "right way" to enable `systemD` on **Windows Subsystem for Linux** (without `genie`), and I also had a (probably related) infinite [Windows RemoteApp error](https://user-images.githubusercontent.com/1439550/210227714-d15c1eac-9138-48c1-a03f-157fd90fec6c.png) poping in.
Morty Proxy This is a proxified and sanitized view of the page, visit original site.