Virtualbox and running virtual machines have worked previously. I cannot remember what changed for it to not work anymore.

Whenever I try to launch or create a new virtual machine this error pops up:

AMD-V is not available (VERR_SVM_NO_SVM). AMD-V is not available (VERR_SVM_NO_SVM).

I have tried making new 64-bit ubuntu and 32-bit ubuntu. My existing VM also get that error. Same error always. I have tried reinstall virtualbox but that didn't help.


  • Ryzen 7 1700x with Windows 10.
  • SVM is enabled in the bios settings.
  • I have Hyper-v turned off as other answers have pointed out.

Hyper-V is turned off

I am aware of possible duplicates but those answers was not satisfactory:


Try :

  • To ensure Hyper-V is totally disabled, enter in elevated Command Prompt:

    bcdedit /set hypervisorlaunchtype off
  • Run gpedit.msc and go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security, and set to Disabled. Do the same for CredentialGuard.

  • Check Windows Defender Security Center > Device Security > Core Isolation Details, that it is turned off.

|improve this answer|||||
  • I'm getting an error when creating a 32-bit ubuntu but I don't think they are releated. Also using a prebuilt vm works as it should. Thanks for your answer. I think specifically the gpedit part did the trick. I previously had done bcedit. Also I did a reboot, but don't know of it's effect. – Starlord Nov 12 '18 at 13:10
  • Please, please, please @Microsoft to fix this! – Arnis Juraga Feb 22 at 15:45
  • I think I had to also restart the pc, at least – FantomX1 Mar 2 at 19:30

This problem happened on my Windows 10 build 1903 after I enabled Windows Sandbox in Windows features. It was solved after I uninstalled it.

|improve this answer|||||

For me it helped it looks like to disable and enable virtualization in bios. UEFI bios type I have, -> Advanced -> cpu features -> SVM item (this is named virtualization in UEFI BIOS on ADM cpus other cpus and bioses its VTX).

I also used above bcdedit /set hypervisorlaunchtype off but it didn't seem to help.

|improve this answer|||||
  • I can't help myself but comment, why I got minus point?, I did this comment tbh not for you, but for me guys, as it helped me, so I presume it works. I used the above command, but not even restart helped, I might try to reproduce. So disabling and enabling, might be sometimes the case to clear some cache I assume. – FantomX1 Mar 2 at 19:29

Not the answer you're looking for? Browse other questions tagged or ask your own question.