virtualbox.org

I am having problems with my VM.
I can't open it and the worst part is that when I try to launch it, the disk usage of my windows goes from 0% to 100%! I have tried numerous times and so far is the same outcome.

With that in mind, I don't know how to provide the minimum information needed for the assistance. How can I provide the above information without launching the VB?

The important thing is to get my files/documents. Is there any way?
Any suggestions??

Same problem for me, unfortunately.

I do not know what happened since everything was working fine before and now—all of the sudden—it won't even start.

I originally had Windows 8 on my PC, but I since upgraded to Windows 10. This was about 6-months ago when it became available for everyone.

I've installed a wide arrangement of apps, though none conflicting to my eye. That being said however, it's not as if I've installed two-hundred programs on my system either.

In any case, my situation is that after a while of using Windows 10, I decided to install Virtual Box in the hopes of being able to then install and run Linux Mint as a guest.

So, I did just that. Everything was working fine and I made my little tweaks here and there (icons, firewall, etc.), but as of right now, I can't check any of the settings I had set prior due to the fact that Virtual Box won't even open. It starts up for like a second, and a second later, it closes. However, this is only viewable via the Task Manager on Windows. Nothing shows up when I double click on the executable. This problem just happened recently and I've had Virtual Box for about 3-4 months now (I believe).

Additional Info:
OS Name Microsoft Windows 10 Pro
Version 10.0.10586 Build 10586
OS Manufacturer Microsoft Corporation
System Manufacturer Gigabyte Technology Co., Ltd.
System Model To be filled by O.E.M.
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor AMD FX(tm)-6300 Six-Core Processor, 3500 Mhz, 3 Core(s), 6 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. F2, 7/15/2013
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Hardware Abstraction Layer Version = "10.0.10586.0"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.96 GB
Available Physical Memory 5.58 GB
Total Virtual Memory 9.84 GB
Available Virtual Memory 6.32 GB
Page File Space 1.88 GB
Page File C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Guest OS(s) installed: Linux Mint 17.2 [Cinnamon][ x64 ](however, since I've been upgrading it, I'm not sure what it is now. That's what I installed however)

Since there's more than one log file to my recollection, I'm not sure which one it is that would be of use here.

I may be wrong in my assertion here, but I believe the issue might have arisen after the latest big update Windows released. It wasn't like the previous smaller ones as this update sort of reminded me of when I was upgrading to Windows 10 from Windows 8.1. It took a while, let's just say that.

Please let me know what I can do to help you folks understand what it is that's gone wrong. I'd be more than happy to provide more information.

Thank you for reading.

Regards,

T.R.G.

I think our problems are a bit different from each other.

I can launch the VB but after 5 minutes of waiting to open, the disk usage goes to 100% and the VB is not usable. I have waited long enough to be sure that it doesn't work after some amount of time. It's always the same outcome: launch, wait, unusable and kill.

Haven't found anything until now to help me.

Regards
JfF

@JustForFun
Most probably it's your Windows client or the Windows update. Let it sit overnight and see if it gets fixed. This is most probably not a VirtualBox problem but a Windows problem.