Boot Repair Loop after enabling either "windows sandbox/virtualisation in bios (SVM)"

Question

Hello,

I recently upgraded to win 11 pro to use windows sandbox and hyper-v.

In "turn windows features on or off", upon enabling windows sandbox I was prompted to restart where the laptop got stuck in a boot loop. To fix I tried:

-updating the bios

-reinstalling windows

-running windows update

-getting the right drivers

In the end I managed to enable the windows sandbox by:
Enabling virtualisation in bios > enabling windows sandbox > reboot > disabling virtualisation in bios > reboot > windows sandbox will install successfully during boot.

Windows sandbox is now available in start but wont run (virtualisation not being enabled in bios)

Enabling virtualisation in bios will still cause a boot loop.

Following a help thread for a fix to a "boot repair loop", I booted into safe mode and ran "BCDedit /set hypervisorlaunchtype Off" in cmd. This fixed the bootloop when virtualisation is enabled. But running windows sandbox then gives the problem: No hypervisor was found. Please enable hypervisor support. (0xc0351000).

Laptop Brand: ASUS

Model: FX505DU
Bios version: 316
Windows Specs:
Edition Windows 11 Pro

Version 22H2

Installed on ‎25/‎02/‎2023

OS build 22621.1265

Experience Windows Feature Experience Pack 1000.22638.1000.0

*Note: My only virtualisation in the bios is an option called SVM which is what I am referring to whenever I mentioned virtualisation.

I am really hoping that I can get virtualisation and sandbox to run together without having to deactivated one or the other as it defeats the purpose. Hopefully a solution can be found to this.

Please let me know if there is more information needed. Many thanks in advance for any help or advise.

Kind regards.

Answer 1

Hello there,

Have you tried updating your BIOS and drivers?

From your description I can see that you have even made an clean install of the device which should have sorted the issue of this is related with operating system of the device .

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer--

Answer 2

Hello there,

Have you tried updating your BIOS and drivers?

From your description I can see that you have even made an clean install of the device which should have sorted the issue of this is related with operating system of the device .

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer--

Answer 3

Hey Hector Klemens

I had the same issue as you had and i feel like i have got an fix to this issue you are facing .

There is an option below the SVM option in the BIOS. It is set to 512M to default
I got the fix by changing it to Auto

That Worked for me and Hyper-V and Windows Sandbox works for me like a charm

Revert back incase you face any issue after the above fix