Skip to content

Windows Subsystem For Android: Windows 10 for x64 Processors (Windows_10_WSA_2301.40000.4.0_x64)

Compare
Choose a tag to compare
@MustardChef MustardChef released this 10 Feb 06:10
· 723 commits to master since this release
Windows_10_2301.40000.4.0
d5c73cb
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

win10downcpre

Warning

Read the guide in full before installing. Ensure you meet the full requirements for an installation on Windows 10.

Note

If you're updating WSA, merge the folders and replace the files for all items when asked

Follow the same steps as with installing WSA on Windows 11.

Contains Magisk and MindTheGAPPS

Note :
If you have the official WSA installed, you must completely uninstall it to use MagiskOnWSA

  1. Extract the zip file
  2. Delete the zip file
  3. Move the newly extracted folder to a suitable location (Documents folder is a good choice), as you will need to keep the folder on your PC to use MagiskOnWSA
  4. Open the WSA folder and double-click Run.bat

Notice:

  1. As stated in the Requirements, You can only install WSA on a NTFS partition, not on an exFAT partition.
  2. You can NOT delete the WSA installation folder.
    What Add-AppxPackage -Register .\AppxManifest.xml does is to register an appx package with some existing unpackaged files,
    so you need to keep them as long as you want to use WSA.
    Check https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps for more details.
  3. You need to register your WSA appx package before you can run WSA.
    For WSABuilds and MagiskOnWSALocal users, you need to run Run.bat in the extracted dir.
    If the script fails, you can take the following steps for diagnosis (admin privilege required):
    1. Open a PowerShell window and change working directory to your WSA directory.
    2. Run Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml in PowerShell.
      This should fail with an ActivityID, which is a UUID required for the next step.
    3. Run Get-AppPackageLog -ActivityID <UUID> in PowerShell.
      This should print the log of the failed operation.
    4. Check the log for the reason of failure and fix it.

Problems You May Encounter:

  • When using WSA 2209.40000.26.0, I was able to run applications in WSA, but I was not able to connect to WSA ADB after enabling Developer Mode, since netstat shows that no process is listening on port 58526. After I upgraded to WSA 2210.40000.7.0, I was able to connect to WSA ADB.
  • The WSA settings window does not hava a draggable title, but you can move the WSA window if you hold the cursor left near the "minimize" button, or press Alt+Space, then click "Move" in the context menu. cinit/WSAPatch#1 cinit/WSAPatch#2
  • If your WSA crashes(or suddenly disappears) when starting up, try to upgrade your Windows to Windows 10 22H2 10.0.19045.2311. (Someone has reported that WSA failed to start on 22H2 19045.2251, but worked after upgrading to 19045.2311.)

Changelog

  • Microsoft Official Changelog
  • Added Windows 10 Support (Credit: WSAPatch)
  • Update from WSA v2211.40000.11.0 ---> WSA v2301.40000.4.0
  • WSA Android Version: Android 13
  • MindTheGapps 13.0 x86_64
  • Magisk Canary v831a398b
  • Amazon Appstore Removed

Credits:

https://github.com/LSPosed/MagiskOnWSALocal
https://github.com/cinit/WSAPatch

Assets 3