Opened 7 years ago
Last modified 7 years ago
#16811 new defect
VBox 5.1.12.12440 immediately crashes - Win10 x64 Home
| Reported by: | Malchore | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.12 |
| Keywords: | crash | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
I cannot run VirtualBox 5.1.12.12440 x64. It crashes immediately when launced. I can't confirm, but I suspect the recent Windows 10 Creators update maybe did something to harm VBox, only becuase VBox worked fine until that Windows update was applied to my computer.
I've attached a crash dump of the most recent launch. I've also attached the most recent logs.
Attachments (3)
Change History (6)
by , 7 years ago
| Attachment: | VirtualBox.exe.14148.dmp added |
|---|
comment:1 by , 7 years ago
Windows 10 updates are notorious for breaking already installed applications. Plus, 5.1.12 is too old, you got to keep updating, mainly because you update the foundation that VirtualBox depends on (Win10).
- Uninstall VirtualBox. Your VMs are going to be untouched. Reboot.
- You may want to clean up your registry and/or filesystem at this point. CCleaner is a freeware utility that could help you. Mind the installation, it comes with "offers" from 3rd parties, known as "bundleware".
- Download the latest VirtualBox and the matching ExtPack. Store them in a common location, i.e. not on "Desktop", or "Documents", but to "Public/Downloads" for example.
- Locate the downloaded file in Windows Explorer. Right-click on the installer and select "Run-as-Administrator", even if you are the administrator. At the end of the installation, choose to "Start Oracle VM VirtualBox". Do not worry if your VMs do not show.
- If you're going to install the ExtPack, go to File » Preferences » Extensions. Click on the icon with the orange, down-pointing arrow on the right. Select the ExtPack from the previous steps.
- Quit VirtualBox. Re-start VirtualBox as you would normally, i.e. from the Desktop shortcut or the Start menu.
- Update the Guest Additions (GAs) in your guest(s), if the GAs are available for a specific guest.
May I suggest something? It's usually better and faster, if issues like this one (configuration, question) 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 most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
follow-up: 3 comment:2 by , 7 years ago
socratis, I appreciate your comment. I was hoping to avoid installing a newer version. I am running the lasest version of Vagrant, which makes use of VBox 5.1.12, and my vagrnt machines rely on guest additions 5.1.12. If I install a new version of VBox, my Vagrant VMs will fail to launch because I'll need an updated version of guest additions.
Oh, by the way, never ever, EVER install an application as Administrator (on Windows) unless abslutely nessesary. If you do, some processes could run as Administrator when you later launch them. That brings with it a whole lot of security headaces. VBox is pretty well bahaved when installed as a normal user. Besides, iirc I think the VBox installer alreadys asks you for elevation to Administrator anyways...so.
It's been a long time since I was a Windows programmer. A lot has changed. I was writting Windows apps when MFC 6.0 was around. That's when Windows 98 was fairly new.
comment:3 by , 7 years ago
Replying to Malchore:
I am running the lasest version of Vagrant, which makes use of VBox 5.1.12, and my vagrnt machines rely on guest additions 5.1.12
That's a detail that you forgot to mention. Vagrant uses VirtualBox, it is not VirtualBox. They do have their own support channels. In any event, as I said, if the basic API that VirtualBox relies upon changes, then VirtualBox has to adapt as well, don't you think? If you look at the Changelog, in every version there are fixes specific for Win10, because that puppy is a moving target, there's no way around it. Unfortunately for the developers and the end users alike. The only way is to disable the Win automatic updates, but that's user-controlled, and not optimal.
Oh, by the way, never ever, EVER install an application as Administrator (on Windows) unless abslutely nessesary. If you do, some processes could run as Administrator when you later launch them. That brings with it a whole lot of security headaces. VBox is pretty well bahaved when installed as a normal user. Besides, iirc I think the VBox installer alreadys asks you for elevation to Administrator anyways...so.
You couldn't be further from the truth I'm afraid. The proper way to do an application installation *IS* as administrator. Especially if there are kernel drivers installed, there is no other way. The Run-as-Administrator is an additional requirement starting mostly after Win8.1 where the UAC silently started rejecting drivers, even for the administrator account. Just for fun...
In fact in all of my hosts over the years there is always an administrator account, solely to install applications. Never run an application, only install and log out. I've never had an issue like you're describing in the last 25 year. Yes, before Win98 (or even 95), it was with NT 3.5 (a domain controller) and the rest of its younger siblings...
You are installing kernel drivers for Pete's sake, and you're worried about what an application could run as? VirtualBox does not run as administrator, and there are multiple ways to verify that.
CrashDump