MagiskOnWSAOld Payloads and Installer
Overview
MagiskOnWSAOld/ is a legacy packaging area for older MagiskOnWSA/WSA builds. The covered paths are mostly vendored payloads and install-time resources rather than the active build logic: architecture-specific Android system overlays live under MagiskOnWSAOld/arm64/ and MagiskOnWSAOld/x64/, installer launch scripts live under MagiskOnWSAOld/installer/, and native/binary assets are staged under MagiskOnWSAOld/bin/, MagiskOnWSAOld/DLL/, MagiskOnWSAOld/libhoudini/, and MagiskOnWSAOld/linker/. This differs from the active tree in that these files are already materialized payloads for old-build packaging, including checked-in binaries, certificates, XML request templates, and per-architecture installer scripts; reviewers should treat this area as a compatibility/archive payload set, not as the current source of truth for generating modern packages.
The install entry point is the copied installer folder that contains MagiskOnWSAOld/installer/Run.bat plus one architecture subfolder. Run.bat only changes to its own directory, verifies that Install.ps1 exists beside it, and starts PowerShell with execution policy bypass. The actual install scripts are architecture copies: MagiskOnWSAOld/installer/x64/Install.ps1 and MagiskOnWSAOld/installer/arm64/Install.ps1. Both elevate to Administrator, enable sideloading through HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock, ensure the Windows VirtualMachinePlatform optional feature is enabled, optionally install UWP dependencies from an adjacent uwp/ folder based on AppxManifest.xml, remove or update an existing non-development WSA package, shut down WsaClient, and register the loose package with Add-AppxPackage -Register .\AppxManifest.xml. On success, they launch the WSA Settings app, Magisk, Play Store, and Android Settings through app URI/shell targets.
The arm64 installer has extra old-build integrity/resource handling that the x64 installer does not fully mirror. MagiskOnWSAOld/installer/arm64/Install.ps1 reads an adjacent filelist.txt and aborts when any listed payload is missing, then runs MakePri.ps1 when both MakePri.ps1 and makepri.exe are present. MagiskOnWSAOld/installer/arm64/MakePri.ps1 checks filelist-pri.txt, dumps existing PRI resources into priinfo/, recreates resources.pri using MagiskOnWSAOld/…/priconfig.xml, appends resource declarations from the other XML files under xml/ into AppxManifest.xml, and then deletes transient packaging inputs (pri/, xml/, makepri.exe, filelist-pri.txt, and itself). MagiskOnWSAOld/installer/x64/MakePri.ps1 performs the same PRI dump/rebuild/manifest append/cleanup flow but points to a Windows SDK makepri.exe at C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\makepri.exe rather than using a local executable, and the x64 Install.ps1 does not call it.
Path responsibilities:
MagiskOnWSAOld/installer/contains the Windows-side install launcher and per-architecture PowerShell installers. These scripts assume they are executed from a prepared package root containing AppxManifest.xml, optionaluwp/dependencies, and for arm64 the file-list/resource tooling inputs copied beside the scripts.MagiskOnWSAOld/arm64/andMagiskOnWSAOld/x64/contain architecture-specific old WSA system payload fragments. In the current covered listing, both providesystem/priv-app/VpnDialogs/VpnDialogs.apk;MagiskOnWSAOld/arm64/makepri.exeis the local resource-indexing executable used by the arm64 installer flow.MagiskOnWSAOld/bin/EROFS/contains the vendored EROFS tooling binariesmkfs.erofsandfuse.erofs, used as packaging/runtime filesystem tools by the old-build payload set.MagiskOnWSAOld/cacerts/contains 21 Android-style hashed certificate files (*.0) intended to be installed into the Android certificate store for the legacy system image payload.MagiskOnWSAOld/DLL/contains Windows DLL payloadsWsaPatch.dllandicu.dll. MagiskOnWSAOld/…/README.md identifiesWsaPatch.dllas coming from the WSAPatch release stream athttps://github.com/cinit/WSAPatch/releases.MagiskOnWSAOld/libhoudini/contains native-bridge assets for Houdini support.MagiskOnWSAOld/libhoudini/lib64/libhoudini.sois the top-level Houdini library, whileMagiskOnWSAOld/libhoudini/lib64/arm64/carries a large set of Android arm64 shared libraries and HAL/AIDL support libraries such aslibnativebridge.so,libnativeloader.so, graphics/media/audio stacks, and Android hardware interface libraries needed by that native-bridge payload.MagiskOnWSAOld/linker/contains a minimal Android dynamic linker/runtime support set:linker64,libc.so,libdl.so, andlibm.so.- MagiskOnWSAOld/…/priconfig.xml configures
makepriindexing withen-USas the default language and PRI/priinfo indexer support. MagiskOnWSAOld/…/GetCookie.xml, MagiskOnWSAOld/…/WUIDRequest.xml, and MagiskOnWSAOld/…/FE3FileUrl.xml are SOAP request templates for Microsoft Software Distribution/Windows Update endpoints, with{}placeholders for caller-supplied ticket/user, cookie, category, flight ring, update ID, and revision values. MagiskOnWSAOld/.gitattributesforces LF by default, CRLF for*.batand*.ps1, and marks executable/library/image payload formats (*.exe,*.dll,*.erofs,linker64,*.so) as binary withmerge=theirson all paths.MagiskOnWSAOld/LICENSEis the GNU AGPLv3 license text used by the legacy MagiskOnWSALocal scripts.
Coupling
- If
MagiskOnWSAOld/installer/arm64/Install.ps1is copied or changed, keep its package-root assumptions synchronized with the generated old-build package layout: it reads filelist.txt, expects AppxManifest.xml, optionally consumesuwp/, and only invokes resource merging when bothMakePri.ps1andmakepri.exeare adjacent to the installer. - If
MagiskOnWSAOld/installer/*/MakePri.ps1changes, verify MagiskOnWSAOld/…/priconfig.xml and the non-priconfig.xml XML files still match the manifest/resource merge flow. Both scripts append<Package><Resources><Resource>entries from every XML file underxml/except priconfig.xml; malformed or differently shaped XML will break AppxManifest.xml mutation rather than just resource generation. - If old-build architecture payloads under
MagiskOnWSAOld/arm64/orMagiskOnWSAOld/x64/are moved, update the file lists generated into the installer package as well. The arm64 installer aborts before registration when any path from filelist.txt is absent. - If
MagiskOnWSAOld/libhoudini/lib64/libhoudini.sois replaced, verify the companion libraries inMagiskOnWSAOld/libhoudini/lib64/arm64/and the linker/runtime files inMagiskOnWSAOld/linker/come from a compatible Android/WSA build. This legacy area vendors the native bridge and many of its Android runtime dependencies as a set; mixing versions can produce loader failures inside WSA. - If
MagiskOnWSAOld/.gitattributesis changed, check the covered binary payload directories before merging. The file marks.so,.dll,.exe, EROFS payloads, andlinker64as binary and usesmerge=theirs; losing that behavior can corrupt vendored binaries through line-ending conversion or accidental text merges.
Risks
MagiskOnWSAOld/installer/arm64/MakePri.ps1andMagiskOnWSAOld/installer/x64/MakePri.ps1delete their own resource inputs after a successful merge (xml/,pri/, filelist-pri.txt, and the script itself; arm64 also deletesmakepri.exe). If these scripts run in the repository checkout instead of a disposable package output directory, they can remove tracked legacy resources.MagiskOnWSAOld/installer/x64/MakePri.ps1hardcodes the Windows SDK tool pathC:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\makepri.exe. On a host without that exact SDK, resource regeneration fails and the package may retain stale or missing PRI resources.- MagiskOnWSAOld/…/GetCookie.xml, MagiskOnWSAOld/…/WUIDRequest.xml, and MagiskOnWSAOld/…/FE3FileUrl.xml embed Microsoft Software Distribution endpoint URLs and many protocol/device attributes with positional
{}placeholders. If callers substitute fields in the wrong order or Microsoft changes the FE3 protocol expectations, update discovery/download flows that depend on these templates will fail before packaging begins.