A WSA 5.15 x86_64 kernel with ReSukiSU root, SUSFS and a native x86_64 KPM runtime.
This project packages the kernel-side pieces needed to use ReSukiSU, SUSFS and KPM modules in Windows Subsystem for Android. The x86_64 KPM support is implemented in the paired ReSukiSU fork, which is pinned here as the KernelSU submodule.
| I want to... | Go to |
|---|---|
| Install the latest kernel | Installation guide |
| Build the kernel myself | Build guide |
| Fix a boot or Manager problem | FAQ and recovery steps |
| Check whether a KPM module is compatible | Module compatibility tracker |
| Understand the x86_64 KPM implementation | Technical overview |
| See what changed between releases | Changelog |
- the Microsoft WSA 5.15.104 x86_64 kernel base;
- ReSukiSU root integration with SUSFS support;
- a real x86_64 KPM loader, hook backend and native syscall wrappers;
- a paired Manager and
ksudpath for loading and controlling KPM modules; - CI checks for kernel builds, version metadata, release manifests and Manager packaging.
- Download the kernel and its release metadata from the latest release.
- Read the installation guide, including its prerequisites and rollback steps.
- Back up your current
Tools\kernel, verify the downloaded checksum, then replace the kernel and re-register WSA. - Boot WSA and verify the installation:
adb shell uname -a
adb shell su -c "ksud kpm version"
adb shell su -c "ksud kpm doctor --json"The kernel string should contain WSA-ReSukiSU. The KPM version should match the value recorded in the release manifest. The full installation guide explains the checks and recovery procedure step by step.
- The tested target is a WSA 2407-style package with the 5.15.104 x86_64 kernel. Other packages may use a different kernel layout or ABI.
- ARM64
.kpmfiles do not run on x86_64. Modules with available source may be portable using the ReSukiSU porting guide. - The Manager must contain a matching x86_64
libksud.so. A stock or ARM64-only Manager can report KPM as unsupported even when the kernel side is present. - Memory Integrity has worked in the recorded WSA baseline, but behavior can vary with Windows and WSA builds. See the FAQ if hooks fail or WSA does not start.
- Native x86_64 syscall wrappers are available. Compat syscall wrapping is not supported.
Consult the WSA compatibility matrix before using a different Windows or WSA version.
Clone this repository with submodules so the kernel and ReSukiSU revisions stay paired. The build guide covers the required toolchain, configuration fragments, build command and artifact verification.
Do not replace the KernelSU submodule with an arbitrary upstream revision. The WSA kernel and ReSukiSU fork share an x86_64 KPM ABI and are released together.
| Document | Contents |
|---|---|
| Install | Windows installation, verification and rollback |
| Build | Reproducible WSL2 and Linux builds |
| FAQ | Manager, HVCI, boot and KPM troubleshooting |
| KPM port | Loader, hooks, ABI and safety model |
| Module compatibility | Status and evidence for x86_64 KPM modules |
| Release gate | Required artifact, Manager and runtime evidence |
| Debug validation | KASAN, KCSAN, W^X and race-testing matrix |
The latest release page is the source of truth for the current tag, kernel checksum, ReSukiSU revision, loader marker and validation status. Keeping those values with the artifact avoids stale release data in this README.
Every release candidate is expected to pass the checks in docs/RELEASE_GATE.md. Historical changes and superseded releases remain in CHANGELOG.md.
Open an issue in the issue tracker and include:
adb shell uname -a
adb shell su -c "ksud kpm version"
adb shell su -c "ksud kpm doctor --json"Also attach the relevant dmesg section and note your Windows build, WSA package version and Memory Integrity state.
This work builds on the Microsoft WSA Linux kernel, KernelSU, ReSukiSU, SukiSU-related research, SUSFS and the Linux x86 text-patching infrastructure. The WSA x86_64 KPM port and packaging are maintained by Ognisty321.
The kernel is licensed under GPL-2.0. Included components retain their upstream licenses. See COPYING, LICENSES and KernelSU/LICENSE.