Skip to Main Content
Forums

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

The virtual machine has terminated unexpectedly during startup with exit code 1 (0x1)

1035002Dec 11 2014 — edited Jan 13 2020

Hello All,

I came up with the error below, when I am trying to start a virtual machine from my VirtualBox. It was working fine till yesterday, and all of a sudden it's throwing this error. The only change I can think of, is of some automatic windows update which might have changed/updated the registry entries.

VirtualBox Version: 4.3.20

Host:     Win7 64 bit

Guest:   OracleLinux 64 bit

Failed to open a session for the virtual machine DEVM.

The virtual machine 'DEVM' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'E:\VM\DEVM\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)

Component: Machine

Interface: IMachine {480cf695-2d8d-4256-9c8c-cce0000fa123}

Please suggest on how to move forward.

Thanks,

Moore
This post has been answered by 1035002 on Dec 12 2014
Jump to Answer

Comments

Dude!

If you think it is a registry entry, you might want to check and delete the following entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

"C:\Program Files\Oracle\VirtualBox\VirtualBox.exe"="DISABLEUSERCALLBACKEXCEPTION"

(source: https://forums.virtualbox.org/viewtopic.php?f=6&t=62615)

2812973

I am getting the same error and problems as Craig.  It was working fine until yesterday's Windows Update.  The registry entry that Dude! suggested doesn't even exist on my machine.

Edit:  I should mention that, like Craig mentioned below, the "Layer" tree is missing.  I even did a entire registry search for "DISABLEUSERCALLBACKEXCEPTION" and found nothing.

1035002

Thanks for the reply.

The folder "Layer" in missing from my system's registry i.e after [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags]

OS Version: Windows 7 Professional.

Thanks!

Dude!

When something happens that probably affects many users, such a as bad Windows update, checking the most recent reports in the Virtualbox product forum might be the best address:

https://forums.virtualbox.org/viewtopic.php?f=6&t=65083

https://forums.virtualbox.org/viewtopic.php?f=6&t=65056

2812973

Thanks.  Uninstalling that particular update file did the trick.

EdStevens 
2812973 wrote:




I am getting the same error and problems as Craig.  It was working fine until yesterday's Windows Update. 

When it comes to Windows, nothing surprises me.  At my last job the network/desktop unit was completely separate from the database/application unit.  We (database/application) knew that every Wednesday would be spent chasing new errors brought about by Micros*** "Patch (bug) Tuesday"

1035002

Thanks Dude for the links.

Looks like now we have a solution from Microsoft for the bug.

Install KB3024777 to fix an issue with KB3004394 on Windows 7 and Windows Server 2008 R2

Thanks!

1035002
Answer

I have overcome the issue.

1) Installed the latest update from Microsoft.http://support.microsoft.com/kb/3024777

2) Did System Reboot.

3) Uninstalled the Oracle VM VirtualBox.

4) Installed it again after a second Reboot.

Thanks Again for all your comments.

Marked as Answer by 1035002 · Dec 12 2014
2 people found this helpful
3125471

I am getting this error on Windows 10 Enterprise edition. What is the solution for that?

3394347

Not sure but I found this looking for an error ALMOST identical to this that turned out to be a conflict between VirtualBox and MS  Hyper-V. If you have Hyper-V installed, it will not let VirtualBox access the "VT-x" function of the CPU.

Check:

https://www.virtualbox.org/ticket/12350

Hope this helps.

Jim

3316778

hi everyone how's going on. i have this problema, how can i do

Fallo al abrir una sesión para la máquina virtual Oracle DB Developer VM.

The virtual machine 'Oracle DB Developer VM' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
ae461b91-eac4-46ba-a0dc-b8dfe928eb2a

I had the same issue after I installed the latest Windows 10 update, so I uninstalled VirtualBox and replace it with the latest version and it works! make sure you get the last edition of the extension pack as well

user12106937

I guess everyone installing those Windows 10 updates faces the issue.

I did not uninstall the older version of VirtualBox. I looked for a software update from the menu and updated from the exe. It is working fine now.

I have quite a few VMs for RAC and Cloudera that I had configured previously and did not want to take a chance in losing those, with an uninstall.

kyagh001

Hello,

I have the same problem but with Mac OS High Sierra

The virtual machine 'NeuroDebian 8.0.0 (64bit)' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code:

NS_ERROR_FAILURE (0x80004005)

Component:

MachineWrap

Interface:

IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

I have unistalled and reinstalled the Virtualbox multiple times... but nothing works.

1 person found this helpful
User_GHO69

Having the same issue. Trying out Oracle Linux for a customer POC - not looking good.
MacOS: BigSur 11.2.3 (20D91)
VirtualBox: Version 6.1.18 r142142 (Qt5.6.3)
Vagrant: Installed Version: 2.2.14
```
vagrant init oraclelinux/8 https://oracle.github.io/vagrant-projects/boxes/oraclelinux/8.json
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
~/w/c/oracle-linux ❯❯❯ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'oraclelinux/8' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'https://oracle.github.io/vagrant-projects/boxes/oraclelinux/8.json'
default: URL: https://oracle.github.io/vagrant-projects/boxes/oraclelinux/8.json
==> default: Adding box 'oraclelinux/8' (v8.3.195) for provider: virtualbox
default: Downloading: https://yum.oracle.com/boxes/oraclelinux/ol8/OL8U3_x86_64-vagrant-virtualbox-b195.box
default: Calculating and comparing box checksum...
==> default: Successfully added box 'oraclelinux/8' (v8.3.195) for 'virtualbox'!
==> default: Importing base box 'oraclelinux/8'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'oraclelinux/8' version '8.3.195' is up to date...
==> default: Setting the name of the VM: oracle-linux_default_1615574415202_38118
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "c457af36-4324-4928-83be-2f2b7aa8c6c5", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'oracle-linux_default_1615574415202_38118' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
```

1 - 15

Post Details

Added on Dec 11 2014
#oracle-virtualization, #virtualbox
15 comments
428,321 views