[Solved] Unable to start VM
-
- Posts: 7
- Joined: 15. Aug 2019, 17:36
[Solved] Unable to start VM
Hey guys, I'm new to VBox and could really use some help.
System specs:
9900k
32gb ram
WIndows 10 Pro
Hyper-v - Feature turned off
Intel Virtualization Technology - Enabled
When I try to start the vm, the window pops up then throws an error. Please see the attached log and let me know if you have any questions or if I'm missing something.
One thing I noticed in the log, it states my processor is a 6700k when it's really a 9900k (I upgraded about a month ago and re-installed Windows)
Thanks in advance!
System specs:
9900k
32gb ram
WIndows 10 Pro
Hyper-v - Feature turned off
Intel Virtualization Technology - Enabled
When I try to start the vm, the window pops up then throws an error. Please see the attached log and let me know if you have any questions or if I'm missing something.
One thing I noticed in the log, it states my processor is a 6700k when it's really a 9900k (I upgraded about a month ago and re-installed Windows)
Thanks in advance!
- Attachments
-
- VBOX LOG.zip
- (9.39 KiB) Downloaded 73 times
Last edited by socratis on 15. Aug 2019, 19:16, edited 1 time in total.
Reason: Marked as [Solved].
Reason: Marked as [Solved].
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Unable to start VM
It is usually a god idea to tell us what the error was, too, especially if the error window has a Copy button which can be used to directly copy the error message for your post.
Good for posting a log, though! Th error was at the bottom:
VERR_NEM_VM_CREATE_FAILED
Tis a usual error from Windows 10
See I have a 64bit host, but can't install 64bit guests Carefully go through each command in the 2nd & 3rd posts.
Good for posting a log, though! Th error was at the bottom:
VERR_NEM_VM_CREATE_FAILED
Tis a usual error from Windows 10
See I have a 64bit host, but can't install 64bit guests Carefully go through each command in the 2nd & 3rd posts.
-
- Posts: 7
- Joined: 15. Aug 2019, 17:36
Re: Unable to start VM
Good call, here's the error that's posted:
I'll go ahead and go through the commands in the 2nd and 3rd posts you referenced.Failed to open a session for the virtual machine SJ_VM_01.
Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Unable to start VM
FWIW the magic bullet in most follow-ups on this error has been this command:
bcdedit /set hypervisorlaunchtype off
followed by a complete shut down and power off, unplugged for a few minutes.
bcdedit /set hypervisorlaunchtype off
followed by a complete shut down and power off, unplugged for a few minutes.
-
- Posts: 7
- Joined: 15. Aug 2019, 17:36
Re: Unable to start VM
1. Hyper-V is unchecked
2. Virtualization Based Security was set to Undefined - set it to Disabled
3. Core isolation is set to off
I tried starting the VM again (before running the bcdedit command as I would prefer not to restart at this moment unless completely necessary), it still failed to start but this time gave me different errors in the log.
2. Virtualization Based Security was set to Undefined - set it to Disabled
3. Core isolation is set to off
I tried starting the VM again (before running the bcdedit command as I would prefer not to restart at this moment unless completely necessary), it still failed to start but this time gave me different errors in the log.
Failed to open a session for the virtual machine SJ_VM_01.
Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-
- Posts: 7
- Joined: 15. Aug 2019, 17:36
Re: Unable to start VM
I'm not at home atm so a complete shutdown will be a little difficult, but how does a complete shutdown (including uplugging the system) help set the bcedit hypervisor launch type vs a standard shutdown or restart?
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Unable to start VM
It's unknown to me why, only that it works.
It has been known that changing the VT-x setting in the PC BIOS has required a full power-off and unplug. The bcdedit shutdown & unplug could just be another of those things.
You could always try the bcdedit command, but You would at least have to restart. As a possibility if you want to try without a full power off, try the full "reboot" shutdown command after the bcdedit command:
shutdown -r
This shutdown command bypasses Windows 10's partial shutdown fast-boot thing and causes a complete dump-all-Windows-caches shutdown a la XP/7. Maybe that would work.
It has been known that changing the VT-x setting in the PC BIOS has required a full power-off and unplug. The bcdedit shutdown & unplug could just be another of those things.
You could always try the bcdedit command, but You would at least have to restart. As a possibility if you want to try without a full power off, try the full "reboot" shutdown command after the bcdedit command:
shutdown -r
This shutdown command bypasses Windows 10's partial shutdown fast-boot thing and causes a complete dump-all-Windows-caches shutdown a la XP/7. Maybe that would work.
-
- Posts: 7
- Joined: 15. Aug 2019, 17:36
Re: Unable to start VM
Good news! After the bcdedit command and a restart the VM's are now working!! Thank you so much for the help!!
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Unable to start VM
Great! Glad to help. For my info, did you do the unplug, or the shutdown command, or just a simple restart?
-
- Posts: 7
- Joined: 15. Aug 2019, 17:36
Re: Unable to start VM
I did a simple restart because I missed your recommendation to run the reboot command from command prompt.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: [Solved] Unable to start VM
Interesting, Thanks for the info. Glad you're up and running.
-
- Posts: 7
- Joined: 15. Aug 2019, 17:36
Re: [Solved] Unable to start VM
No problem, thanks again for the help!