Mirrors/WSABuilds
2
0
Fork 0
mirror of https://github.com/MustardChef/WSABuilds.git synced 2024-12-27 03:41:48 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update FixVirtError.md with an upgraded guide.

Browse Source
This commit is contained in:
MCDeltaT 2023-08-22 14:07:50 +01:00 committed by GitHub
parent 69b7b4235b
commit 8ed5d681c0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 46 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
Fixes/FixVirtError.md
View File

@ -14,31 +14,69 @@
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 folder that you extracted and installed from) + Go to %LOCALAPPDATA%/Packages/ and delete the folder: MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe
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.
2. ***Go to "Turn Windows features on and off" and disable Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, and Windows Subsystem for Linux, then restart.****
2. ***Go to "Turn Windows features on and off" and if any of these features below are enabled, DISABLE THEM.***
3. ***Reenable these features and restart a second time.***
- Hyper-V
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Subsystem for Linux
4. ***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
 
5. ***In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends"***
3. ***Restart your PC***
 
4. ***Boot into your BIOS, and DISABLE Virtualization.***
- ***[Click here for a guide for Windows 11](https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-11-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1)***
- ***[Click here for a guide for Windows 10](https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-10-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1)***
 
5. ***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
 
6. ***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
6. ***Then in CMD (Run as Adminstrator), paste:***
 
7. ***Then in CMD (Run as Adminstrator), paste:***
```cmd
bcdedit /set hypervisorlaunchtype auto
```
7. ***Restart the Computer***
 
8. ***Reinstall WSA by running `Run.bat`***
8. ***ENABLE the features that you disabled in ``Step 1`` and restart a second time.***
 
9. ***Boot into your BIOS, and ENABLE Virtualization.***
- ***[Click here for a guide for Windows 11](https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-11-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1)***
- ***[Click here for a guide for Windows 10](https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-10-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1)***
 
10. ***Restart the Computer***
 
11. ***Reinstall WSA by running `Run.bat`***