VirtualBox

Opened 10 years ago

Closed 8 years ago

#12601 closed defect (obsolete)

4.3.6 Cannot access the kernel driver

Reported by: A_User_Called_M Owned by:
Component: other Version: VirtualBox 4.3.6
Keywords: Cc:
Guest type: other Host type: Windows

Description

Host: Windows Vista Home Premium 32 bit SP2 Intel Core 2 Cpu 6600

Upgrading from 4.2.18 (or 4.2.16) Installed 4.3.6, and getting this error.

Failed to open a session for the virtual machine fed13.

The virtual machine 'fed13' has terminated unexpectedly during startup with exit code 1.

Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}


I then:

  • rebooted
  • uninstalled virtualbox. Removed all files from programfiles and from config. [1]
  • rebooted
  • run the installer as admin (anti virus (avg) and firewall disabled)
  • rebooted

I have UAC turned off. (But trying with it turned on made no difference)

[1] According to autoruns from SysInternals, there where a few Vbox.... files in system32/drivers that where registered as part of "Sun Virtualbox" (very old). I removed them too.

Still get the error. (With a newly created guest (fedora)

I have a log of the MSI install.

Attachments (1)

MSI3fa64.rar (40.7 KB ) - added by A_User_Called_M 10 years ago.

Download all attachments as: .zip

Change History (5)

by A_User_Called_M, 10 years ago

Attachment: MSI3fa64.rar added

comment:1 by A_User_Called_M, 10 years ago

Worst case scenario now: I uninstalled 4.3.6, rebooted, installed 4.2.18 (previously working), rebooted, and get the same error.

Same error with 4.2.22 too.

It seems I no longer can install any VBox at all (loosing access to all my VM)

The attempt with "repairing" the installation (as given on various places on the net) also does not work for me.

Any suggestions, what I could try, could look at, can do to help getting the issue fixed?

comment:2 by A_User_Called_M, 10 years ago

Solved, sorry about the report. The issue was in my windows system. (though maybe the installer could give a better error msg)

The CAPI2 (cryptographic) service was failing (it seems it was started/running, but not functioning. (root cause: new hard disk, old driver)

Or maybe it was teh related fold of some catalog (system32/catroot2), that went down at the same time.

comment:3 by moonleo, 10 years ago

I got the same error after I upgrade my virtual box (host windows 7)

Even I uninstall the virtualbox and reinstall the old version, I still the same error when I try to load any VM

Failed to open a session for the virtual machine ubantua1304.

The virtual machine 'ubantua1304' has terminated unexpectedly during startup.

Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {22781af3-1c96-4126-9edf-67a020e0e858}

Can any one help on how to solving it?

comment:4 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use