virtualbox.org

My OS: Windows 10 x64.

1) I've installed vanila VirtualBox
2) I've chosen "create linux" - "ubuntu x32"
3) I've chosen "create new virtual disc" - "VDI' - "static" - "2 GB" , pressed "ok"
4) Virtual Box closed
5) I've opened VirtualBox again but it crashes instantly with no error, just saying "virtualbox manager stopped working". - I see that there is a new virtual mashine on the list.

After deleting this ubuntu and reinstalling VirtualBox it works fine until i do the same and get the same problem.

First time i solved this problem by ejecting sd-card. Now it has no effect.

I can upload log, but it seems not to update after this error.

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Perryg wrote:Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

I did it. The new log after crash. Absolutely fresh.

Is this the only log file? Did you follow my instructions? There should be a file called "vbox.log"

To me it seems that your VM selector window crashes, is that correct?

I had a look at the VBoxSVC.log file. It contains a very strange path in Loading settings file "C:\Users\RedNeck\OneDrive\Документы\1\1.vbox" with version "1.15-windows" This migt be the reason for the crash. Could you try to change the path for VMs to C:\Users\RedNeck/VMs (open the Global Settings / General / Path for VMs) and then try to create a VM again? Does it still crash?

Weird. I see this. Different editors?

Not to butt in but OneDrive is Microsoft's Cloud Service and I can't imagine a guest in its folder would work well.

Perryg wrote:Is this the only log file? Did you follow my instructions? There should be a file called "vbox.log"

VB crashes instantly on launch.

Frank Mehnert wrote:To me it seems that your VM selector window crashes, is that correct?
I had a look at the VBoxSVC.log file. It contains a very strange path in Loading settings file "C:\Users\RedNeck\OneDrive\Документы\1\1.vbox" with version "1.15-windows" This migt be the reason for the crash. Could you try to change the path for VMs to C:\Users\RedNeck/VMs (open the Global Settings / General / Path for VMs) and then try to create a VM again? Does it still crash?

Did all what you say. VM is now on C:// . But it still crashes in the same way. New log is attached.
But why do i see my flash card F: in the log? Maybe the problem is somehow connected with it?

PROBLEM SOLVED
Just download the previous stable version Virtual Box v4.2
virtualbox. org/wiki/Download_Old_Builds_4_2

Sticking forever to the 4.2 branch is hardly a solution.

mpack wrote:Sticking forever to the 4.2 branch is hardly a solution.

my other win 10 computer works fine. Quite good solution for rare case

ununnamed wrote:Quite good solution for rare case

True, but if we let this without digging any further, someone else is going to "trigger" this "rare case" and we won't have a clue what to do.

Oh, and BTW, keep in mind that 4.2.x was released way before Windows 10 was available, so you might bump into incompatibilities in the future.