Introducing a new way to review your PRs.

Read the announcement

mustardchef / wsabuilds

Run Windows Subsystem For Android on your Windows 10 and Windows 11 PC using prebuilt binaries with Google Play Store (MindTheGapps) and/or Magisk or KernelSU (root solutions) built in.

View on GitHub

12 documents · Updated Nov 16, 2026

docs / magiskonwsa-bundled-payloads

MagiskOnWSA bundled payloads

Overview

This area covers vendored files that MagiskOnWSA copies into a WSA build rather than generating during the build. The payloads are organized by destination role:

  • MagiskOnWSA/bin/<arch>/ contains host-side build/runtime executables for each WSA package architecture. MagiskOnWSA/bin/x64/lspinit and MagiskOnWSA/bin/arm64/lspinit are injected into Tools/initrd.img by MagiskOnWSA/…/build.sh as /lspinit, then symlinked to /init so the Magisk boot path can wrap the original WSA init. MagiskOnWSA/bin/x64/makepri.exe and MagiskOnWSA/bin/arm64/makepri.exe are copied into the package root by MagiskOnWSA/…/build.sh; MagiskOnWSA/installer/MakePri.ps1 invokes makepri.exe to rebuild resources.pri, then removes the executable and updates filelist.txt so it is not retained after install-time resource merging.
  • MagiskOnWSA/libhoudini/ is the bundled Intel Houdini/native-bridge payload used to add ARM and ARM64 translation support. MagiskOnWSA/…/houdini_installer.sh expects to run from the repository root, locates ./libhoudini, expands and mounts system.vhdx and vendor.vhdx, and copies the payload into the mounted Android images.
  • MagiskOnWSA/libhoudini/bin/houdini and MagiskOnWSA/libhoudini/bin/houdini64 are installed into both /vendor/bin and /system/bin; the installer sets executable permissions and SELinux labels, then bind-mounts the vendor copies over the system paths through the init configuration.
  • MagiskOnWSA/libhoudini/lib/libhoudini.so and MagiskOnWSA/libhoudini/lib64/libhoudini.so are the main 32-bit and 64-bit native-bridge shared libraries. MagiskOnWSA/…/houdini_installer.sh copies them to /vendor/lib/libhoudini.so and /vendor/lib64/libhoudini.so with root ownership, mode 0644, and same_process_hal_file SELinux labels.
  • MagiskOnWSA/libhoudini/lib/arm/ and MagiskOnWSA/libhoudini/lib64/arm64/ are bulk ARM userspace dependency trees copied recursively into /vendor/lib/arm/ and /vendor/lib64/arm64/. The visible filenames show Android runtime, media, graphics, hardware-interface, libc/libc++, ART, binder, EGL/GLES, codec, and other system libraries needed by translated ARM processes. These should be reviewed as a matched vendor drop, not as generated build products.
  • MagiskOnWSA/libhoudini/etc/binfmt_misc/ contains text registration records for ARM and ARM64 ELF executable/dynamic formats. The records route 32-bit ARM entries to /system/bin/houdini and ARM64 entries to /system/bin/houdini64. MagiskOnWSA/libhoudini/etc/init/houdini.rc registers those records based on native-bridge properties; MagiskOnWSA/libhoudini/etc/init/init.windows.x64_64 includes WSA init content plus native-bridge registration and bind mounts.
  • MagiskOnWSA/.gitattributes marks .exe, .apk, and .so as binary while enforcing LF for shell/Python scripts and CRLF for Windows XML, batch, and PowerShell files. MagiskOnWSA/.gitignore excludes local build artifacts (download, output, python3-env, token). MagiskOnWSA/LICENSE is the AGPL-3.0 license text for the MagiskOnWSA project, not a per-binary provenance manifest.

Reviewers should treat changes under MagiskOnWSA/bin/** and MagiskOnWSA/libhoudini/** as binary/vendor asset routing changes unless the diff is limited to lightweight text files such as MagiskOnWSA/libhoudini/etc/binfmt_misc/*, MagiskOnWSA/libhoudini/etc/init/*, or MagiskOnWSA/…/houdini_installer.sh. Do not infer binary internals from committed .exe or .so contents; verify placement, architecture pairing, file names expected by scripts, licensing/provenance notes in the change, and whether the corresponding installer/build script still copies the asset to the expected destination.

Coupling

  • If files are added, removed, or renamed under MagiskOnWSA/bin/x64/ or MagiskOnWSA/bin/arm64/, also check MagiskOnWSA/…/build.sh: it hard-codes ../bin/$ARCH/lspinit for initrd injection and ../bin/$ARCH/makepri.exe for package assembly, so a payload rename breaks builds before any runtime validation.
  • If MagiskOnWSA/bin/*/makepri.exe changes, verify MagiskOnWSA/installer/MakePri.ps1 still invokes the same executable name from the package root and still removes it from filelist.txt; otherwise the installer may fail resource merging or leave a temporary tool in the final package.
  • If the Houdini library tree changes under MagiskOnWSA/libhoudini/lib/** or MagiskOnWSA/libhoudini/lib64/**, verify MagiskOnWSA/…/houdini_installer.sh still has enough image growth headroom and still copies both the top-level libhoudini.so files and the recursive ARM dependency directories into /vendor.
  • If MagiskOnWSA/libhoudini/bin/houdini, MagiskOnWSA/libhoudini/bin/houdini64, or MagiskOnWSA/libhoudini/etc/binfmt_misc/* changes, verify the interpreter paths remain synchronized: the binfmt records point at /system/bin/houdini and /system/bin/houdini64, while MagiskOnWSA/…/houdini_installer.sh installs those binaries to both /system/bin and /vendor/bin and then modifies init rules around bind mounts.
  • If MagiskOnWSA/libhoudini/etc/init/* changes, check it against MagiskOnWSA/…/houdini_installer.sh rather than only the static file: the installer searches the mounted vendor init directory for a Windows/x86 init file and injects extra exec registration lines after specific mount none /vendor/bin/houdini... patterns.
  • If new binary extensions are introduced under these payload directories, update MagiskOnWSA/.gitattributes so Git does not apply text EOL normalization to opaque vendor assets.

Risks

  • MagiskOnWSA/…/houdini_installer.sh sizes vendor.vhdx by adding a fixed 600 MiB before copying MagiskOnWSA/libhoudini/lib/arm/ and MagiskOnWSA/libhoudini/lib64/arm64/. A larger Houdini vendor drop can exhaust the mounted image and fail late during recursive copy or filesystem finalization.
  • MagiskOnWSA/…/houdini_installer.sh patches init files by matching literal mount lines for /vendor/bin/houdini and /vendor/bin/houdini64. If MagiskOnWSA/libhoudini/etc/init/init.windows.x64_64 or the WSA image's vendor init file changes those lines, binfmt registration may not be injected even though the binaries and libraries are copied.
  • Covered history shows repeated native-bridge churn (Add Fixes for ARM Translation Layer, Update (and fix) the Arm Translation Layer (Libhoudini)..., and Update Libhoudini to Google Play Games PC v26.8.237.1). Treat partial updates under MagiskOnWSA/libhoudini/** as high risk: mixing bin/, top-level libhoudini.so, etc/binfmt_misc, and ARM dependency trees from different drops can boot but fail when translated ARM processes load missing or mismatched shared libraries.