From 49a67fcd22a38c57ddb7cce337456a90e8362743 Mon Sep 17 00:00:00 2001 From: MCDeltaT <68516357+MustardChef@users.noreply.github.com> Date: Thu, 19 Jan 2023 22:05:33 +0000 Subject: [PATCH] Update Custom Build requirements --- custombuilds/MagiskDelta/README.md | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/custombuilds/MagiskDelta/README.md b/custombuilds/MagiskDelta/README.md index 970459f..a4647ac 100644 --- a/custombuilds/MagiskDelta/README.md +++ b/custombuilds/MagiskDelta/README.md @@ -1,6 +1,6 @@ -# WSABuilds     -### MagiskOnWSA (Magisk Delta) (For Windows™ 10 and 11) -#### Windows Subsystem For Android™ (WSA) with Google Play Services and (or) Magisk Delta +# WSABuilds       +### MagiskOnWSA (Magisk Delta) (For Windows™ 10 and 11) [](https://discord.gg/2thee7zzHZ) +#### Windows Subsystem For Android™ (WSA) with Google Play Services and (or) Magisk Delta   @@ -15,6 +15,8 @@ | | [![win11down](https://img.shields.io/badge/Download%20Latest%20Build-Windows%2011-blue?style=for-the-badge&logo=windows11)](https://mega.nz/file/AzoSUDKT#PNuK7uQqvn8NmUDXcrHy6ii3TqLfK5207p89N637k14)| | | [![win10down](https://img.shields.io/badge/Download%20Latest%20Build-Windows%2010-blue?style=for-the-badge&logo=windows)](https://mega.nz/file/YrZjjbxS#BrnY3rOvcejPCh6w1m9seXVfOb1JtKXJlsvd_oBqjD0)| + +   | :exclamation: **Important:**   `⚠️DO NOT FORK⚠️` | @@ -33,10 +35,6 @@ > #### The same level of scrutiny should be applied with the WSA builds as with any other program that you download from the internet   -## Join The Discord! - -[![Discord](https://invidget.switchblade.xyz/2thee7zzHZ)](https://discord.gg/2thee7zzHZ) - ## Requirements | | | |-----------------------|-----------------------| @@ -45,6 +43,7 @@ |- Processor type: x64 or ARM64.| - Processor type: x64 or ARM64.| |- Virtual Machine Platform Enabled:
This optional setting is for virtualization and you can enable the setting from Control Panel/ Optional Features.| - Virtual Machine Platform Enabled:
This optional setting is for virtualization and you can enable the setting from Control Panel/ Optional Features.| |- Storage: Solid-state drive (SSD)
- Hard Disk Drive (HDD) (NOT RECOMMENDED).| - Storage: Solid-state drive (SSD)
- Hard Disk Drive (HDD) (NOT RECOMMENDED).| +| - Partition: NTFS
WSA can only be installed on a NTFS partition, not on an exFAT partition |- Partition: NTFS
WSA can only be installed on a NTFS partition, not on an exFAT partition| |- Windows™ 11: Build 22000.526 or higher.| - Windows™ 10: 22H2 10.0.19045.2311 or higher.
- May work on Windows™ 10 [21H2 10.0.19044.2311](https://user-images.githubusercontent.com/68516357/210234947-233d9207-6b54-4f70-99b3-2267bb542098.png)| |- The Computer must support virtualization and be enabled in BIOS/UEFI and Optional Features. [Guide](https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-11-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1)|- The Computer must support virtualization and be enabled in BIOS/UEFI and Optional Features. [Guide](https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-11-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1)| @@ -78,14 +77,13 @@ 9. Close File Explorer 10. **Enjoy** -### Notice: For the Windows 10 Builds +### Notice (Applicable for both Windows 10 and 11): -1. You can only install WSA on a NTFS partition, not on an exFAT partition. -2. You can NOT delete the WSA installation folder. +1. 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. +2. You need to register your WSA appx package before you can run WSA. For [WSABuilds](https://github.com/MustardChef/WSABuilds) and [MagiskOnWSALocal](https://github.com/LSPosed/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.