MustardChef / WSABuilds

Run Windows Subsystem For Android on your Windows 10 and Windows 11 PC using prebuilt binaries with Google Play Store (MindTheGapps) and/or Magisk or KernelSU (root solutions) built in.
GNU Affero General Public License v3.0
8.28k stars 1.39k forks source link

[BUG] WSA does not open after shutdown android windows subsystem #119

Closed iStiler closed 7 months ago

iStiler commented 1 year ago

Describe the bug | 描述一下这个错误

I installed it normally, I managed to install the apps then I turned it off and on again to be able to use the apps it doesn't open anymore it just keeps loading and then closes. it does not open any application

image

Steps to reproduce the issue | 重现该问题的步骤

1 - open play store or any other android app 2 - Starting the Windows subsystem for Android... it just keeps loading.. 3 - closes without opening the APP

Expected behaviour | 预期的行为

it was supposed to open the apps normally

Downloaded Build Of WSA | 已下载的WSA版本

WSA_2305.40000.6.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon_Windows_10

Windows build number | Windows构建号

19045.3086

PC Specification | 个人电脑规格

Operating System Name Microsoft Windows 10 Home Single Language Version 10.0.19045 Build 19045 Other Operating System Description Not available Operating System Manufacturer Microsoft Corporation ACERNITRO system name Acer system manufacturer Nitro System Model AN517-51 X64-based PC system type System SKU 0000000000000000 Intel(R) Core(TM) i5-9300H Processor CPU @ 2.40GHz, 2400Mhz, 4 Core(s), 8 Logic Processor(s) BIOS version/date Insyde Corp. V1.33, 11/17/2020 Version of SMBIOS 3.0 Embedded Controller Version 1.29 UEFI BIOS Mode Manufacturer of BaseBoard CFL BaseBoard Product Superb_CFS BaseBoard Version V1.33 Mobile Platform Role Secure Boot State Enabled PCR7 Configuration Evaluation Required for Display Windows Folder C:\WINDOWS C:\WINDOWS\system32 system folder Boot Device \Device\HarddiskVolume3 Location Brazil Hardware Abstraction Layer Version="10.0.19041.2728" Username ACERNITRO\mathe Time zone Official time in Brazil Physical Memory (RAM) Installed 16.0 GB Total physical memory 15.8 GB Available physical memory 7.76 GB Total virtual memory 27.8 GB Available virtual memory 9.29 GB Paging file space 12.0 GB Pagefile C:\pagefile.sys Kernel DMA Protection Disabled Virtualization Based Security Running Mandatory security properties of virtualization-based security Virtualization-based Security Available Security Properties Baseline Virtualization Support, Secure Boot, DMA Protection, SMM Security Mitigations 1.0, Baseline Execution Control Mode Configured virtualization-based security services Virtualization based security services running Device Encryption Support Trial Required for Display A hypervisor has been detected. Resources needed by Hyper-V will not be displayed.

Additional context | 额外的背景

No response

MustardChef commented 1 year ago

@iStiler This is a tricky thing to fix.

First method you can try to fix this:

Note You can change it back to 3, if it makes no difference

bcdedit /set hypervisorlaunchtype auto

Second method you can try to fix this (if the first recommended steps did not work):

Third method you can try to fix this (if the second recommended steps did not work):

Uninstall WSA and reinstall it without any backup and restore of data (Clean Install WSA)

iStiler commented 1 year ago

@iStiler This is a tricky thing to fix.

First method you can try to fix this:

  • Go to "Turn Windows features on and off"
  • Disable the following, if enabled:
    1. Hyper-V,
    2. Virtual Machine Platform,
    3. Windows Hypervisor Platform,
    4. Windows Subsystem for Linux,
  • Restart your PC
  • In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends" Change the value of “Start” from “3” to “0”

Note You can change it back to 3, if it makes no difference

  • Then in CMD (Run as Adminstrator), paste:
bcdedit /set hypervisorlaunchtype auto
  • Reenable the features that you disabled in "Turn Windows features on and off"
  • Restart your PC

Second method you can try to fix this (if the first recommended steps did not work):

Third method you can try to fix this (if the second recommended steps did not work):

Uninstall WSA and reinstall it without any backup and restore of data (Clean Install WSA)

I uninstalled the whole program, and installed it again now, the play store does not appear, only windows subsystem for android

MustardChef commented 1 year ago

@iStiler This is a tricky thing to fix.

First method you can try to fix this:

  • Go to "Turn Windows features on and off"
  • Disable the following, if enabled:

    1. Hyper-V,
    2. Virtual Machine Platform,
    3. Windows Hypervisor Platform,
    4. Windows Subsystem for Linux,
  • Restart your PC
  • In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends" Change the value of “Start” from “3” to “0”

Note You can change it back to 3, if it makes no difference

  • Then in CMD (Run as Adminstrator), paste:
bcdedit /set hypervisorlaunchtype auto
  • Reenable the features that you disabled in "Turn Windows features on and off"
  • Restart your PC

Second method you can try to fix this (if the first recommended steps did not work):

Third method you can try to fix this (if the second recommended steps did not work):

Uninstall WSA and reinstall it without any backup and restore of data (Clean Install WSA)

I uninstalled the whole program, and installed it again now, the play store does not appear, only windows subsystem for android

Open the Windows Subsystem for Android Settings and click on the button on the Files tab and tell me if the Android Files app opens.

iStiler commented 1 year ago

Isso é uma coisa complicada de consertar.

Primeiro método que você pode tentar corrigir isso:

  • Vá para "Ativar e desativar recursos do Windows"
  • Desative o seguinte, se habilitado:

    1. Hyper-V,
    2. Plataforma de Máquina Virtual,
    3. Plataforma de hipervisor do Windows,
    4. Subsistema Windows para Linux,
  • Reinicie o PC
  • No editor do Registro (regedit), vá para "\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends" Altere o valor de "Start" de "3" para "0"

Observação Você pode alterá-lo de volta para 3, se não fizer diferença

  • Em seguida, no CMD (Run as Adminstrator), cole:
bcdedit /set hypervisorlaunchtype auto
  • Reative os recursos que você desabilitou em "Ativar e desativar recursos do Windows"
  • Reinicie o PC

Segundo método você pode tentar corrigir isso (se as primeiras etapas recomendadas não funcionaram):

Terceiro método que você pode tentar corrigir isso (se as segundas etapas recomendadas não funcionaram):

Desinstale o WSA e reinstale-o sem qualquer backup e restauração de dados (Clean Install WSA)

Eu desinstalei todo o programa, e instalei novamente agora, a loja de jogos não aparece, apenas o subsistema do Windows para Android

Abra o Subsistema do Windows para Configurações do Android e clique no botão na guia Arquivos e me diga se o aplicativo Arquivos do Android é aberto.

It just stays on that screen loading and then closes alone. image

MustardChef commented 1 year ago

@iStiler Have you tried Method 1

iStiler commented 1 year ago

Você já tentou o método 1

yes, and it's the same thing.

TouchstoneTheDev commented 1 year ago

image image win11 hard drive taking too much time

MustardChef commented 1 year ago

image image win11 hard drive taking too much time

@tanmay-veer Please open a seperate issue!

GumbyXGames commented 1 year ago

I've run into this same issue with build Windows_11_WSA_2306.40000.4.0_x64). I just used WSA last night without an issue, but when I tried to access the Play Store I had to log in. When I tried to update or install any apps, they stayed in Pending. I tried to manually Turn Off WSA but it spins the activity "circle" indefinitely. Nothing comes up when trying to open an installed app.

When following Method 1, I noticed I was missing Hyper-V and the other three features were disabled. I manually installed Hyper-V via command line then enabled all the features and rebooted. I then followed all steps in Method 1. Now I get a window that the app is starting, but that window closed and the app doesn't open. When I tried to shutdown WSA, I get the infinitly spinning activity circle. Going to attempt a clean install of WSA.

OS: Windows 11 Home Build: 22H2 (22621.1992)

Update: Clean install is working. I was using the build with Magisk, so I'm trying the build with MindTheGapps and Amazon App Store

TouchstoneTheDev commented 1 year ago

Means i should install hperv then install with Magisk so i might not get infini buffer @GumbyXGames

amaruelle commented 1 year ago

Hi! I'm having a similiar issue on Windows 11 22H2, 22621.2070 (Insider Preview Dev Channel). The apps were perfectly working for the first 20 minutes after installing, I've used the Stable WSA Build with GApps and no Amazon Store. There are no errors at all, but the apps just don't start anymore (loading finalizes and then nothing). My full PC specs:

OS Name Microsoft Windows 11 Pro
Version 10.0.22621 Build 22621
Other OS Description    Not Available
OS Manufacturer Microsoft Corporation
System Name STUDIO
System Manufacturer Gigabyte Technology Co., Ltd.
System Model    Z490I AORUS ULTRA
System Type x64-based PC
System SKU  Default string
Processor   Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz, 2808 Mhz, 10 Core(s), 20 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. F5c, 7/9/2020
SMBIOS Version  3.2
Embedded Controller Version 255.255
BIOS Mode   UEFI
BaseBoard Manufacturer  Gigabyte Technology Co., Ltd.
BaseBoard Product   Z490I AORUS ULTRA
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.22621.1413"
User Name   studio\bulka
Time Zone   Russia TZ 2 Standard Time
Installed Physical Memory (RAM) 64.0 GB
Total Physical Memory   63.9 GB
Available Physical Memory   51.4 GB
Total Virtual Memory    73.4 GB
Available Virtual Memory    56.4 GB
Page File Space 9.50 GB
Page File   C:\pagefile.sys
Kernel DMA Protection   Off
Virtualization-based security   Running
Virtualization-based security Required Security Properties  
Virtualization-based security Available Security Properties Base Virtualization Support, DMA Protection, UEFI Code Readonly, 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   Audit
Device Encryption Support   Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.    

Is this error related to my system version?

SZRXAI commented 1 year ago

I would like a review on this problem again, thanks. @MustardChef I tried possible ways, I think the problem might be these modifications(which are obviously useful), the main error is caused by the programs that listen to the same port as WSA, in my case is System with PID 4 (it should not be Turned Off), I already used "adb" and the service is ON but the virtual platform won't boot up, I can't even understand Where is the problem coming from.

hkwpc commented 1 year ago

I seem to have encountered the same problem. The Android subsystem can be installed and started normally. After a day or two of normal use, the above-mentioned problem will appear inexplicably. The subsystem or program is loading, and then flashes back and cannot be started.

MustardChef commented 1 year ago

@hkwpc

Can you try out the steps in this guide, to see if they fix your issue.