VAGRANT UP Issue When Restart

MongoDB University M103: Basic Cluster Administration
#1

When I restart the vagrant using --vagrant up-- command, go the below error
I use Windows 10

G:\university\m103\m103-vagrant-env>vagrant status
Current machine states:

mongod-m103 poweroff (virtualbox)

The VM is powered off. To restart the VM, simply run vagrant up

G:\university\m103\m103-vagrant-env>vagrant up
Bringing machine ‘mongod-m103’ up with ‘virtualbox’ provider…
==> mongod-m103: Clearing any previously set forwarded ports…
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [“modifyvm”, “d3152147-a005-4844-8865-5391ff93b3a5”, “–natpf1”, “delete”, “ssh”]

Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: “LockMachine(a->session, LockType_Write)” at line 525 of file VBoxManageModifyVM.cpp

#2

Here is one solution from past discussions:

Well, I figure out how to resolve it. This error is in VM Virtual manager during restart. You must turn on the virtualization(vt-x) in BIOS. Watch out below two minutes video how to enable the virtualization. https://www.youtube.com/watch?v=7U-e3Ui-NhU

Let me know if it works!

Kanika