Stephen Sabatini stephensabatini

## README.md

      
              1 file
            
          
              14 forks
            
          
                20 comments
              
            
              99 stars
            
          
                4wk-
                / README.md
            
            
              Last active
              May 7, 2025 19:28
            
              
                Clean uninstall then reinstall of WSL on Windows 10, with systemD support
              
          
    Uninstall then reinstall WSL on Windows 10 (clean way)

Background

I've been using wsl (version 2) with genie mod for years without issue, but one day, Windows 10 finally catch up on wsl Windows 11 features and gives us a way to use systemD natively.
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 poping in.
Fixing it

A - Uninstall wsl and related stuff


In powershell (as admin)


## wordpress-roles.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              1 star
            
          
                stephensabatini
                / wordpress-roles.md
            
            
              Last active
              May 7, 2020 08:30
            
              
                These are the `wp_usermeta` fields associated with a specific user in WordPress to define their role/permissions in the database.
              
          
    WordPress Roles

Administrator

wp_capabilities a:1:{s:13:"administrator";b:1;}

wp_user_level 10
Editor

wp_capabilities a:1:{s:6:"editor";b:1;}

  
## fix-wsl2-dns-resolution.md

      
              1 file
            
          
              125 forks
            
          
                269 comments
              
            
              734 stars
            
          
                coltenkrauter
                / fix-wsl2-dns-resolution.md
            
            
              Last active
              May 12, 2025 10:36
            
              
                Fix DNS resolution in WSL2
              
          
    Permanent WSL DNS Fix (WSL 2.2.1+)

If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,