Mirrors/WSABuilds
2
0
Fork 0
mirror of https://github.com/MustardChef/WSABuilds.git synced 2025-12-18 19:16:04 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
WSA-next
WSABuilds/Documentation/Fix Guides/Post-Install Issues/FixVirtError.md
MustardChef 71d91259eb Improve readability.
2025-07-18 12:52:16 +00:00

3.6 KiB
Raw Permalink Blame History

WSABuilds      

   

Issues:

   

Solution:

You may encounter this problem, even if Virtualization is enabled on your PC (in the BIOS) and shows up as enabled in Task Manager (as seen below) and Virtual Machine Platform + Windows Hypervisor Platform is Enabled. The solution is:

 

  1. Remove WSA: Right clicking on "Windows Subsystem for Android™ Settings" and pressing uninstall + Deleting the extracted WSA (MagiskOnWSA/WSABuilds) folder that you extracted and installed from.

 

  1. Go to "Turn Windows features on and off" and if any of these features below are enabled, DISABLE THEM.

    • Hyper-V
    • Virtual Machine Platform
    • Windows Hypervisor Platform
    • Windows Subsystem for Linux

 

  1. Restart your PC

 

  1. Boot into your BIOS, and DISABLE Virtualization.

 

  1. Ensure that you have Control Flow Guard enabled in Windows Security > Apps & browser control > Exploit protection. This is a known issue that can prevent WSA from starting

 

  1. In registry editor (regedit):

    • Go to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends

      • Change the value of Start from 3 to 0

    • Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard

      • Change the value of EnableVirtualizationBasedSecurity to 0
      • If you do not have a EnableVirtualizationBasedSecurity DWORD value, create one by right-clicking and adding a new DWORD (32 bit) value. Rename it to EnableVirtualizationBasedSecurity and make sure that the value is set to 0.

 

  1. Then in CMD (Run as Adminstrator), paste:
bcdedit /set hypervisorlaunchtype auto

 

  1. ENABLE the features that you disabled in Step 2 and restart a second time.

 

  1. Boot into your BIOS, and ENABLE Virtualization.

 

  1. Restart the Computer

 

  1. Reinstall WSA by running Run.bat

 



For AtlasOS Users:

  • If the steps above still do not fix your issue, go to the AtlasOS configuration folder and run the Enable Hyper-V and VBS CMD file. Then restart your PC and try running WSA again

    Image description


Have futher question or need help?

Join the Discord if you have any other questions or need help!

Reference in New Issue View Git Blame Copy Permalink