VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (187 - 189 of 16363)

Ticket Resolution Summary Owner Reporter
#21041 fixed v6.1.37 Test Builds Fail to Install - Signature verification failed while checking integrity of driver package 'VBoxSup.inf' Jacob Klein
Description

Originally reported here: https://forums.virtualbox.org/viewtopic.php?f=15&t=106662v6.1.37 Test Build 152627... fails to install.

It says: "Oracle VM VirtualBox 6.1.37 Setup Wizard ended prematurely" and VirtualBox Installer Installation failed! Error: Fatal error during installation.

Tested on Windows 10 Release Preview (19045.1865), and Windows 11 Dev Channel (25169.1000) ... since those are all that I have readily available.

Is the installer busted for this VirtualBox Test Build?

Oracle VirtualBox v6.1.36 Build 152435 ... continues to install fine. And I'm nearly sure that all the v6.1.35 Test Builds installed fine, too, from my testing.

=============================== Bug Details:

When I run the installer with option "--logging", I'm able to get an install log file in C:\Users\{User}\AppData\Local\Temp

See attached to compare these: VBoxInstallLog - 6.1.36 r152435.txt VBoxInstallLog - 6.1.37 r152676.txt

The main problem appears to be: DIFXAPP: ERROR: Signature verification failed while checking integrity of driver package 'VBoxSup.inf' ('C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.inf'). (Error code 0x800B0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.)

Is it possible that 6.1.35 Test Builds were WHQL signed, but 6.1.37 Test Builds are not? Note: I don't have my 6.1.35 Test Builds anymore, but I'm sure they worked.

#21037 duplicate 6.1.34 -> 6.1.36 breaks kbunbtu hightekvagabond
Description

Booting a kbuntu vm created in 6.1.34 from the latest kbuntu distro crashes on boot with a memory error on 6.1.36.

To recreate: 1) on a windows host install virtualbox 6.1.34 2) create a linux virtual machine and install the latest kbuntu 3) install the virtual box tools on the kbuntu instance 4) close the kubuntu instance by saving state 5) upgrade to virtualbox 6.1.36 6) start the kbuntu instance - instacrash

Sorry, don't have screen shots.

#21034 fixed Fail to contact COM server => Fixed in SVN efayol
Description

I'm using Ubuntu 20.04.4 on x86_64 with Gnome on X11. Since I've updated to 6.1.36, I cannot use any vbox command nor the VirtualBox VM Manager GUI: they stall a few minute then end with an error about COM.

  • The VirtualBox GUI displays an error dialog with the following message: "

Failed to acquire the VirtualBox COM object.

The application will now terminate.

Callee RC: NS_ERROR_ABORT (0x80004004) "

  • Command "VBoxManage list vms" sends the following to stderr:

VBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

Reinstalling Virtualbox 6.1.34, it is working fine again.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy