[BUG] No Package Identity

[Alicyl]

Describe the bug

I'm not really sure what's going on with my installation of Windows Subsystem for Android, but whenever I attempt to install it, I'm met with this error or a premature "All done!" at the end of it. I've fully uninstalled it, including checking %LOCALDATA%\Packages\ for MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe (which is never present), so I'm at a loss.

https://github.com/user-attachments/assets/adfb41fb-b0eb-4a20-a556-b82453a9e62f

Steps to reproduce the issue

1. Download Windows Subsystem for Android.
2. Extract to C:\WSA.
3. Open Run.bat.
4. Accept the prompt for administrative privileges needed for Install.ps1.
5. Wait for the terminal to finish the process of installation.
6. Be met with the problems shown in the clip/screenshots.

Expected behaviour

I expected the installation to proceed as it has before and for Windows Subsystem for Android to open itself at the end of it.

Downloaded Build Of WSA

1. 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-NoGApps-NoAmazon.7z
2. https://github.com/MustardChef/WSABuilds/releases/download/Windows_11_2407.40000.4.0_v2/WSA_2407.40000.4.0_x64_Release-Nightly-NoGApps-RemovedAmazon.7z

Windows build number

26200.7171

PC Specification

• OS Name Microsoft Windows 11 Pro
• Version 10.0.26200 Build 26200
• Other OS Description Not Available
• OS Manufacturer Microsoft Corporation
• System Name
• System Manufacturer Gigabyte Technology Co., Ltd.
• System Model X870 EAGLE WIFI7
• System Type x64-based PC
• System SKU Default string
• Processor AMD Ryzen 7 9800X3D 8-Core Processor, 4700 Mhz, 8 Core(s), 16 Logical Processor(s)
• BIOS Version/Date American Megatrends International, LLC. F5a, 5/5/2025
• SMBIOS Version 3.7
• Embedded Controller Version 255.255
• BIOS Mode UEFI
• BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
• BaseBoard Product X870 EAGLE WIFI7
• BaseBoard Version x.x
• Platform Role Desktop
• Secure Boot State Off
• PCR7 Configuration Elevation Required to View
• Windows Directory C:\WINDOWS
• System Directory C:\WINDOWS\system32
• Boot Device \Device\HarddiskVolume1
• Locale United States
• Hardware Abstraction Layer Version = "10.0.26100.1"
• User Name
• Time Zone
• Installed Physical Memory (RAM) 32.0 GB
• Total Physical Memory 31.1 GB
• Available Physical Memory 9.05 GB
• Total Virtual Memory 70.2 GB
• Available Virtual Memory 35.6 GB
• Page File Space 39.1 GB
• Page File C:\pagefile.sys
• Kernel DMA Protection Off
• Virtualization-based security Running
• Virtualization-based security Required Security Properties Base Virtualization Support, Secure Boot, DMA Protection
• Virtualization-based security Available Security Properties Base Virtualization Support, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control
• Virtualization-based security Services Configured Credential Guard, Hypervisor enforced Code Integrity, Secure Launch, Kernel-mode Hardware-enforced Stack Protection
• Virtualization-based security Services Running Hypervisor enforced Code Integrity, Kernel-mode Hardware-enforced Stack Protection
• App Control for Business policy Enforced
• App Control for Business user mode policy Off
• Automatic Device Encryption Support Elevation Required to View
• A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Additional context

When I installed it for the first time, it seemed to have properly gone through the entire process with a prompt at the end to press y to restart for enabling Virtualization, all of which are already enabled—SVM Mode (AMD), Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform.

I mistakenly pressed t instead of y and tried running Run.bat again. Ever since that accident, I've been encountering the issues shown in the clip/screenshots. Maybe accidentally pressing a different key or rerunning Run.bat was what broke the installation?

Also, I posted this within the Discord server, but I was not sure if I should have done so here first—if this is a bug or not.