Make WSA (Windows Subsystem for Android) Run on Windows 10

• ExplorerPatcher

  649 21,339 9.2 C

  This project aims to enhance the working environment on Windows

Well, there are features missing.

Given how every monitor in existence is wide , it's super odd you can't drag the taskbar to the side, it's bottom only. https://www.windowscentral.com/microsoft-explains-why-you-ca...

The Win 11 context menu is just irritating, it displays a lot of unnecessary things and the "real" context menu is hidden under "show more options"

You can see much more at https://github.com/valinet/ExplorerPatcher/ -- and this project fixes them, too.

• WSAPatch

  11 1,442 1.0 C++

  Make WSA(Windows Subsystem for Android) run on Windows 10.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• wsl-vpnkit

  18 2,065 2.5 Shell

  Provides network connectivity to WSL 2 when blocked by VPN

If it works at all like WSL, you might want to look at wsl-vpnkit.

https://github.com/sakai135/wsl-vpnkit

It's not a proxy, but would give some idea how to shim into the middle.

• WSA-Magisk

  17 226 7.3 Shell

  A custom Windows Subsystem for Android with GApps, Magisk and KernelSU

  

I was reading the linked repo in step 2 <https://github.com/LSPosed/MagiskOnWSALocal#magisk-on-wsa-wi...> and saw this message, which seems like utter nonsense:

> For fork developers: Please don't build using GitHub Actions, as GitHub will count your forked GitHub Actions usage against this upstream repository, which may cause this upstream repository gets disabled by GitHub staff like MagiskOnWSA because of numerous forks building GitHub Actions, and counting the forks' Action usage against this upstream repository.

is that even remotely true?

If there's any "disabled by GitHub staff" going on, it's likely due to DMCA nonsense, not due to forks having their GitHub Actions billed against the upstream repo. Related to that, I'm surprised to see the submitted repo distribute icu.dll and winhttp.dll, versus telling interested parties to extract them out of the Win11 ISO. I bet Microsoft won't bother striking the repo over to random dlls but why roll the dice?

Suggest a related project