[BUG] Asking to activate virtualization even though it is activated

[ghost]

Describe the bug

My virtualization is enabled, but it still won't start and the following error appears: "Verify that virtualization is enabled in the BIOS and that the Virtual Machine Platform is enabled for the computer."

Steps to reproduce the issue

When I try to start WSA, the error appears: "Could not start Windows Subsystem for Android. Verify that virtualization is enabled in the BIOS and that the Virtual Machine Platform is enabled for the computer."

Expected behaviour

Solve this error

Downloaded Build Of WSA

WSA_2407.40000.4.0_x64_Release-Nightly-GApps-13.0-NoAmazon_Windows_10.7z

Windows build number

22H2 (SO 19045.5608)

PC Specification

i5-10400f 2.90GHz 16 GB RAM RX 550 4GB

Additional context

No response

[antonny107846]

Same issue here

[YAROSSAINT]

Same. AMD-V enabled and VMware working just fine. Virtual Machine Platform and Hyper-V enabled too.

Win 10 Pro x64

ASUS Crosshire VI Extreme, latest bios. / Ryzen 5950

[ikxrean]

For any users with AMD CPUs, I have come across a fix that worked for AMD users and myself included.

In Regedit, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard.

Once you are in DeviceGuard, set EnableVirtualizationBasedSecurity to 0.

If you do not have EnableVirtualizationBasedSecurity in DeviceGuard, add a DWORD (32 bit) value and rename the value to EnableVirtualizationBasedSecurity. Ensure the value is set to 0.

Restart, then reopen Run.bat and let it reinstall. The virtualization error should no longer exist and you should be able to access WSA fully.

[ikxrean]

Also, OP states he has an i5, so I'm not sure how it would work as I have never had this issue running this WSA build on any computers running Intel. Regardless, I'd like to see how the potential fix might fare for this issue across the board.

[nolan70gaming]

For any users with AMD CPUs, I have come across a fix that worked for AMD users and myself included.

In Regedit, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard.

Once you are in DeviceGuard, set EnableVirtualizationBasedSecurity to 0.

If you do not have EnableVirtualizationBasedSecurity in DeviceGuard, add a DWORD (32 bit) value and rename the value to EnableVirtualizationBasedSecurity. Ensure the value is set to 0.

Restart, then reopen Run.bat and let it reinstall. The virtualization error should no longer exist and you should be able to access WSA fully.

Not working for me sadly, virtualisation activated in bios. I see it activated in my task manager.

I have a ryzen 7 9800x3D

EDIT: open cmd as admin and put:

bcdedit /set hypervisorlaunchtype auto

Restart computer then its work for me !!

[YAROSSAINT]

For any users with AMD CPUs, I have come across a fix that worked for AMD users and myself included. In Regedit, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard. Once you are in DeviceGuard, set EnableVirtualizationBasedSecurity to 0. If you do not have EnableVirtualizationBasedSecurity in DeviceGuard, add a DWORD (32 bit) value and rename the value to EnableVirtualizationBasedSecurity. Ensure the value is set to 0. Restart, then reopen Run.bat and let it reinstall. The virtualization error should no longer exist and you should be able to access WSA fully.

Not working for me sadly, virtualisation activated in bios. I see it activated in my task manager.

I have a ryzen 7 9800x3D

EDIT: open cmd as admin and put:

bcdedit /set hypervisorlaunchtype auto

Restart computer then its work for me !!

Thank you! Problem solved for me too.