Table of Contents
In this article, we will look to solve Cannot enable nested VT-x/AMD-V without nested-paging error but before that let me give you a quick background on this error. Sometimes people working on VirtualBox tends to enable Nested VT-x/AMD-V but forget to disable Hyper-V feature in Windows due to which whenever they try to start the VirtualBox VM, they always end up in getting
Cannot enable nested VT-x/AMD-v without nested-paging and unrestricted guest execution error. So to solve this error we just need to disable Virtual Machine Platform feature from Windows Features. This can be accomplished by following steps mentioned in the below section.
[Solved]: Cannot enable nested VT-x/AMD-V without nested-paging
Step 1: Open CMD
You need to first Open the Windows Command line terminal. To do that, Search
CMD in the Windows bottom
Once it shows up, right click on it and then select
Run as Administrator. You will see a command line opened like below.
Step 2: Disable Hyper-V
On the command line window, you need to run
bcdedit /set hypervisorlaunchtype off command to disable Hyper-V in your System.
bcdedit is a command line tool for managing Boot Configuration Data(BCD) stores. You can check more about this on Microsoft official website.
C:\>bcdedit /set hypervisorlaunchtype off The operation completed successfully.
Step 3: Turn off Windows Feature
Then you need to turn off "Virtual Machine Platform" feature from Windows Features. For that you just need to uncheck this feature and then Click
Step 4: Reboot
After unchecking the Virtual Machine Platform feature, it will ask you to reboot the Windows to update the changes. Click on
restart now to reboot your Windows System. That's all you need to do. After finishing the steps, you can now try to start the VM again and this time it should start without any further error.
You can check all the options available with bcdedit command by running
bcdedit /? as shown below.
C:\>bcdedit /? BCDEDIT - Boot Configuration Data Store Editor The Bcdedit.exe command-line tool modifies the boot configuration data store. The boot configuration data store contains boot configuration parameters and controls how the operating system is booted. These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM entries (in Extensible Firmware Interface-based operating systems). You can use Bcdedit.exe to add, delete, edit, and append entries in the boot configuration data store. For detailed command and option information, type bcdedit.exe /? <command>. For example, to display detailed information about the /createstore command, type: bcdedit.exe /? /createstore For an alphabetical list of topics in this help file, run "bcdedit /? TOPICS". Commands that operate on a store ================================ /store Used to specify a BCD store other than the current system default. /createstore Creates a new and empty boot configuration data store. /export Exports the contents of the system store to a file. This file can be used later to restore the state of the system store. /import Restores the state of the system store using a backup file created with the /export command. /sysstore Sets the system store device (only affects EFI systems, does not persist across reboots, and is only used in cases where the system store device is ambiguous).