Opened 6 years ago
Closed 6 years ago
#17910 closed defect (invalid)
after windows 10 upgrade no longer able to start my VMs
| Reported by: | ves | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.16 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
I have a windows 10 machine with several VMs (Ubuntu) installed which were running fine. After Win10 upgrade to 1709 OS Build 16299.551 i cannot access my VMs. Error i get is
VT-x is not available (VERR_VMX_NO_VMX). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
My Machine is a Lenovo ThinkPad T470, I checked the BIOS and virtualization is enabled (never made a change to this setting in BIOS)
I tried all the suggestion in this forum https://forums.virtualbox.org/viewtopic.php?f=6&t=84618 but no luck. I reinstalled VB and I tried any other suggestion by googling on this error and still no luck.
Change History (2)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The bugtracker is not a place for discussions, the forums are. It's usually better and faster, if issues get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".