WSABuilds [BUG] "WSA_2407.40000.4.0_x64_Release-Nightly-with-magisk-29.0.29000.-stable-GApps-13.0.7" Can not install on Win10

Describe the bug

Unable to install version "WSA_2407.40000.4.0_x64_Release-Nightly-with-magisk-29.0.29000.-stable-GApps-13.0" even when running "run.bat" as administrator and turning off all antivirus software (including Windows defender) and then the error appears as shown in the figure.

---Poweshell--- PS C:\Windows\system32> cd "D:\Program Files\WSA\WSA_2407.40000.4.0_x64" PS D:\Program Files\WSA\WSA_2407.40000.4.0_x64> Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml Add-AppxPackage : Deployment failed with HRESULT: 0x80073CFD, Unable to meet the prerequisites for installation. Windows cannot install the package MicrosoftCorporationII.WindowsSubsystemForAndroid_2407.40000.4.0_x64__8wekyb3d8bbwe because it is incompatible with the device. This package requires the Windows.Desktop device family to be running OS version 10,0,22000,120 or higher. The device is currently running OS version 10,0,19045,5965. NOTE: For additional information, look for [ActivityId] 64262438-dc03-0006-ea93-276403dcdb01 in the Event Log or use th e command line Get-AppPackageLog -ActivityID 64262438-dc03-0006-ea93-276403dcdb01 At line:1 char:1

Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion ...

  + CategoryInfo          : NotSpecified: (D:\Program File...ppxManifest.xml:String) [Add-AppxPackage], Exception
  + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

PS D:\Program Files\WSA\WSA_2407.40000.4.0_x64> Get-AppPackageLog -ActivityID 64262438-dc03-0006-ea93-276403dcdb01

Time ID Message

2025/6/12 22:50:21 603 Started deployment Register operation on a package with main parameter AppxManif est.xml and Options ForceApplicationShutdownOption,DevelopmentModeOption,ForceUp dateFromAnyVersion and 0. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. 2025/6/12 22:50:21 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com /developer/appx/2015/build is inapplicable, it will be ignored during manifest p rocessing. 2025/6/12 22:50:21 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com /appx/manifest/desktop/windows10/8 is inapplicable, it will be ignored during ma nifest processing. 2025/6/12 22:50:21 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com /developer/appx/2015/build is inapplicable, it will be ignored during manifest p rocessing. 2025/6/12 22:50:21 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com /appx/manifest/desktop/windows10/8 is inapplicable, it will be ignored during ma nifest processing. 2025/6/12 22:50:21 10002 Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\d8468ef2 -9ac2-4485-8743-5964f2231451_S-1-5-21-495222449-4236745599-1306212695-1001_1.rsl c for Register Operation on Package MicrosoftCorporationII.WindowsSubsystemForAn droid_2407.40000.4.0_x64__8wekyb3d8bbwe. 2025/6/12 22:50:21 607 Deployment Register operation on package MicrosoftCorporationII.WindowsSubsystem ForAndroid_2407.40000.4.0_x64__8wekyb3d8bbwe has been de-queued and is running f or user SID S-1-5-21-495222449-4236745599-1306212695-1001. 2025/6/12 22:50:21 854 Successfully added the following uri(s) to be processed: D:\Program Files\WSA\W SA_2407.40000.4.0_x64\AppxManifest.xml. 2025/6/12 22:50:21 778 Windows cannot install package MicrosoftCorporationII.WindowsSubsystemForAndroid _2407.40000.4.0_x64__8wekyb3d8bbwe because this package is not compatible with t he device. The package requires OS version 10.0.22000.120 or higher on the Windo ws.Desktop device family. The device is currently running OS version 10.0.19045. 5965. 2025/6/12 22:50:21 605 The last successful state reached was BundleProcessed. Failure occurred before r eaching the next state Indexed. hr: 0x80073CFD 2025/6/12 22:50:21 401 Deployment Register operation with target volume C: on Package MicrosoftCorporat ionII.WindowsSubsystemForAndroid_2407.40000.4.0_x64__8wekyb3d8bbwe from: (AppxM anifest.xml) failed with error 0x80073CFD. See http://go.microsoft.com/fwlink/? LinkId=235160 for help diagnosing app deployment issues. 2025/6/12 22:50:21 404 AppX Deployment operation failed for package MicrosoftCorporationII.WindowsSubsy stemForAndroid_2407.40000.4.0_x64__8wekyb3d8bbwe with error 0x80073CFD. The spec ific error text for this failure is: Windows cannot install the package MicrosoftCorporationII.WindowsSubsyst emForAndroid_2407.40000.4.0_x64__8wekyb3d8bbwe because it is incompatible with the device. This package requires the Windows.Desktop device family to be running operating system version 10.0.22000.120 or later. The device is currently running operating system version 10.0.19045.5965.

PS D:\Program Files\WSA\WSA_2407.40000.4.0_x64> ---PowerShell---

The feedback seems to be saying that my system version is too old, but I have updated it to the latest version.

Steps to reproduce the issue

Run "run.bat" as an administrator,

Expected behaviour

Run "run.exe" and install normally

Downloaded Build Of WSA

https://github.com/MustardChef/WSABuilds/releases/download/Windows_11_2407.40000.4.0_LTS_7/WSA_2407.40000.4.0_x64_Release-Nightly-with-magisk-29.0.29000.-stable-GApps-13.0.7z

Windows build number

19045.5965

PC Specification

Operating System Name: Microsoft Windows 10 Pro Version: 10.0.19045 Build 19045 Other OS Description: Not Available OS Manufacturer: Microsoft Corporation System Name: DESKTOP-D3EQHBV System Manufacturer: HASEE Computer System Model: CV1S5 System Type: x64-based PC System SKU: Not Applicable Windows Directory: C:\Windows System Directory: C:\Windows\system32 Boot Device: \Device\HarddiskVolume1 Hardware Abstraction Layer (HAL): Version = "10.0.19041.5553" Processor & BIOS

Processor: 12th Gen Intel(R) Core(TM) i5-12450H, 2000 Mhz, 8 Core(s), 12 Logical Processor(s) BIOS Version/Date: INSYDE Corp. 1.07.15THZY3, 2022/8/19 SMBIOS Version: 3.3 Embedded Controller Version: 7.05 BIOS Mode: UEFI BaseBoard Manufacturer: Notebook BaseBoard Product: CV1S5 BaseBoard Version: Not Applicable Memory (RAM)

Installed Physical Memory (RAM): 16.0 GB Total Physical Memory: 15.7 GB Available Physical Memory: 8.50 GB Total Virtual Memory: 31.7 GB Available Virtual Memory: 23.8 GB Page File Space: 16.0 GB Page File: C:\pagefile.sys Security & Settings

Platform Role: Mobile Secure Boot State: Off PCR7 Configuration: Binding Not Possible Locale: United States Time Zone: Eastern Daylight Time User Name: DESKTOP-D3EQHBV\ErrorAnti Kernel DMA Protection: On Virtualization-based security: Running Virtualization-based security Required Security Properties: Virtualization-based security Available Security Properties: Base Virtualization, Secure DMA, UEFI, Memory Protections, SMM Security Mitigations 1.0, Mode-based execution control, APIC virtualization Virtualization-based security Services Configured: Hypervisor enforced Code Integrity Virtualization-based security Services Running: Hypervisor enforced Code Integrity Windows Defender Application Control policy: Enforced Windows Defender Application Control user mode policy: Off Device Encryption Support: Reasons for failed automatic device encryption: Hyper-V is enabled, which prevents it. A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Additional context

No response

Jun 13 '25 02:06 ErrorAnti

You are facing this issue because you have selected the wrong build.

Please get the correct WSA build from the Windows 10 release.

Jun 13 '25 08:06 MustardChef

@MustardChef

I'm facing the same issue, and I think you should take a look at it. Let me explain.

When you click on the "DOWNLOAD LATEST STABLE BUILDS WINDOWS 10 X64" button from https://github.com/MustardChef/WSABuilds#downloads, it redirects to: http://github.com/MustardChef/WSABuilds/releases/tag/Windows_10_2407.40000.4.0_v2

On that page, it says: "THIS NON-LTS RELEASE HAS NO MAGISK BUILDS. USE THE LTS_7 RELEASE, IF YOU REQUIRE MAGISK BUILDS."

Clicking on LTS_7 takes you to: https://github.com/MustardChef/WSABuilds/releases/tag/Windows_11_2407.40000.4.0_LTS_7

At first glance, that page appears to be for Windows 11. However, on that same page, there's a section titled: "Follow these steps to install on Windows 10." Link: https://github.com/MustardChef/WSABuilds/releases/tag/Windows_11_2407.40000.4.0_LTS_7#:~:text=Follow%20these%20steps%20to%20install%20on%20Windows%2010.

This implies that these builds can also be installed on Windows 10.

So, there's either a real issue here, or the instructions are wrong.

Aug 20 '25 09:08 MathewJake365