Opened 9 years ago
Closed 9 years ago
#14454 closed defect (fixed)
CAN launch guest in Windows 10, but only after the forth attempt
| Reported by: | ryanflores | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.2 |
| Keywords: | windows 10 vagrant four attempts virtualbox 5.0.1 5.0.2 | Cc: | |
| Guest type: | all | Host type: | Windows |
Description
Unlike some others, I'm able to launch guests in Windows 10, but only after four attempts immediately after logging into the host. Whenever I reboot my system, no guest will launch. I can see in the GUI for a split second Starting below the VM, but the status will change back to either Powered Off or Aborted. I've been able to consistently reproduce this issue with versions 5.0.1 and 5.0.2.
In addition, this happens when I either try to start a VM I manually created directly in the GUI, or when I try to start a VM created using Vagrant. It doesn't matter which approach I use, it always takes exactly four attempts before the guest VM will run.
I also described this behavior in the following Vagrant ticket: https://github.com/mitchellh/vagrant/issues/6068
Attachments (1)
Change History (4)
by , 9 years ago
| Attachment: | VBoxSVC.log added |
|---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Hi frank. Yes, 5.0.4 did the trick. I didn't have to do anything special. I just upgraded (installed over) 5.0.2, updated the extension pack, then manually launched my VMs. All fired up on a single attempt.
After, I rebooted then tested using Vagrant. I was able to destroy and start all my existing Vagrant boxes without issues.
Thanks to the VB team for fixing this! Awesome job and many kudos to you all!
Any change with VBox 5.0.4?