virtualbox.org

I have recently installed VirtualBox v5.0.6 r103037 onto my Windows 2008 server.
When I try and start any VM I get the following error
Failed to open a session for the virtual machine 3cx.

Not supported. (VERR_NOT_SUPPORTED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I thought I had installed SBS 2008, but the system tells me it is Windows Server Standard FE !!!

I would appreciate any ideas from anybody on whether it should run and if so why it isn't.
Many thanks
Alan Skinner

Let's clarify something: the topic title says that "VirtualBox 5.0.6 won't run", but in fact you installed it, and created a number of VMs, so something is running, right?

If you mean that you are having trouble with a specific VM, then you need to post a VM log file for it. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

Also, did you create this VM yourself, or did someone else give it to you?

Hi,

The actual VirtualBox program installs ok, but when I create any VM, it errors with the error specified earlier/above.
I have attached the log

Many thanks

Alan Skinner

Well, the error above includes a VM name, so I'd be rather surprised if you got that exact same message for every VM you create.

I note however that the log is for a different, Windows 7 VM.

I do see this in the log :-

VBox.log wrote: 00:00:16.551701 File system of 'C:\Users\Administrator\VirtualBox VMs\Telephones\Snapshots' (snapshots) is unknown
00:00:16.551712 File system of 'C:\Users\Administrator\VirtualBox VMs\Telephones\Telephones.vhd' is ntfs
00:00:16.553982 File system of 'C:\EDOT Data Area\ISO Files\en_windows_7_professional_n_with_sp1_x64_dvd_u_677207.iso' (DVD) is ntfs

So, you are running (and probably installed) VirtualBox as the wrong user, and this is most likely a host permissions issue. Specifically, it can't mount the "Telephones.vhd" file because it has no write access to the selected folder.

Uninstall VirtualBox from the Adminstrator user account, and reinstall as the correct user, but running the installer using "Run as administrator".

Tip: admin rights is not at all the same thing as being logged in as the user account called "Administrator". The latter account is intended to be used for maintenance activities on your PC. It so happens that that the "Administrator" user does usually have admin rights (hence the account name). But, that is a different user, so you generally don't install applications there that you need to access from your normal user account.

Incidentally, I would suggest that you scrap whatever VMs you have started so far (since you can't have got anywhere with them). And, when you come to recreate them use VDI format rather than VHD format. In general you should stick with defaults until you know more about the software.

Hi,

I have followed your instructions, and completely removed VirtualBox and rebooted and then installed by right clicking and installing as administrator.
I then ran the VirtualBox program again by right clicking icon and running as administrator.
I then created a VM called Telphones. When I click on start I get the following error
Not supported. (VERR_NOT_SUPPORTED).


Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have attached the log which I obtained by right clicking the VM and show log and then saving it.

Any idea why it wont run, and what I need to do to get it to run please ?????

Regards

Alan Skinner

VBox.log wrote: 00:00:32.546781 File system of 'C:\Users\Administrator\VirtualBox VMs\Telephones\Snapshots' (snapshots) is unknown
00:00:32.546793 File system of 'C:\Users\Administrator\VirtualBox VMs\Telephones\Telephones.vdi' is ntfs
00:00:32.549128 File system of 'C:\EDOT Data Area\ISO Files\en_windows_7_professional_n_with_sp1_x64_dvd_u_677207.iso' (DVD) is ntfs

No change. You are still accessing a VM in another users documents folder, specifically the documents folder of user "Administrator".

As I said before, you need to scrap the existing attempts to create a VM, and start again. There is no way VirtualBox is accessing files in another users folders unless you have been futzing with the default paths and haven't mentioned it.

Hi,

When I installed it, I accepted all the defaults.
I have just ran it normally, I deleted the VM, changed the default path for the VM VDI, created a new VM and still got the same error.
I have attached the new log file.

Regards

Alan Skinner

mpack wrote:

VBox.log wrote:You are still accessing a VM in another users documents folder, specifically the documents folder of user "Administrator".

Maybe his username is actually Administrator?

@Alan Skinner: Can you confirm or deny the above? What is the username that you log in with in your host?

It doesn't matter. If he runs all the time as the dummy user "Administrator" then I still walk away.

@mpack
Oh, surely that shouldn't matter. I mean, imagine installing (on bare metal) a Windows installation. With one user. Called Administrator. And you install VBox. Then what? VBox refuses to run? I don't buy it. In fact, I tried it in a VM and it worked flawlessly. On top of that I didn't see an Access denied type of error, what I saw so far was a VERR_NOT_SUPPORTED error.

@Alan Skinner
Could you post a zipped "VBoxHardening.log"? It should be located in the same place that your logs are stored. Plus I'm still waiting for confirmation/denial of whether you actually log in as a user called "Administrator".

Alan Skinner wrote:Hi,

I have followed your instructions, and completely removed VirtualBox and rebooted and then installed by right clicking and installing as administrator.
I then ran the VirtualBox program again by right clicking icon and running as administrator.
I then created a VM called Telphones. When I click on start I get the following error
Not supported. (VERR_NOT_SUPPORTED).


Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have attached the log which I obtained by right clicking the VM and show log and then saving it.

Any idea why it wont run, and what I need to do to get it to run please ?????

Regards

Alan Skinner

If you are getting the E-FAIL (0x80004005), the following information worked for me. Give it a try.

Go to "C:\Users\COMPUTER_NAME\VirtualBox VMs\LOCAL_VM_Name" (replacing computer_name and vm_name with your local variables) and make sure that each of your virtual machine directories have both of the following files.

vm_name.vbox-prev
vm_name.vbox-tmp

If both of these files do not exist in "C:\Users\COMPUTER_NAME\VirtualBox VMs\LOCAL_VM_Name", make a copy of vm_name.vbox-prev and name it vm_name.vbox-tmp.

Each of my local VM's were missing their corresponding .vbox-tmp file (Running Windows 10 64bit Enterprise, vbox v4.3.28).

*The source of my solution relates to a previous solution, but with some updates to the new directory which vbox stores .vbox=tmp files. Find the similar solution by searching for the post title "[SOLVED] E_FAIL (0x80004005) / runtime (-102) on Win7 Host"

Good luck!

Um... that is nonsense I'm afraid.

The xxx-tmp file is a temporary file which VirtualBox creates just before renaming the old .vbox file. VirtualBox does not look for a xxx-tmp file except during a save of a new .vbox file, which is does as the VM is shutting down - and in that case it creates a new file. VirtualBox never reads that file, nor does it require the presence of this file on startup.

The xxx-prev file is a backup of an old file, i.e. a rename of the previous .vbox file. VirtualBox doesn't ever use this file.

So how did you persuade yourself that this solved something? I can only guess that shutting down VirtualBox and restarting (or maybe restarting the host) was what actually did the trick.

@mpack What caused me to think this was the error? Perhaps I am basing my recommendation on repeatable results.

You are obviously experienced with troubleshooting vbox so I won't pretend to know more than you. However, having now removed my v-name.vbox-tmp from my "C:\Users\COMPUTER_NAME\VirtualBox VMs\LOCAL_VM_Name" my problem returns. Is it at all possible that Virtualbox is now looking at this file before starting up where previously they did not look at this file? Change does seem to be a constant.

Cheers.

This is the error I get without the corresponding *.vbox-tmp file. If I return .vbox-tmp, guest starts normally.

Failed to open a session for the virtual machine arch.

Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDDR0.r0: SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE (VERR_LDR_MISMATCH_NATIVE).

Failed to register ourselves as a PCI Bus (VERR_MODULE_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Sorry, I don't do speculation. Nothing you have said changes the facts I've outlined - i.e. VirtualBox does not read either of the files you mention.