﻿ticket,summary,version,type,created,modified,_changetime,_description,_reporter
20908,Cannot install or delete VirtualBox,VirtualBox 6.1.34,task,2022-04-22T16:30:47Z,2022-04-26T12:47:42Z,2022-04-26T12:47:42Z,I migrated VitualBox from my Windows 10 computer to my Windows 11 computer. VirtualBox won't start; trying to Repair it is unsuccessful; trying to Reinstall it is unsuccessful; trying to Delete it is unsuccessful. Please help!,HorseyBob
20075,No VirtualBox packages for Ubutnu 20.10 'Groovy',VirtualBox 6.1.16,task,2020-12-01T16:15:55Z,2021-01-08T19:31:37Z,2021-01-08T19:31:37Z,"As of 2020-12-01 there are no VirtualBox DEB packages for
newly released (2020-10-22) Ubuntu version 20.10 'Groovy':

http://download.virtualbox.org/virtualbox/debian/dists/

VirtalBox packages for the previous Ubuntu release 20.04 'Focal'
require dependency package 'python-is-python2' to be installed,
but this breaks many other packages in Ubuntu 20.10, e.g. 'dh-python'.
",PHD
18731,Fatal No bootable medium found system halting (with iso inserted),VirtualBox 6.0.8,task,2019-06-29T14:45:12Z,2019-07-05T11:57:35Z,2019-07-05T11:57:35Z,"Error:
When trying to start a new vm with the disk and iso inserted into sata receiving error: Fatal No bootable medium found system halting. Solutions already attempted: changing from sata to ide, making it a live cd/dvd and hot pluggable, and updating to the most recent version (stable or not stable).",28202
17751,"""A critical error has occured while running the virtual machine and the machine execution has been stopped.""",VirtualBox 5.2.12,task,2018-05-10T17:19:51Z,2018-05-10T20:03:42Z,2018-05-10T20:03:42Z,"Hello.
I just installed VirtualBox on Windows 8.1, in order to install Kali Linux, however I keep getting the warning ""A critical error has occured while running the virtual machine and the machine execution has been stopped."".
What should I do?
Thank you in advance.",Nyctivoe
16470,Install Oracle Certificate automatically to Trusted Publishers store,VirtualBox 5.1.14,task,2017-02-09T09:48:11Z,2017-02-09T09:48:11Z,2017-02-09T09:48:11Z,"Please install the Oracle Corporation vertificate to Trusted Publishers store inside the MSI setup to prevent the driver popups. WiX has such a feature, see http://wixtoolset.org/documentation/manual/v3/xsd/iis/certificate.html

Without this it is complicated to deploy VirtualBox via AD for nothing. Other sofware also does this and does not bubble message boxes with untrusted drivers.",vboxuser4
21452,Please add require for kernel headers in Fedora rpm packages,VirtualBox-7.0.6,enhancement,2023-02-01T03:03:22Z,2023-02-01T03:03:22Z,2023-02-01T03:03:22Z,"A long time annoying missing thing is that Fedora rpms does not by itself fetch the required kernel headers,
and therefore won't work until user figures out whats missing.

YES - I am aware that Fedora have HAD a problem with fetching the wrong version - and that's most likely why you don't do it ....... but this is FIXED now.

Fedora now has a new package in all repos, that should fix this problem - it is called kernel-devel-matched

coming with this description:
This meta package is used to install matching core and devel packages for a given kernel.

Please add ""Requires: kernel-devel-matched"" for new releases, to finally fix this annoyance 
",Yoda
21124,VirtualBox v7's macOS installer should check the host's requirements first.,VirtualBox 7.0.0,enhancement,2022-10-11T00:28:35Z,2022-10-11T00:28:35Z,2022-10-11T00:28:35Z,"My upgraded VirtualBox (v7) told me that it doesn't run in my old, updated macOS Mojave v10.14.6. It told me this AFTER (install/upgrad)ing VirtualBox v6.1.38-153438 to v7. I had to uninstall v7 and reinstall the older version. It should had told me that BEFORE (install/upgrad)ing. :(",Ant
18128,Some strings are not translatable in macOS,VirtualBox 5.2.22,enhancement,2018-11-13T16:52:28Z,2018-11-14T19:08:34Z,2018-11-14T19:08:34Z,"In macOS some of the text is in english.
I would like the text to be translatable or removed for a more fully translation of VirtualBox.

Running the dmg file the first i see is the image from VirtualBox/.background/vbox_folder.tiff with the text:
""1 Double click on this icon:""
""2 Run the VirtualBox application
   from the Application Folder:""

Looking at other installers i have tried in macOS it seems they tend to use a way where you drag the icon to the application folder from left to right and then there might be an arrow suggesting what to do and some installations have no text.
If this is the ways its done in macOS then perhaps VirtualBox install could do it the same way so its consistent with how its done in other software and then perhaps the english text can be removed.



When i double click the installer (VirtualBox.pkg) i see some text like:
""Installer Oracle VM VirtualBox""
""Installering af Oracle VM VirtualBox""
""Oracle VM VirtualBox for Mac OS X""
""Welcome to Oracle VM VirtualBox 5.2.22 for Mac OS X! This installer...""

It seems to be from CoreServices/Installation so maybe the installer is already translated by Apple and then VirtualBox have added some strngs that is not translatable.
I would like the strings to be translatable.",scootergrisen
17413,simplify the automatically offered extension pack upgrade procedure,VirtualBox 5.2.4,enhancement,2018-01-03T09:28:31Z,2018-01-03T09:28:31Z,2018-01-03T09:28:31Z,"After upgrading an existing VirtualBox installation with extension pack installed and starting VirtualBox, a dialog is presented that an older extension pack was found and if the user wants to upgrade the extension pack. 

This is fine, however the procedure to upgrade the extension pack is rather complicated and goes as follows:

  - Older ExtPack was found, want to download and install new version? Click download
  - This is the file to download, still want to download? Click download
  - File was downloaded, upgrade? Click upgrade
  - Hey, here are the T&C for the ExtPack, agree? Click agree (after reading it carefully obviously  ;)
  - Installation occures
  - Installation successfull, do you want to delete the downloaded file? Click delete

Well, it's not that complicated but just rather annoying because it is every time the same thing and the user already made clear that he wanted to upgrade the ExtPack with the first click.

I would like to propose a simplification for this upgrade procedure:

  - After starting VirtualBox, the initial dialog is presented to give the user the chance to decide if he wants to upgrade or not
  - If the user decided to upgrade, a single dialog is presented.
    - It could contain either the link to the ExtPack that will be installed or a version comparison (current version vX.X.X, new version vX.X.Y)
    - It could contain a checkbox, which is checked by default, to delete the file after the upgrade
    - It could contain a linked message like ""By installing the extension pack, you agree to the T&C"" where the link poins to the said T&C
    - It has two buttons: ""Download & Install"" and ""Cancel""
    - Optionally display an OK dialog that installation was finished

This would drastically increase user friendliness and simplify the ExtPack upgrade procedure. Keeping the initial yes/no dialog choice to upgrade also helps the average joe to panic by being slapped in the face with a full blown dialog",Aoshi
16472,Default VirtualBox configuration in MSI,VirtualBox 5.1.14,enhancement,2017-02-09T12:00:23Z,2017-10-20T16:34:55Z,2017-10-20T16:34:55Z,"I need to preconfigure some global defaults for my users.

These are
- GUI/SuppressMessages=all
- GUI/UpdateDate=never
- defaultMachineFolder=""D:\Virtual Machines""

Updates are controlled via AD with MSI deployment. Can you add this as registry keys to the MSI setup, please? I explicitly need a way to set GLOBAL settings that are enforced to all users.",vboxuser4
17187,GPO: automatic update need to be disalbed per machine,VirtualBox 5.1.30,enhancement,2017-10-20T15:35:56Z,2017-10-20T16:20:49Z,2017-10-20T16:20:49Z,"We deploy the MSI file to some developer machines. However it annoys us permanently (every few weeks) about new unimportant version. I know there is a way to disable the warning per user, but this does not help as the software is installed per machine. I cannot change the settings file with a GPO.

We need a registry key or xml config file in app folder or a MSI propery (best) that allows us to disable automatic updates globally.

Always keep in mind that users are not allowed to install or update software.",Marc Bauer
14145,Virtualbox installer does not ask for admin rights (UAC) automatically,VirtualBox 4.3.28,enhancement,2015-05-22T19:35:36Z,2016-11-22T23:16:27Z,2016-11-22T23:16:27Z,"Summary:

Since Virtualbox needs to install drivers, it always needs admin privileges. An installer can be compiled to require this, and many programs that need such privileges are (e.g. Networx, made by SoftPerfect).

Virtualbox is not. If a user has UAC at its default setting (enabled, one notch down from the top), as most people do, then at least in a Vbox upgrade scenario one must remember to run the installer ""as admin.""  If this isn't done, then the installation will still look like it worked, but Virtualbox's system drivers will likely not be installed (if you look at the drivers after the reboot -- e.g. vboxdrv.sys, vboxusb.sys, vboxusbmon.sys, etc -- they will not have been updated).

Proposal:

Virtualbox be made to force elevation upon a normal double click, thereby guaranteeing that this will not be a problem for the forgetful.

Note: I have not provided a log since this problem is one that's visible before setup begins to do anything more than show its initial screen. Also, this isn't specific to any particular version. It's been like this for any version for Windows that I can remember up through the current version.",rseiler
16157,Windows installer should add VirtualBox path to the PATH environment variable,VirtualBox 5.1.8,enhancement,2016-11-06T09:02:09Z,2016-11-06T09:02:09Z,2016-11-06T09:02:09Z,"I believe the title pretty much covers it, but in detail, installing !VirtualBox on a Windows host should modify the ""PATH"" environment variable to include the !VirtualBox installation directory as well (typically {{{""C:\Program Files\Oracle\VirtualBox""}}}).

Reason? One less step to issue ""VBoxManage"" commands, one less step to make a mistake. Plus, it's already there in the other hosts...",Socratis
15475,Auto updater for system without a repository,VirtualBox 5.0.20,enhancement,2016-06-03T19:24:56Z,2016-06-03T19:24:56Z,2016-06-03T19:24:56Z,"An auto update system for VirtualBox would be awesome. Maybe using the integrated downloader (that for now seems quite pointless) as VMWare does, at least in Windows and OS X as there is no repository system and users always has to download and update manually. 
At least download the new version and launch the installer...",QcFe
14726,Remove option for Quick Launch shortcut from installer,VirtualBox 5.0.6,enhancement,2015-10-21T12:51:23Z,2015-10-21T13:01:43Z,2015-10-21T13:01:43Z,"There should not be an option for a Quick Launch shortcut in the Windows installer. This feature was deprecated 6.5 years ago with the launch of Windows 7; then it took a settings change to bring it back. With Windows 10, it takes a registry hack to bring back this feature.",Aren Cambre
12614,New rpm packaging convention of 4.3 and autoupgrade in OpenSuse 13.1,VirtualBox 4.3.6,enhancement,2014-01-15T22:37:10Z,2014-01-15T22:37:10Z,2014-01-15T22:37:10Z,"OpenSuse 13.1 (and maybe other releases) contains VirtualBox 4.2.* divided in several 
rpm (sub)packages as virtualbox, python-virtualbox, virtualbox-guest-kmp-desktop,
virtualbox-host-kmp-desktop, virtualbox-qt ...

if one have installed the 4.2.* release from the original distribution (4.2.18) or
from the community distro (http://download.opensuse.org/repositories/Virtualizatio/openSUSE_13.1/, 4.2.20) and then tries to upgrade to 4.3.*  everything seams to work
as aspected. but this is not a supported upgrade in rpm sense.
no provides oder obsolets entries in the all-in-one 4.3 packade gives the installer a hint to
delete the old installation or inform the user about conflicts.

the trouble begins when some uncontrolled or automatic upgrade see the
existing old entry and simple overwrites the new installation with old stuff.
as a result /dev/vboxdru disappiers and so on.

suse 13.1 is actally heavely under development, its rather a .0 oder a beta version.
i simple foregot one of the 4.2 packages to delete and than i spend a long time to underestand
what was going on.

my suggestion is to place additional Provides: statements with the old naming conventions
to the rpm or corresponding Obsoletes: statements. then the user will be informed and can decide what should happen.

regards
i.b.

(see also http://www.virtualbox.org/ticket/5884)






 
  ",iber
6057,[feature-request] Installer: warn users for incompatible drivers on Windows host,VirtualBox 3.1.2,enhancement,2010-01-22T10:11:14Z,2013-08-21T20:53:02Z,2013-08-21T20:53:02Z,"
I see there are some instances where vboxdrv or vboxnetflt drivers are incompatible with currently installed 3rd party drivers on Windows Host platform.

It would be better, especially for newbie users, if we detect such incompatibilities in our installer, and warn users.

Here is the known list: (and perhaps a few more that I overlook)

#3752 DNS protocol problem with Vista hosts => check Shrew Soft Lightweight filter rules

#5519 vboxnetflt: fatal BSOD installation on Marvell Server NIC

#3370 VBoxNetFlt: Conflict with the Trend Micro Anti-Virus driver

#3724 Host crash: vboxdrv crashes, when run together with coLinux

Other incompatible software:

-decndis.sys caused the crash on one user. decndis is part of the DEC (Digital Equipment Corp) LAT protocol that we use to access the VAX (reported by Huihong Luo of VMlite)

-Microsoft VirtualPC

-Microsoft Hyper-V

The same issues applies to Linux-host installer too, but since installers are platform-specific, it deserves a separate wish.

-Technologov, 22.1.2010",Technologov
3852,"vboxusers group should be added as a system group, not as an ordinary group",VirtualBox 2.2.0,enhancement,2009-04-26T17:04:25Z,2011-12-08T16:39:44Z,2011-12-08T16:39:44Z,"When installing VirtualBox-2.2.0_45846_fedora9-1.i386.rpm (on Fedora 10) a vboxusers group is created. Unfortunately it is created as an ordinary group and not as a system group, which means that it can clash with other (older) groups which haven't been (re)added yet to /etc/group.

The problem can be fixed by running ''groupadd'' with the '''-r''' parameter. Quoting from the man page:

  '''-r'''  This flag instructs groupadd to add a system account. The first available gid lower than 500 will be automatically selected unless the -g option is also given on the command line. This is an option added by Red Hat.",Cristian Ciupitu
8649,[feature-request] VBox Windows Installer should check for python version,VirtualBox 4.0.4,enhancement,2011-03-29T06:57:13Z,2011-11-08T02:02:44Z,2011-11-08T02:02:44Z,"Host: Windows (all), VBox 4.0.4

VBox currently installs python bindings even on buggy python modules. (python 2.5.1 and pywin32 v213)

1. in ""vboxshell.py"" terminal colors on Windows Vista/7 must be disabled by default, and it is a known python bug, checking for python version fixes garbage on those platforms

2. We must check for pywin32 version. v213 is known to be broken. This fixes VBox bug #8605

We should refuse to install python bindings (gray out this option, or gives warning message), if python modules are old.

-Technologov, 29.3.2011.",Technologov
4682,"Remove ""Create Quick Launch Icon"" from installer on Windows 7 and above",VirtualBox 3.0.4,enhancement,2009-08-05T09:31:40Z,2011-03-01T08:52:41Z,2011-03-01T08:52:41Z,"Since ""Quick Launch"" has been removed from Windows 7 and is unlikely to return in future builds of Windows, creating a quick launch icon should not be offered on Windows 7 an above. This is merely a cosmetic issue as this option has no effect on Windows 7 but should be fixed eventually.",Frank Freibuth
6178,[feature-request] Installer: Please introduce internal checksum,VirtualBox 3.1.4,enhancement,2010-02-12T23:36:09Z,2010-02-15T15:05:21Z,2010-02-15T15:05:21Z,"Some users, including me, experience bad downloads from time to time... which results in broken VBox installation.

Please introduce internal checksum, so installer won't proceed if it was damaged during download or by virus.

I had this problem on Windows hosts; Not sure if this is applicable to other hosts...

Similar issue: Bug #6177

-Technologov, 13.2.2010",Technologov
1526,Virtualbox 'Native' Menu of the Virtual Machine,VirtualBox 1.6.0,enhancement,2008-05-10T05:30:53Z,2008-08-19T20:26:56Z,2008-08-19T20:26:56Z,"Having a menu under the Applications menu(GNOME [linux OS]) wich is called 'VirtualBox' wich contains submenus of every virtual machine you have would be very useful, each of these submenus would contain the ""Start > all programs"" content of each of em, making it faster and easier for an end-user to access applications wich require Windows to be running, but these applications will run in seamless mode by opening them within this submenu making it feel like its a native application.",marcos
21451,Upcoming problem for Fedora 38 rpms,VirtualBox-7.0.6,defect,2023-02-01T02:26:58Z,2023-02-01T02:26:58Z,2023-02-01T02:26:58Z,"Fedora 38 (currently Rawhide - but due to be released in April) has tightened the security on the crypto on the rpm packages. While we until only few day ago could use your released Fedora36 packages on even rawhide, that is no longer possible, because your signing mechanism is now outdated.

This is just a heads up for Fedora 38 release in april - it should not affect current Fedora 35/36/37 releases.

Please read this blogpost from nirik about the changes:
https://www.scrye.com/wordpress/nirik/2023/01/31/error-rpmdbnextiterator-skipping-in-fedora-38/

",Yoda
21266,good day. The guest additions CD does not work. I think the CD drive is not working.,VirtualBox-7.0.2,defect,2022-11-11T23:19:44Z,2023-01-18T15:29:07Z,2023-01-18T15:29:07Z,"I tried several things but the cd player does not work, what would be the solution.",yuvlower.hacsshikkennvyu@…
21415,"Debian/Ubuntu repositories: remove dependency ""vitualbox-x.y recommends linux-image""",VirtualBox-7.0.6,defect,2023-01-17T23:59:41Z,2023-01-17T23:59:41Z,2023-01-17T23:59:41Z,"vitualbox-x.y packages in Debian/Ubuntu repositories should have their dependency

""vitualbox-x.y recommends linux-image"" removed.

1.

This dependency sometimes makes apt resolve conflicts by installing random ""linux-image-*"" packages (which provide ""linux-image"" virtual package).

This mostly includes Linux kernel images dedicated for cloud:
linux-image-*-azure, linux-image-*-gcp, linux-image-*-oracle, linux-image-*-aws

Automatically installing these makes an annoying mess in host's Linux installation,
and may also result in failed upgrades if /boot partition is too small to fit all these kernel images.

2.

At least 1 package providing ""linux-image"" is obviously most likely installed already in any Linux system, so this dependency is quite useless anyway.
",PHD
21327,macosx M2 Unable to import OVA with error NS_ERROR_INVALID_ARG,VirtualBox-7.0.4,defect,2022-12-07T13:54:36Z,2022-12-13T11:22:24Z,2022-12-13T11:22:24Z,"Does anyone have a work around for importing .ova files into Version 7.0.4_BETA4 r154605 (Qt6.3.0) on Mac M2 silicone?

With Regards,
",greyh0und
21295,Win 7 32b guest VM craash when installing guest additions 7.0.4,VirtualBox-7.0.4,defect,2022-11-22T22:05:47Z,2022-11-22T22:23:21Z,2022-11-22T22:23:21Z,"Host:
Ubuntu 20.04.5 LTS
kernel 5.4.0-132
Wayland, Gnome 3.36.8

Guest:
Windows 7 (32bit)
Guest Additions 7.0.2 previously installed

Procedure:
Start guest VM; boot; login
From VM window menu -> Devices -> Insert Guest Additions CD image...
Start Guest additions installer from Windows Explorer
Install runs through until the graphics driver is installed.
Window resizes shortly to VGA (probably the 'uninstall' of the old driver) then goes back to previous resolution (probably when the new driver is enabled).
This is the moment when the VM crashes.
Reproducible.
This error is new in 7.0.4. It was not there in 7.0.2.
The Windows VM can be restarted normally after the abort and the guest additions appear to be installed, including the graphics driver. Vbox Task Bar App reports v7.0.4 installed.

Maye a duplicate to https://www.virtualbox.org/ticket/21123",sunrider
21257,virtualbox kernal modules do not match,VirtualBox-7.0.2,defect,2022-11-09T14:14:22Z,2022-11-09T14:14:22Z,2022-11-09T14:14:22Z,"upgraded to version 7,error RTR3InitEx failed with rc=-1921 (fRtFlags=0x10000)(rc=1912)

kernel modules do not match extra

uninstalled, reset computer and still the same, strait back to verison 6.1.40 which works straight away",exinsp
21164,Virtualbox 7.0.0 - macOS - provisioning profile,VirtualBox 7.0.0,defect,2022-10-18T15:11:22Z,2022-10-18T21:56:08Z,2022-10-18T21:56:08Z,"Hi all,

I and other forum members noticed that the latest VB on macOS adds provisioning profile:

https://forums.virtualbox.org/viewtopic.php?f=8&t=107346

Would it be possible briefly explain what it is for? macOS profiles are very powerful thing usually used by corporate administrators to change behavior of managed computers, e.g. to install new root certs. Long story short it can have potentially security implications some of us care more than others.

Thank you for your clarification in advanced.

Kind Regards

kapitainsky",kapitainsky
21101,installation folder is not remembered when upgraded,VirtualBox 6.1.38,defect,2022-09-08T23:42:16Z,2022-09-08T23:42:16Z,2022-09-08T23:42:16Z,"the folder is not remembered when updated it falls bach to
the default on every time  tried several versions even the latest 6.1.38",sphinxios
21035,Upgrading from VirtualBox 6.1.34 to 6.1.36 on Windows results in incorrect drivers,VirtualBox 6.1.36,defect,2022-07-26T06:49:05Z,2022-07-26T06:49:05Z,2022-07-26T06:49:05Z,"Windows 11 Home. No previous installations of VirtualBox. Steps to reproduce:

Install 6.1.34. Install Extensions for 6.1.34. Create a VM (does not matter what it contains). Upgrade to 6.1.36. Install Extensions for 6.1.36.

Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys.

Uninstall VirtualBox. Reboot. Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys.

Manually remove VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys. Reboot.

Install 6.1.36. Install Extensions for 6.1.36 (confirm re-installation of extensions). Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys, VBoxSup.sys and VBoxUSBMon.sys.

It would appear that (1) the upgrade code in the 6.1.36 installer does not correctly remove the older drivers, (2) the 6.1.36 uninstaller does not correctly remove the (older) drivers, and (3) the upgrade code in the 6.1.36 installer does not correctly install the new drivers.",weird_stuff_happens
21001,la instalacion viene rota,VirtualBox 6.1.32,defect,2022-06-21T18:56:31Z,2022-06-21T19:10:27Z,2022-06-21T19:10:27Z,lo intalo despues de mucho tiempo sin instalarlo (pq antes el año pasado lo tenia instalado) viene con error critico y no abria asi q  abri el setup para repararlo y me encuentro q no se puede reparar,xd64
20878,Building kernel module fails on CentOS8 and Kernel 5.17,VirtualBox 6.1.32,defect,2022-03-23T08:28:45Z,2022-04-06T06:49:22Z,2022-04-06T06:49:22Z,"Had running VB6.1.32 under kernel 5.16. Reboot triggered after installing kernel 5.17. Build kernel driver failed with error.


{{{
Building the main VirtualBox module.
Error building the module:
make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.17.0-1.el8.elrepo.x86_64/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j16 modules
make[1]: warning: -j16 forced in submake: resetting jobserver mode.
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `if [ ""gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10)"" != """"gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)"""" ]; then \'
make[1]: *** [Makefile:1717: prepare] Error 1
make: *** [/tmp/vbox.0/Makefile-footer.gmk:117: vboxdrv] Error 2

}}}
",HRZ d. Universität Bielefeld
20753,VirtualBox exe failed to install on Windows 11,VirtualBox 6.1.30,defect,2021-12-30T21:18:44Z,2022-03-07T12:39:31Z,2022-03-07T12:39:31Z,"Hello,

I am facing a serious problem when installing virtualbox.exe
I tried multiple versions and all didn't install knowing that before I had vbox installed normally. But when I uninstalled it to update to the new version I got this problem.

I am using Windows 11.

Proof Of Concept:
1. Open `VirtualBox-6.1.30-148432-Win.exe` and proceed with the steps.
2. I get this error while installing
Error:
The Windows Installer Service could not be accessible. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
3. And after I hit `OK`. I get the following message.
Installation failed! Error: Fatal error during installation.

Please notice that any exe files are being installed normally without any errors. I am facing this problem when just installing virtual box.

I hope you can find a solution for this problem.

Kind Regards.",ahmad_halabi
20811,Test build release not installing on Linux,,defect,2022-02-04T15:09:33Z,2022-02-04T16:50:57Z,2022-02-04T16:50:57Z,"''Test build v.'': 6.1.33 r149712 (Qt5.6.1)
''Host'' Fedora 35; Gnome 41 on X.org

''Note'': Previous installation v. 6.1.32, whose source repository was RPMfusion,  did work as intended. All components related to Virtualbox were dully removed as instructed before the installation of that test build release.

Installation not operational; What follows' won't fix it.


{{{
# /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel ""header"" files matching the current kernel
for adding new hardware support to the system.
This system is currently not set up to build kernel modules.
Please install the Linux kernel ""header"" files matching the current kernel
for adding new hardware support to the system
}}}
",Ricky Tigg
20752,VirtualBox-6.1.30-SunOS-amd64-r148432.pkg failed on Solaris 10 1/13 s10x_u11wos_24a,VirtualBox 6.1.30,defect,2021-12-29T14:29:10Z,2021-12-29T19:36:19Z,2021-12-29T19:36:19Z,"Info for Solaris 10:

# cat release
                    Oracle Solaris 10 1/13 s10x_u11wos_24a X86
  Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
                            Assembled 17 January 2013


VB installation console output:
# pkgadd -G -d VirtualBox-6.1.30-SunOS-amd64-r148432.pkg

The following packages are available:
  1  SUNWvbox     Oracle VM VirtualBox
                  (i386) 6.1.30,REV=2021.11.22.16.37.46.148432

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1

Processing package instance <SUNWvbox> from </tmp/VirtualBox-6.1.30-SunOS-amd64-r148432.pkg>

Oracle VM VirtualBox(i386) 6.1.30,REV=2021.11.22.16.37.46.148432

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.


The installation of this package was previously terminated and
installation was never successfully completed.

Do you want to continue with the installation of <SUNWvbox> [y,n,?] y
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
Done.
Waiting for services from previous installation to be removed.........
Warning!!! Some service(s) still appears to be present
Using </> as the package base directory.
## Processing package information.
## Processing system information.
   327 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

The following files are being installed with setuid and/or setgid
permissions:
* /opt/VirtualBox/amd64/VBoxHeadless <setuid root>
* /opt/VirtualBox/amd64/VBoxNetAdpCtl <setuid root>
* /opt/VirtualBox/amd64/VBoxNetDHCP <setuid root>
* /opt/VirtualBox/amd64/VBoxNetNAT <setuid root>
* /opt/VirtualBox/amd64/VBoxSDL <setuid root>
* /opt/VirtualBox/amd64/VirtualBoxVM <setuid root>

* - overwriting a file which is also setuid/setgid.

Do you want to install these as setuid/setgid files [y,n,?,q] y

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <SUNWvbox> [y,n,?] y

Installing Oracle VM VirtualBox as <SUNWvbox>

## Installing part 1 of 1.
/opt/VirtualBox/vboxconfig.sh
[ verifying class <none> ]
[ verifying class <manifest> ]
## Executing postinstall script.
Checking for older bits...
//opt/VirtualBox/vboxconfig.sh: syntax error at line 682: `refgroup=$' unexpected
## ERROR!! Failed to remove older/partially installed bits.
pkgadd: ERROR: postinstall script did not complete successfully

Installation of <SUNWvbox> failed.

",Ming H
20748,6.1.30.148432 Install Results in Extract Path Error,VirtualBox 6.1.30,defect,2021-12-24T15:23:19Z,2021-12-24T15:31:48Z,2021-12-24T15:31:48Z,"Upon downloading the latest build and executing it I get the following error on Windows 10.

Failed to create extraction path 'C:\Users\ADMINI~1\AppData\Local\Temp\2\VirtualBox': VERR_PATH_NOT_FOUND

What I found is that the Temp\2 folder does not exist.  I manually created the 2 folder under temp and installation successfully completed after that.",Bruceman1
20691,Can't install virtualbox to other hard drive with msi parameter,VirtualBox 6.1.30,defect,2021-11-25T19:45:06Z,2021-12-10T08:02:36Z,2021-12-10T08:02:36Z,"Hello,


{{{
msiexec /i VirtualBox-6.1.30.msi /L*vx VirtualBox-6.1.30-install.log IAGREE=Yes /QB TARGETDIR=""D:\Program Files\Oracle\VirtualBox"" VBOX_INSTALLDESKTOPSHORTCUT=0 VBOX_START=0 ADDLOCAL=""VBoxApplication,VBoxUSB,VBoxNetworkFlt,VBoxPython""
}}}

D: is a hard drive formated in NTFS format


Virtualbox is installed to C:



",Owned
20692,No signature was present in the subject,VirtualBox 6.1.30,defect,2021-11-26T02:00:10Z,2021-11-26T04:14:03Z,2021-11-26T04:14:03Z,"Cannot install VirtualBox due to failure installing VBoxUSB driver:
{{{
Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
}}}

When viewing the properties of VBoxUSB.inf it reports the following for the sha256 cert:
{{{
No signature was present in the subject
}}}

I have attached signtool output comparing VBoxUSB.sys and VBoxUSB.cat. The same cert is successfully validated on the .sys but fails on the .cat with ""No signature found"".

I am running a dev build of Windows 11, not currently sure whether this issue affects all Windows 11.

Forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=104557",sgadsby
20598,Security & Privacy in MacOS doesn't give Oracle as option,VirtualBox 6.1.26,defect,2021-10-07T14:27:57Z,2021-10-07T15:41:51Z,2021-10-07T15:41:51Z,"Attempted to install VBox 6.1.26 on macOS X 11.6 Big Sur. Initial install gave errors due to Security & Privacy. After going into Security & Privacy and uninstalling VBox due to kernel-driver-not-installed-rc-1908-error attempted another install. Oracle does not come up as option in Security & Privacy. Tried re-starting computer and installing 6.1.26, also 6.1.24 but installer says ""Installed Successfully"" even though Oracle won't come up in Security & Privacy during install and kernels are missing.",Rick Szerminski
20576,Installer must be able to update VBoxSDS windows service entry,VirtualBox 6.1.26,defect,2021-09-25T18:05:32Z,2021-09-25T18:05:32Z,2021-09-25T18:05:32Z,"When VBoxSDS erxists in windows service list, installer fails. 

It's not so hard to invoke ""sc delete VBoxSDS"" command, report to user(write log entry) if necessary and successfully proceed. As it happens after manual ""sc delete"".

In case there was a failure with loss of previously installed files, simple over-[writing-existent-system-entries-]installation - the most obvious and easy solution - becomes troublesome and painful.",KDV
20575,"Installer must never rely on trash, left by previous version",VirtualBox 6.1.26,defect,2021-09-25T17:54:34Z,2021-09-25T17:54:34Z,2021-09-25T17:54:34Z,"Installing VBox of newer version into windows after ${user profile}/Local/Temp cleanup fails.
Installer starts to beg for previous version MSI package, providing no workarounds.

Installation process must flow successfully instead. Installer must be able to upgrade or eradicate previous version traces at least. No trash, especially (installing sub-)system critical one must be left. A warning(never blocking failure) message about eradicating previous version could be provided to user, if necessary.",KDV
20522,hang on windows after update notifier window pops up,VirtualBox 6.1.22,defect,2021-08-23T15:54:51Z,2021-08-23T15:54:51Z,2021-08-23T15:54:51Z,"i was using a relatively recent VirtualBox version on Windows 10
and was sending my host machine to sleep (as it works quite nice all the time).
after a wake up VBox brought up the notifyer dialog for a new version
beeing available on the internet for download. (not sure if that dialog is normally modal or not - but it would be better if its not!)
at this point i was no longer able to control the main application and neither the currently running VM window. neither keyboard nor mouse input were able to interact with any of the two main windows and (BAD THING HERE) not even with the update notifier pop up windows.

(closing either of this first with a task manager did not cure the situation for the other window.)",jetpilot
20473,Can't insall VirtualBox VM,VirtualBox 6.1.24,defect,2021-07-24T01:50:05Z,2021-07-24T01:50:05Z,2021-07-24T01:50:05Z,"Hi,

I cant' seem to run the attached VM to VirtualBox, please help",Shawnloveshorses161
20472,Can't insall VirtualBox,VirtualBox 6.1.24,defect,2021-07-23T20:13:48Z,2021-07-23T20:13:48Z,2021-07-23T20:13:48Z,"Hi :) 

I am on a Surface Pro 5 i5 4gbram, can't install VirtualBox on Windows 11. 

Did it on Windows 10 but not on 11.

It gives an error, Windows it can't run due to performance and it is basically this app can't run on this version of Windows.
",Shawnloveshorses161
20466,Virtualbox Extension Pack upgrade is unnecessarily convulted on Ubuntu,VirtualBox 6.1.24,defect,2021-07-21T09:31:46Z,2021-07-21T09:31:46Z,2021-07-21T09:31:46Z,"after upgrading the VirtualBox installation I need to follow the the following dialogs/procedure to upgrade the Extension Pack:
1. You have an old version... click Download
2. Are you sure you want to download... click Download
3. Do you wish to install ... click Install
4. An older version is already installed... click Upgrade
5. PUEL license agreement... read license to the bottom, click I Agree
6. Authentication is needed... enter admin pass
7. Successfully installed... click OK
8. Do you want to delete ... click Delete
This is frankly annoying and unnecessary.

This should be reduced to:
1. You have installed a new version of VirtualBox. You need to upgrade the Extension Pack. If you wish to do it, accept the PUEL license by entering the admin password. The package will be downloaded, installed. The old package is unusable, thus will be deleted.

Thanks for considering the change!",OM617
20465,Failure to load signed modules on UEFI secure boot system,VirtualBox 6.1.24,defect,2021-07-21T06:39:00Z,2021-07-21T06:39:00Z,2021-07-21T06:39:00Z,"As in title really. VirtualBox scripts build the modules, put them in right place but they (rightfully) cannot be loaded.

So I sign them.

And the story repeats - /usr/lib/virtualbox/vboxdrv.sh scripts doesn't recognize the drivers as valid ones, rebuilds them (trashing the signature I've just made) and the story repeats.

The problem probably is in line 330 in function module_available():

    [ ""$mod_dir"" != ""misc"" ] || return

which likely should be:

    [ ""$mod_dir"" = ""misc"" ] || return
",Tomek
20363,building kernel modules on a multiarch host fails,VirtualBox 6.1.22,defect,2021-05-13T15:17:30Z,2021-05-13T15:17:30Z,2021-05-13T15:17:30Z,"In the Makefile-header.gmk of the three actual kernel modules, the BUILD_TARGET_ARCH_DEF variable, that reflect in BUILD_TARGET_ARCH, the actually used one, is set by the shell command 
$(shell dpkg-architecture -qDEB_HOST_GNU_CPU)
But on a multiarch environment is perfectly sane having a 32 bit version of dpkg-architecture, even if running a 64 bit kernel or building for a 64 bit kernel installed but not running at the moment of building.
In such a case, the build fails because BUILD_TARGET_ARCH is set to i686.
Maybe it's a bug in dpkg, but please consider using a different method to find the target kernel architecture.
Regards
Claudio",Claudio Laurita
20340,Headless mode on Windows requires too high permissions because of COM security,VirtualBox 6.1.22,defect,2021-05-05T16:36:07Z,2021-05-05T16:36:07Z,2021-05-05T16:36:07Z,"I need to automatically run VMs headless WITHOUT any interactive user login after Windows booted. The started VMs should additionally run somewhat secure using a default, restricted non-admin user of Windows. This seems like exactly the setup recommended on non-Windows and am I using with Ubuntu 16.04 and phpVirtualBox currently. In theory this should easily be possible by creating a standard user in Windows and a task in the task scheduler to execute a VM headless using that user and e.g. the following command line:

> VBoxManage startvm ""[...]"" --type headless

While that works using an interactive login on the shell, it didn't work by default using task scheduler. The reason can be found in the event viewer of Windows:

> Durch die Berechtigungseinstellungen für ""Anwendungsspezifisch"" wird
> dem Benutzer ""TEPU\virtual_box"" (SID:
> S-1-5-21-3056241376-1506544733-1187908793-1167) unter der Adresse
> ""LocalHost (unter Verwendung von LRPC)"" keine Berechtigung vom Typ
> ""Lokal Aktivierung"" für die COM-Serveranwendung mit der CLSID
> {B1A7A4F2-47B9-4A1E-82B2-07CCD5323C3F}
> und der APPID
> {819B4D85-9CEE-493C-B6FC-64FFE759B3C9}
> im Anwendungscontainer ""Nicht verfügbar"" (SID: Nicht verfügbar)
> gewährt. Die Sicherheitsberechtigung kann mit dem Verwaltungstool
> für Komponentendienste geändert werden.

> Durch die Berechtigungseinstellungen für ""Computerstandard"" wird dem
> Benutzer ""TEPU\virtual_box"" (SID:
> S-1-5-21-3056241376-1506544733-1187908793-1167) unter der Adresse
> ""LocalHost (unter Verwendung von LRPC)"" keine Berechtigung vom Typ
> ""Lokal Aktivierung"" für die COM-Serveranwendung mit der CLSID
> {74AB5FFE-8726-4435-AA7E-876D705BCBA5}
> und der APPID
> {EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA}
> im Anwendungscontainer ""Nicht verfügbar"" (SID: Nicht verfügbar)
> gewährt. Die Sicherheitsberechtigung kann mit dem Verwaltungstool
> für Komponentendienste geändert werden.

Virtual Box installs COM servers which by default can only be started by the groups SYSTEM, ADMINISTRATOR or INTERACTIVE. My created user isn't any member of those groups when used by the task scheduler, but when logging in interactively and using the shell.

{{{
VirtualBox Application
{819B4D85-9CEE-493C-B6FC-64FFE759B3C9}
}}}

{{{
VirtualBox System Service
{EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA}
VBoxSDS
}}}

The security settings to start the necessary COM servers can be changed to include my created user with the necessary permissions and afterwards VBoxManage starts successfully and the COM-related error entries in the event viewer are gone. 

* https://ibb.co/6ysd4FZ
* https://ibb.co/DDsNzKW
* https://ibb.co/MZhwx7n
* https://ibb.co/ctrR7cp

As you already have an installer bringing services, device drivers etc. into the system, you could as well adjust security for those COM servers. Some other software simply creates a group for their own purposes, assigning the necessary permissions and document somewhere that users like the one created by me simply need to be a member of that group. That approach is pretty common, e.g. VMware and OpenVPN create custom groups for special maintenance as well.

I'm considering this a defect instead of an enhancement, because using users with least possible privileges is a recommended security practice and because COM isn't used on non-Windows, that approach works on other platforms. After fixing or working around this problem, VBox will be easier to use with the same concepts and good practices across more OS.

Thanks!",Thorsten Schöning
19989,VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33,VirtualBox 6.1.16,defect,2020-10-22T01:16:38Z,2021-02-03T20:19:45Z,2021-02-03T20:19:45Z,"VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64.rpm does not install on Fedora 33 with following error:

Erreur : 
 Problème: conflicting requests
  - nothing provides python(abi) = 3.8 needed by VirtualBox-6.1-6.1.16_140961_fedora32-1.x86_64


Test build VirtualBox-6.1.15-140899-Linux_amd64.run installs and works fine on Fedora 33.",Didier
20127,Finalize File System fails,VirtualBox 6.1.16,defect,2021-01-14T18:45:16Z,2021-01-14T18:45:16Z,2021-01-14T18:45:16Z,"Failed to finalize file system
",MikeTheBike
20121,[Extension_Pack] Linux downloads the .gz extension file instead of .vbox-extpack,VirtualBox 6.1.16,defect,2021-01-09T19:13:00Z,2021-01-09T19:13:00Z,2021-01-09T19:13:00Z,"Oracle_VM_VirtualBox_Extension_Pack-6.1.16.gz

After manually modifying the file name extension, it was possible to install the package.

Link: https://download.virtualbox.org/virtualbox/6.1.16/Oracle_VM_VirtualBox_Extension_Pack-6.1.16.vbox-extpack



OS:
cat /etc/os-release
NAME=""Ubuntu""
VERSION=""20.04.1 LTS (Focal Fossa)""
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=""Ubuntu 20.04.1 LTS""
VERSION_ID=""20.04""
HOME_URL=""https://www.ubuntu.com/""
SUPPORT_URL=""https://help.ubuntu.com/""
BUG_REPORT_URL=""https://bugs.launchpad.net/ubuntu/""
PRIVACY_POLICY_URL=""https://www.ubuntu.com/legal/terms-and-policies/privacy-policy""
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
",rh.silicon@…
19407,Extension Pack 6.1.4 Failed to install VERR_FILE_NOT_FOUND,VirtualBox 6.1.4,defect,2020-03-16T03:45:31Z,2020-11-26T13:35:49Z,2020-11-26T13:35:49Z,"I'm on Mac OS X Yosemite 10.10.5 running VirtualBox 6.1.4

When trying to install Oracle_VM_VirtualBox_Extension_Pack-6.1.4.vbox-extpack , i faced Failed to install the Extension Pack /Users/..../Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.1.4.vbox-extpack.


{{{
﻿Failed to load the main module ('/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'): VERR_FILE_NOT_FOUND - dlopen(/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib, 6): no suitable image found. Did find:
/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib: code signature invalid for '/Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/darwin.amd64/VBoxPuelMain.dylib'
}}}

Could someone please enlighten where i've gone wrong ? 
",writetokelvin
20017,VB installation failing in linux kernel drivers installation,VirtualBox 6.1.16,defect,2020-11-04T18:13:31Z,2020-11-06T08:08:19Z,2020-11-06T08:08:19Z,"Host is a Debian 10.
Kernel is 5.9.3.

Compilation of modules located in /usr/src/vboxhost-6.1.16 fail during the install stage.
It is the vboxpci driver.

I checked its content and it seems there has been some cleaning there (all Makefile*) files, etc.

I have managed to bypass that failure to install and all other drivers get installed
(I just renamed the vboxpci to vboxpci.del in order to be bypassed).

I can run VirtualBox but then (my guess is that) VT-d, for the guest machines, cannot be enabled.


Regards,
Josep",jepjepus
19992,VirtualBox does not install on Fedora 32,VirtualBox 6.1.16,defect,2020-10-22T14:39:52Z,2020-10-28T14:36:49Z,2020-10-28T14:36:49Z,"uname -a: Linux master-1.fios-router.home 5.8.15-201.fc32.x86_64 #1 SMP Thu Oct 15 15:56:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Installed: kernel-devel.x86_64 ver 5.8.15-201.fc32
           kernel-headers.x86_64 ver 5.8.11-200.fc32
           VirtualBox-6.1.x86_64 ver 6.1.16_140961_fedora32-1
           gcc.x66_64 ver 10.2.1-5.fc32
All packages installed via dnf from the appropriate repositories.

vboxconfig fails. Log:
Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.
Error building the module:
make: *** No rule to make target 'install'.  Stop.

I suspect that the underlying cause is that the version of kernel-headers doesn't match the exact version of the kernel. However, the fedora-32 repositories don't contain a package named kernel-headers-5.8.15; kernel-headers-5.8.11 is the most recent. Any other info you need? Any suggestions?",rws
19846,VIRTUALBOX 6.1.6,VirtualBox 6.1.6,defect,2020-08-31T13:04:38Z,2020-08-31T13:15:16Z,2020-08-31T13:15:16Z,"Salve,gentilmente ho un problema in WINDOWS10 di installazione nuova versione, in poche parole non posso piu aggiornare Vb perche manga il file VirtualBox-6.1.6-r137129-Win.msi, non riesco piu ha trovarlo non ce lo piu, quindi non posso installare la nuova versione e neanche disistallare, ho fatto pure uno sbaglio ho cancellato alcuni file cartelle e file di registro manualmente senza risolvere il problema, non mi era mai capitato un problema del genere, il file.MSI lo scaricato da voi,e non lo trovo piu
se cortesemente mi potete aiutare ha trovare il file .MSI oppure mi date una soluzione, nelle faq non ho trovato la soluzione.",Tris
19801,add redhat8_ks.cfg kickstart config to unattended templates,VirtualBox 6.1.10,defect,2020-08-07T14:16:55Z,2020-08-12T12:33:42Z,2020-08-12T12:33:42Z,"From: ""Timothy Tacker"" <>
To: vbox-dev@virtualbox.org
Subject: [vbox-dev] [PATCH] add redhat8_ks.cfg kickstart
Date: Tue, 21 Jul 2020 14:49:04 +0200

Due to changes in RHEL 8, the redhat67_ks.cfg Kickstart script included in the UnattendedTemplates directory does not work with CentOS 8. The patch below adds a Kickstart script for RHEL 8 and CentOS 8, and makes other changes to integrate the new script into VirtualBox. Following the pattern for redhat67_ks.cfg, the new script is named redhat8_ks.cfg. All comments in the new script are worded to mirror language and terms used in the RHEL 8 documentation; and all sections, commands, and options appear in the same order in both the new script and the documentation.

The install command has been deprecated in RHEL 8. In regard to the install command, the documentation states, ""Use its methods as separate commands.""
The cdrom command was retained and now serves to specify that installation should occur from the first optical drive. The install command was removed from the new script.

The auth command has been deprecated in RHEL 8. Passwords are shadowed by default with sha512. The following auth command was removed from the new script:
auth  --useshadow  --passalgo=sha512

The default SELinux policy is enforcing. The following selinux command was removed from the new script:
selinux --enforcing

The documentation states, ""Either the --vckeymap= or the --xlayouts= option must be used"" for the required keyboard command, suggesting an OR rather than an AND. Nonetheless, both --vckeymap=us and --xlayouts='us' are used
in the new script. Many examples of this usage can be found, and it does not appear to cause issues. The value ""us"" was specified to maintain consistency with the value that was specified in the redhat67_ks.cfg script.

In order to comply with the order demonstrated in the syntax shown in the documentation, the timezone command was changed as follows:
timezone@@VBOX_COND_IS_RTC_USING_UTC@@ --utc@@VBOX_COND_END@@
@@VBOX_INSERT_TIME_ZONE_UX@@
timezone @@VBOX_INSERT_TIME_ZONE_UX@@@@VBOX_COND_IS_RTC_USING_UTC@@ --utc@
@VBOX_COND_END@@

For the --plaintext option to the user command, the documentation states, ""If this option is present, the password argument is assumed to be in plain text""; but it does not explicitly indicate plaintext is the default. The --plaintext option was added to the user command as follows:
user --name=@@VBOX_INSERT_USER_LOGIN_SH@@
--password=@@VBOX_INSERT_USER_PASSWORD_SH@@
user --name=@@VBOX_INSERT_USER_LOGIN_SH@@
--password=@@VBOX_INSERT_USER_PASSWORD_SH@@ --plaintext

For the network command, DHCP is the bootproto method used by default. In addition, due to a change in how network devices are named in RHEL 8, eth0 is not a valid device name by default; but the link keyword can be used to specify the first interface with its link in the up state. The network command was changed as follows:
network  --bootproto=dhcp --device=eth0 --onboot=on
--hostname=@@VBOX_INSERT_HOSTNAME_FQDN_SH@@
network --device=link --onboot=on  
--hostname=@@VBOX_INSERT_HOSTNAME_FQDN_SH@
@

For the bootloader command, mbr is the default value for the location
option. The bootloader command was changed as follows:
bootloader --location=mbr --append=""nomodeset crashkernel=auto rhgb quiet""
bootloader --append=""nomodeset crashkernel=auto rhgb quiet""

The autopart command automatically creates partitions in accordance with Red Hat recommendations. The value plain for the type option specifies ""Regular partitions with no LVM."" The following two part commands were changed to the single autopart command on the third line immediately below:
part / --fstype ext4 --size 6000 --grow --asprimary
part swap --size 1024
autopart --type=plain

Without the elfutils-libelf-devel package installed, post install scripting failed to compile kernel modules for VirtualBox Guest Additions, resulting in their failure to install. The elfutils-libelf-devel package was added to the %packages section in order to resolve this issue.

Only the new Kickstart script has been tested, and it has only been tested with CentOS 8. OS and Guest Additions both install. Full testing with RHEL 8 should be completed prior to integration.

I'm licensing this patch under the MIT license. Please review. Feedback is welcome. Thanks!

Timothy Tacker
{{{
---
  src/VBox/Installer/Config.kmk                 |   1 +
  .../Main/UnattendedTemplates/Makefile.kmk     |   1 +
  .../Main/UnattendedTemplates/redhat8_ks.cfg   | 116 ++++++++++++++++++
  src/VBox/Main/include/UnattendedInstaller.h   |  11 ++
  4 files changed, 129 insertions(+)
  create mode 100644 src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg

diff --git a/src/VBox/Installer/Config.kmk b/src/VBox/Installer/Config.kmk
index 077d6af6..0cbcfe8d 100644
--- a/src/VBox/Installer/Config.kmk
+++ b/src/VBox/Installer/Config.kmk
@@ -66,6 +66,7 @@ ifdef VBOX_WITH_UNATTENDED
   rhel4_ks.cfg \
   rhel5_ks.cfg \
   redhat67_ks.cfg \
+ redhat8_ks.cfg \
   win_nt5_unattended.sif \
   win_nt6_unattended.xml \
         \
diff --git a/src/VBox/Main/UnattendedTemplates/Makefile.kmk
b/src/VBox/Main/UnattendedTemplates/Makefile.kmk
index c8baeaf5..cd15ffb4 100644
--- a/src/VBox/Main/UnattendedTemplates/Makefile.kmk
+++ b/src/VBox/Main/UnattendedTemplates/Makefile.kmk
@@ -32,6 +32,7 @@ ifdef VBOX_WITH_UNATTENDED
   rhel4_ks.cfg \
   rhel5_ks.cfg \
   redhat67_ks.cfg \
+ redhat8_ks.cfg \
   ol_ks.cfg \
   fedora_ks.cfg \
   suse_autoinstall.xml \
diff --git a/src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg
b/src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg
new file mode 100644
index 00000000..d37f8baa
--- /dev/null
+++ b/src/VBox/Main/UnattendedTemplates/redhat8_ks.cfg
@@ -0,0 +1,116 @@
+#platform=x86, AMD64, or Intel EM64T
+#version=DEVEL
+
+
+## Installation program configuration and flow control commands:
+
+# Install from first optical drive.
+cdrom
+
+# Specify info as minimum log level on tty3 in Anaconda during
installation.
+logging --level=info
+
+# Attempt to eject bootable media and reboot after installation.
+reboot --eject
+
+# Perform installation in text mode.
+text
+
+
+## System configuration commands:
+
+# Do not configure iptables rules.
+firewall --disabled
+
+# Set available keyboard layouts for system.
+keyboard --vckeymap=us --xlayouts='us'
+
+# Set language to use during installation and default to use on installed
system.
+lang @@VBOX_INSERT_LOCALE@@
+
+# Set system root password using supplied plaintext.
+rootpw --plaintext @@VBOX_INSERT_ROOT_PASSWORD_SH@@
+
+# Set system time zone and indicate if hardware clock is UTC (Greenwich
Mean) time.
+timezone @@VBOX_INSERT_TIME_ZONE_UX@@@@VBOX_COND_IS_RTC_USING_UTC@@ --utc@
@VBOX_COND_END@@
+
+# Create new user on system and set password using supplied plaintext.
+user --name=@@VBOX_INSERT_USER_LOGIN_SH@@
--password=@@VBOX_INSERT_USER_PASSWORD_SH@@ --plaintext
+
+
+## Network configuration commands:
+
+# Configure network device and activate in Anaconda installation
environment.
+#  Device specified in first network command activated automatically.
+#  DHCP method used by default.
+#  Device: Link keyword specifies first interface with link in up state.
+#  Onboot: Enable device at boot time.
+#  Hostname: Specify host name for installed system.
+network --device=link --onboot=on
--hostname=@@VBOX_INSERT_HOSTNAME_FQDN_SH@@
+
+
+## Storage handling commands:
+
+# Specifify how boot loader installed.
+#  Location boot record written dependent on drive usage of MBR or GPT
scheme.
+#  Append: Specifies additional kernel parameters.
+bootloader --append=""nomodeset crashkernel=auto rhgb quiet""
+
+# Remove partitions from system prior to creation of new partitions.
+#  All: Erase all partitions on disks reachable by installation program,
including attached network storage.
+#  Initlabel: Initialize disk(s) by creating default labels in respective
architectures designated for formatting.
+clearpart --all --initlabel
+
+# Automatically create partitions.
+#  Type: Plain keyword specifies regular partitioning scheme with no LVM.
+#  Default file system is xfs.
+autopart --type=plain
+
+# Initialize invalid partition tables and destroy contents of disks with
invalid partition tables.
+zerombr
+
+
+# Packages.  We currently ignore missing packages/groups here to keep
things simpler.
+%packages --ignoremissing
+@base
+@core
+@@VBOX_COND_IS_NOT_MINIMAL_INSTALLATION@@
+@development
+@basic-desktop
+@desktop-debugging
+@desktop-platform
+@fonts
+@general-desktop
+@graphical-admin-tools
+@remote-desktop-clients
+@x11
+@@VBOX_COND_END@@
+
+# Prepare building the additions kernel module, try get what we can from
the cdrom as it may be impossible
+# to install anything from the post script:
+kernel-headers
+kernel-devel
+glibc-devel
+glibc-headers
+gcc
+dkms
+make
+bzip2
+perl
+elfutils-libelf-devel
+
+%end
+
+
+# Post install happens in a different script.
+# Note! We mount the CDROM explictily here since the location differs
between fedora 26 to rhel5
+#       and apparently there isn't any way to be certain that anaconda
didn't unmount it already.
+%post --nochroot --log=/mnt/sysimage/root/ks-post.log
+df -h
+mkdir -p /tmp/vboxcdrom
+mount /dev/cdrom /tmp/vboxcdrom
+cp /tmp/vboxcdrom/vboxpostinstall.sh /mnt/sysimage/root/vboxpostinstall.sh
+chmod a+x /mnt/sysimage/root/vboxpostinstall.sh
+/bin/bash /mnt/sysimage/root/vboxpostinstall.sh --rhel
+umount /tmp/vboxcdrom
+%end
diff --git a/src/VBox/Main/include/UnattendedInstaller.h
b/src/VBox/Main/include/UnattendedInstaller.h
index 5003613d..09988815 100644
--- a/src/VBox/Main/include/UnattendedInstaller.h
+++ b/src/VBox/Main/include/UnattendedInstaller.h
@@ -518,6 +518,17 @@ protected:
  };


+/**
+ * RHEL 8 installer (same as RHEL 6 & 7, except for the kickstart
template).
+ */
+class UnattendedRhel5Installer : public UnattendedRhel6And7Installer
+{
+public:
+    UnattendedRhel5Installer(Unattended *pParent) :
UnattendedRhel6And7Installer(pParent, ""redhat8_ks.cfg"") {}
+    ~UnattendedRhel5Installer() {}
+};
+
+
  /**
   * RHEL 5 installer (same as RHEL 6 & 7, except for the kickstart
template).
   */
--
}}}

https://www.virtualbox.org/pipermail/vbox-dev/2020-July/015524.html
",Frank Batschulat (Oracle)
19797,installed virtualbox 6.1.12 on centos 7 but vboxweb-service is not started,VirtualBox 6.1.10,defect,2020-08-06T11:52:45Z,2020-08-06T11:52:45Z,2020-08-06T11:52:45Z,"installed virtualbox 6.1.12 but vboxweb-service is not started.
i tried to start ------>
systemctl start vboxweb-service

""Job for vboxweb-service.service failed because the control process exited with error code. See ""systemctl status vboxweb-service.service"" and ""journalctl -xe"" for details.""

systemctl status vboxweb-service -l
● vboxweb-service.service
   Loaded: loaded (/usr/lib/virtualbox/vboxweb-service.sh; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-08-06 17:19:28 IST; 1min 17s ago
  Process: 5801 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=1/FAILURE)

Aug 06 17:19:28 localhost.localdomain systemd[1]: Starting vboxweb-service.service...
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: Starting VirtualBox web service.
Aug 06 17:19:28 localhost.localdomain su[5807]: (to admin) root on none
Aug 06 17:19:28 localhost.localdomain vboxweb-service.sh[5801]: vboxweb-service.sh: failed: VirtualBox web service failed to start.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service: control process exited, code=exited status=1
Aug 06 17:19:28 localhost.localdomain systemd[1]: Failed to start vboxweb-service.service.
Aug 06 17:19:28 localhost.localdomain systemd[1]: Unit vboxweb-service.service entered failed state.
Aug 06 17:19:28 localhost.localdomain systemd[1]: vboxweb-service.service failed.",pmssy
19746,while installing os it stucks at black screen,VirtualBox 6.1.10,defect,2020-07-22T06:20:18Z,2020-07-22T06:20:18Z,2020-07-22T06:20:18Z,"I checked off Hyper-V and 3D acceleration but still, it's stuck at the black screen I waited for half-hour its shows running and stuck at the black screen",promethius
19673,"offering, downloading and installing new versions not supported by host",VirtualBox 6.1.10,defect,2020-06-19T15:57:21Z,2020-06-19T15:59:46Z,2020-06-19T15:59:46Z,"You have three opportunities to tell a user that the software they have been offered, are downloading, or installing is not supported by their OS. You don't. Instead, the user installs the software only to later discover some feature (such as installing an ExtensionPack) no longer works. This could be improved.",littlerunningdeer
17811,VirtualBox (vboxdrv) installation FAILED on some Windows 7 PCs,VirtualBox 5.2.12,defect,2018-06-08T02:16:11Z,2020-06-15T19:31:59Z,2020-06-15T19:31:59Z,"Hi All,

I'we got a new Win 7 PC: Toshiba Z40-C laptop with Intel Core i7 6600U CPU.
VirtualBox 5.2.12 (latest), but also tried 5.1.38 and 5.0.40, with the
same problem. (and even the ancient 4.1.6 version from 2011, before hardening)

One thing is special about this particular Windows 7 PC: It uses UEFI.
All the other dozens of my Windows 7 PCs, where VirtualBox works like
a charm, all use BIOS.
Maybe some kind of security properties do differ somehow.

VBox.log:
https://www.dropbox.com/s/8ss3510bofy4ntd/vbox.log.txt?dl=0

The problem is: no matter what I do, ""vboxdrv"" never gets installed.

It says cannot start VM : ""Make Sure the kernel module has been loaded
successfully"".

Error in supR3HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed

Looking at a list of drivers in ""Device Manager"", I cannot see
""vboxdrv"" listed there. (Even with show hidden -> Non-plug-n-play
devices)

More info:
C:\Users\Alexey>sc.exe query vboxdrv

{{{
SERVICE_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 2  (0x2)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
}}}

It seems there is a conflict between VirtualBox and some other
software / device driver on my PC, or OS configuration. But how to figure it out ?
The PC is totally new, but it has a lot of Toshiba drivers & utils included.
Restarting the PC (the Windows way) didn't help either.

Registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
{{{
DisplayName=VBox Support Driver
ImagePath=\??\C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys
ErrorControl=1
Start=3
Type=1
}}}

Event Viewer:
{{{
System/Information

---
A service was installed in the system.

Service Name:  VBox Support Driver
Service File Name:  C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys
Service Type:  kernel mode driver
Service Start Type:  demand start
Service Account:

---
System/Error

The VBox Support Driver service failed to start due to the following error:
The system cannot find the file specified.
}}}


In reality the driver file exists:

C:\Windows\System32\drivers\vboxdrv.sys
and
C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv.sys

yet, it is completely absent from Windows Device Manager (driver list).
So the driver was copied, but not loaded.


-Alexey Eromenko ""Technologov"". 08.06.2018.",Technologov
19592,dnf upgrade of virtual box sequence,VirtualBox 6.1.8,defect,2020-05-16T21:33:02Z,2020-05-22T12:20:53Z,2020-05-22T12:20:53Z,"The update sequence seems wrong, taking steps to apply 6.1.6 after 6.1.8 

Output to screen:

# dnf upgrade
Last metadata expiration check: 1:17:10 ago on Sat 16 May 2020 03:43:57 PM EDT.
Dependencies resolved.
=========================================================================================================================
 Package                      Architecture         Version                                Repository                Size
=========================================================================================================================
Upgrading:
 VirtualBox-6.1               x86_64               6.1.8_137981_fedora31-1                virtualbox                94 M

Transaction Summary
=========================================================================================================================
Upgrade  1 Package

Total download size: 94 M
Is this ok [y/N]: y
Downloading Packages:
VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64.rpm                                        3.8 MB/s |  94 MB     00:24    
-------------------------------------------------------------------------------------------------------------------------
Total                                                                                    3.8 MB/s |  94 MB     00:24     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                 1/1 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Upgrading        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Running scriptlet: VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 

Creating group 'vboxusers'. VM users must be member of that group!


  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Cleanup          : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Running scriptlet: VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 
  Verifying        : VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                   1/2 
  Verifying        : VirtualBox-6.1-6.1.6_137129_fedora31-1.x86_64                                                   2/2 

Upgraded:
  VirtualBox-6.1-6.1.8_137981_fedora31-1.x86_64                                                                          

Complete!

",Wheaties
19573,Can not install Ubuntu 18.04 or 20.04 only 16.04,VirtualBox 6.1.6,defect,2020-05-08T11:40:55Z,2020-05-08T11:40:55Z,2020-05-08T11:40:55Z,"I tried to install Ubuntu 20.04 but it freezes during installation, then I tried 18.04 and same result, then I tried 16.04 and that installed normally.

I have windows 10, MSI Prestige laptop with 256GB SSD and 8GB memory
Version	10.0.18363 Build 18363


",Fugit185
19498,vbox 6.1.2 vboxnetdhcp process blocks the update to vbox 6.1.6,VirtualBox 6.1.6,defect,2020-04-16T11:01:53Z,2020-04-16T11:01:53Z,2020-04-16T11:01:53Z,you need to close vbox 6.1.2 and REBOOT your (windows 10) pc before installing / updating to vbox 6.1.6,clive darra
19472,Update from VirtualBox 5.2 to 6.1.4 errors,VirtualBox 6.1.4,defect,2020-04-08T19:17:32Z,2020-04-08T19:17:32Z,2020-04-08T19:17:32Z,"I ran the VirtualBox 5.2 .run uninstall, which said it completed normally.  I then ran the VirtualBox6.1.4 .run and it said it installed fine.  VBoxManage -v indicates VirtualBox5.2 is still installed and the VirtualBox Manager does not look like the 6.1.4 version I have on another machine.  The Host machine is Centos6.7 and the guests I had on it were also Centos6.7",njmontfort
19387,Install of VirtualBox 6.1.4 crashes Sudoers on Ubuntu 18.4.4,VirtualBox 6.1.4,defect,2020-03-09T01:29:27Z,2020-03-09T06:39:53Z,2020-03-09T06:39:53Z,When I install VirtualBox 6.1.4 on Ubuntu 18.04.4 the sudoers complex of files is corrupted somehow and the owner of the system can no longer use the sudo command to run as administrator. One example of this is trying to install VirtualBox extensions after installing VirtualBox which always fails on authentication. This behavior survives a reboot.,jgossage
19344,VirtualBox 6.1.14 install fails on RedHat family,VirtualBox 6.1.4,defect,2020-02-24T11:29:57Z,2020-02-29T07:46:02Z,2020-02-29T07:46:02Z,"Can not install VirtualBox using the repository:

{{{
# cat /etc/yum.repos.d/virtualbox.repo
[virtualbox]
name=Yum Repository
baseurl=http://download.virtualbox.org/virtualbox/rpm/fedora/$releasever/$basearch
enabled=1
fastestmirror_enabled=0
gpgcheck=1
gpgkey=https://www.virtualbox.org/download/oracle_vbox.asc

#  dnf install -y VirtualBox-6.1
[...]
Error: Transaction test error:
  file /usr/bin/VBox conflicts between attempted installs of VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64 and VirtualBox-5.2-5.2.38_136252_fedora29-1.x86_64
[...]
}}}

The same problem appears with several distros (Fedora 30, Fedora 29, CentOS 7.7) and with several versions of the package (VirtualBox-6.1-6.1.4, VirtualBox-6.1-6.1.2, VirtualBox-6.0-6.0.18)

Looks like VirtualBox-5.2 is attempted to be installed alongside VirtualBox-6.x, as a dependency, and both packages clashes.

Seems very similar to issue #18924",luisg.muniz
19325,6.1.4_136177_fedora31-1 : Checksum mismatch,VirtualBox 6.1.2,defect,2020-02-20T10:22:35Z,2020-02-20T11:37:48Z,2020-02-20T11:37:48Z,"When updating Virtualbox by Fedora dnf tool, following message appears:

{{{
# LANG=C  dnf update
Fedora 31 - x86_64 - VirtualBox                                                                     1.2 kB/s | 181  B     00:00    
Dependencies resolved.
====================================================================================================================================
 Package                         Architecture            Version                                  Repository                   Size
====================================================================================================================================
Upgrading:
 VirtualBox-6.1                  x86_64                  6.1.4_136177_fedora31-1                  virtualbox                  100 M

Transaction Summary
====================================================================================================================================
Upgrade  1 Package

Total download size: 100 M
Is this ok [y/N]: y
Downloading Packages:
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[MIRROR] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 21ee97ad781368ae5655a2d87f3e172139ecd022e640b47419075633e5dfd9fd(sha256)  Expected: 64d3c8e3462d6b229664f80845486ae8c576bc38a7a3eb633b01a93a906de55a(sha256) 
[FAILED] VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success

The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
  Cannot download VirtualBox-6.1-6.1.4_136177_fedora31-1.x86_64.rpm: All mirrors were tried
}}}

Obviously packages are broken or checksum was calculated wrong.

Due to security reasons this update was rejected by package manager.",bitkocher
18645,Install of kernel drivers fails with osx 10.14.5,VirtualBox 6.0.8,defect,2019-05-15T10:47:11Z,2020-01-26T03:27:50Z,2020-01-26T03:27:50Z,"During installation of VBOX the OSX system show a message to contact Oracle because the software is not compatible with the last upgrade of OSX and the installation fails.

This problem appears after upgrading OSX to 10.14.5 version.

The same error also trying installing previous versions of VBOX.

",Tunesi Edoardo Fabio
19223,VirtualBox Extension Pack 6.0.16 installation failure,VirtualBox 6.0.14,defect,2020-01-14T22:26:29Z,2020-01-19T21:32:23Z,2020-01-19T21:32:23Z,"Following 100% download of the Extension Pack for version 6.0.16, and during the verifying VirtualBox Extension Pack... the error message is displayed: ""The network operation failed with the following error: During network request: Url not found on the server."" I have attached the screenshot of this. Despite many repeated attempts, the error persists.",NickD
19216,"When installing Ubuntu with finnish language, can no see continue tab",VirtualBox 6.0.14,defect,2020-01-10T09:49:10Z,2020-01-10T09:49:10Z,2020-01-10T09:49:10Z,"Problem description:
When installing ubuntu-18.04.3-desktop-amd64 with language set to Finnish (Suomi) then next setup windows don't show ""continue"" button. I can continue using Tab button, so it means that continue button is there but it is not visible

Enviroment
Windows machine with 8G mem 250Gb SSDdisk and i5 Intel
Virtual machine has 2G memory and 15Gb disk allocated",Fugit185
19092,6.0.14 Extensio Pack installation error on Linux Mint Debian Edition 3,VirtualBox 6.0.14,defect,2019-11-16T22:39:26Z,2019-11-17T01:57:01Z,2019-11-17T01:57:01Z,"Система LMDE 3,Ошибка установки VirtualBox 6.0.14 Oracle VM VirtualBox Extension Pack.",gri
19072,VirtualBox 6.0.14 Oracle VM VirtualBox Extension Pack unable to install,VirtualBox 6.0.14,defect,2019-11-08T13:44:40Z,2019-11-12T09:09:08Z,2019-11-12T09:09:08Z,"Upgrade of VirtualBox from 6.0.12 to 6.0.14 was successful but an issue happened during the upgrade of Extension Pack.

Fix: Manual removing all files under ''C:\Program Files\Oracle\VirtualBox\ExtensionPacks''

Error
''Failed to install the Extension Pack C:/Users/i314866/Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-7152' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


VBoxExtPackHelperApp.exe: error: Failed to delete the temporary extension pack directory: VERR_DIR_NOT_EMPTY ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-7152')


rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

''",Lukáš Viktora
19024,Virtualbox Installer launches Virtualbox with non-quoted command line - Windows hosts,VirtualBox 6.0.14,defect,2019-10-16T18:16:34Z,2019-10-16T18:16:34Z,2019-10-16T18:16:34Z,"At the end of the Virtualbox installer, the option is presented by default to start the main Virtualbox window. If there is a program called 'program' or 'program.exe' in the C drive root, that program launches instead of the main Virtualbox window.

This issue is ultimately a Windows issue, but the Virtualbox installer is run with admin privileges (asks for UAC elevate during the install, or is started right-click-run-as-admin), and the subsequent main Virtualbox windows is also launched with admin privileges. (Running the main Virtualbox window with admin privileges is required to install the Extension pack, for example.)

If C:\program or C:\program.exe exists, then 'program' is launched with admin privileges at the end of the Virtualbox installer, instead of the main Virtualbox window.

Is it possible to put double quotes around the command line to launch the main Virtualbox window in the MSI installer? Double-quotes will not launch C:\program or C:\program.exe.

See https://forums.virtualbox.org/viewtopic.php?f=6&t=95156",scottgus1
18999,openSUSE install links broken,VirtualBox 6.0.12,defect,2019-10-10T13:29:11Z,2019-10-10T13:29:11Z,2019-10-10T13:29:11Z,"Following the instructions and links on https://www.virtualbox.org/wiki/Linux_Downloads (OpenSUSE) section and it appears the links do not point to the appropriate files on your servers. 

The following terminal output showing errors below:

peter@localhost:~> sudo rpm --import oracle_vbox.asc

[sudo] password for root:
 
peter@localhost:~> wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | rpm --import -
error: -: import read failed(0).

peter@localhost:~> zypper refresh

Root privileges are required to run this command.

peter@localhost:~> sudo zypper refresh

Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date.
                                                    
Repository 'openSUSE-Tumbleweed-Oss' is up to date.
                                                        
Repository 'openSUSE-Tumbleweed-Update' is up to date.
                                                     
Retrieving repository 'VirtualBox for openSUSE 20191004 - x86_64' metadata .........................[error]

Repository 'VirtualBox for openSUSE 20191004 - x86_64' is invalid.

[virtualbox|http://download.virtualbox.org/virtualbox/rpm/opensuse/20191004/x86_64] Valid metadata not found at specified URL

Please check if the URIs defined for this repository are pointing to a valid repository.

Skipping repository 'VirtualBox for openSUSE 20191004 - x86_64' because of the above error.

Some of the repositories have not been refreshed because of an error.

peter@localhost:~> ^C

peter@localhost:~>

Another problem for noobs is the error in instruction missing the ""sudo"" root user authority - easy to correct this one as terminal gives the correct advice. (""instruction to run zypper refresh"")

I cannot find any advice on how the following can be implemented ""Users of openSUSE can add  the openSUSE repo file to /etc/zypp/repos.d/."" How is this done and where? This needs more instruction please.



",ozfossil
18904,Unable to install VirtualBox on Debian 10 Buster,VirtualBox 6.0.10,defect,2019-09-04T11:59:32Z,2019-10-07T14:12:26Z,2019-10-07T14:12:26Z,"Hello.

Today I tried to upgrade my VirtualBox to the latest version.
I powered off my vms and started the update.
Now, all the versions I try to install (testbuilds included) fail on compiling.
The host is older. No Secure Boot, no EFI, just plain old BIOS and MBR.
OS: Debian 10 Buster almost headless (LXDE installed, but it doesn't start on boot and I almost never use it).

Errors on install:
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why

dmesg:
[  360.630491] vboxdrv: loading out-of-tree module taints kernel.
[  360.630672] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[  360.630887] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[  474.533886] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 2230.385340] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4321.446054] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf
[ 4468.860093] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4912.527732] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 4946.446931] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
[ 5099.180792] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf
[ 5657.446078] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab75af
[ 6310.679083] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000751064cb, val ffffffffc0ab792f
[ 7275.790717] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf

I tried the Fedora 29/30 fix, with no luck.

Please help... I'd hate to reinstall and fall back to Stretch.

If you need more details, please let me know.

Thank you.",baltzatu
18930,VirtualBox-5.2.33-133021-Linux_x86.run hangs on lsmod,VirtualBox 5.2.32,defect,2019-09-16T02:36:25Z,2019-09-16T02:36:25Z,2019-09-16T02:36:25Z,"Two copies of lsmod running in D state.  In 5.2.32 I get 100% cpu on modprobe vboxdrv.

Debian Buster 10, Linux honey14 4.19.0-5-686-pae #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) i686 GNU/Linux

Skip to 6:20 to see install still hung, swapping screen(1) to htop(1) and back. https://www.youtube.com/watch?v=ze95E4xIvEk

Thanks!",supaplextor
18891,USB support feature make error in silent installation,VirtualBox 6.0.10,defect,2019-09-02T10:27:44Z,2019-09-02T12:15:02Z,2019-09-02T12:15:02Z,"Hello,

I tried to make silent install via msiexec.exe and with .msi file. So, when I used command ""msiexec /i [path/to/file.msi] /norestart /qn"" nothing happened. I attach log from one of my tries. 

This problem applies to 6.0.10 and 5.x version.

I discovered when I use command ""msiexec.exe /i [path/to/file.msi /norestart /qn -msiparams ADDLOCAL=VBoxApplication,VBoxNetwork,VBoxPython"" (so I'm not installing USB feature) it works and installation can go on. 

This happen's only on machines which hadn't got VB earlier. Machines with older versions can be updated without any problem.    ",Fangier
18773,VirtualBox-6.0-6.0.10_132072_fedora29-1.x86_64 doesn't build kernel modules,VirtualBox 6.0.10,defect,2019-07-18T23:28:37Z,2019-07-18T23:28:37Z,2019-07-18T23:28:37Z,"VirtualBox-6.0-6.0.8_130520_fedora29-1.x86_64 works on fedora 30, but VirtualBox-6.0-6.0.10_132072_fedora29-1.x86_64 simply doesn't build kernel modules, i.e. vboxdrv, etc.

[l@HP14 ~]$ uname -a
Linux HP14.localdomain 5.1.17-300.fc30.x86_64 #1 SMP Wed Jul 10 15:20:27 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[l@HP14 ~]$ rpm -qi VirtualBox-6.0 
Name        : VirtualBox-6.0
Version     : 6.0.10_132072_fedora29
Release     : 1
Architecture: x86_64
Install Date: Fri 19 Jul 2019 07:16:19 AM CST
Group       : Applications/System
Size        : 240110974
License     : GPLv2
Signature   : DSA/SHA1, Fri 12 Jul 2019 09:00:54 PM CST, Key ID 54422a4b98ab5139
Source RPM  : VirtualBox-6.0-6.0.10_132072_fedora29-1.src.rpm
Build Date  : Fri 12 Jul 2019 07:25:46 PM CST
Build Host  : tinderlin4.de.oracle.com
Relocations : (not relocatable)
Vendor      : Oracle Corporation
URL         : http://www.virtualbox.org/
Summary     : Oracle VM VirtualBox
Description :
VirtualBox is a powerful PC virtualization solution allowing
you to run a wide range of PC operating systems on your Linux
system. This includes Windows, Linux, FreeBSD, DOS, OpenBSD
and others. VirtualBox comes with a broad feature set and
excellent performance, making it the premier virtualization
software solution on the market.
[l@HP14 ~]$ modinfo vboxdrv
modinfo: ERROR: Module vboxdrv not found.
[l@HP14 ~]$ 

",trlu
18716,Installation on macOS 10.15 fails,VirtualBox 6.0.8,defect,2019-06-20T10:40:24Z,2019-06-21T23:07:22Z,2019-06-21T23:07:22Z,It is impossible to install VirtualBox to macOS 10.15,tianyl
18492,failure to install completely,VirtualBox 6.0.4,defect,2019-03-12T23:55:27Z,2019-03-13T00:20:57Z,2019-03-13T00:20:57Z,"This is a new Fedora Core system (fc31/rawhide). 

Installation file is: VirtualBox-6.0.5-129304-Linux_amd64.run

Again, the execution of vboxconfig has failed. I know, it's expected. The problem is one that I seem to have seen A LOT. Eventually it gets fixed but it seems to come back (always(?)). Is the fix NOT being propagated to the development tree? Here's the same old message that I've been seeing:

     22    ./tools/objtool/objtool orc generate  --module --no-fp --retpoline /tmp/vbox.0/SUPR0IdcClient.o
     23 /tmp/vbox.0/linux/VBoxPci-linux.c: In function ‘vboxPciFileWrite’:
     24 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration]
     25   375 |     set_fs(get_ds());
     26       |            ^~~~~~
     27       |            get_fs
     28 /tmp/vbox.0/linux/VBoxPci-linux.c:375:12: error: incompatible type for argument 1 of ‘set_fs’
     29   375 |     set_fs(get_ds());
     30       |            ^~~~~~~~
     31       |            |
     32       |            int

Am I doing something wrong?

Best regards,

Obiewan (George)
",George R. Goffe
18377,VB 6.0.2 and 6.0.4 installation fails on macos 10.13.6,VirtualBox 6.0.4,defect,2019-01-28T21:04:06Z,2019-02-19T18:36:43Z,2019-02-19T18:36:43Z,"This is not a security/KEXT problem (directly, at least). 

Trying to install VirtualBox 6.0.2 a week ago and again today with 6.0.4, ran into an issue where the install would get all the way through until the last screen reported Installation Failed. The workaround I found was to do an Advanced install and deselect the FUSE option. Unfortunately, this seems to defeat the point of having updated to the 6. series, other bug fixes, &c aside. 

Attached is the install.log which shows both the 6.0.2 and 6.0.4 install attempts. Both were ultimately successful once I deselected the FUSE option. ",wgd
18145,Installing VB 5.2 and VB 5.1 are not installing on my system.,VirtualBox 5.2.22,defect,2018-11-22T17:39:42Z,2018-11-30T00:43:55Z,2018-11-30T00:43:55Z,I have downloaded and attempted to install both versions on my MacOS X High Sierra 10.13.6.  Each reports that the installation failed and created a crash file. I have sent the crash files attached and will follow with any other information to support this product.,TravelinMan
18125,Extention Pack  Install Error,VirtualBox 5.2.22,defect,2018-11-12T11:21:55Z,2018-11-12T16:25:37Z,2018-11-12T16:25:37Z,"Failed to install the Extension Pack F:/Downloads/Tools/Oracle/Oracle_VM_VirtualBox_Extension_Pack-5.2.22.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-16880' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

",Hercules Oberholzer
18058,Installation fails > Failed to send WATCHDOG=1 notification message: Connection refused,VirtualBox 5.2.20,defect,2018-10-17T18:00:02Z,2018-10-17T18:00:02Z,2018-10-17T18:00:02Z,"Hi,

I'm on openSUSE Tumbleweed.  When I use the '''5.2.20/All distributions''' bits, my desktop has a brain freeze.  I get the errors below.  Using the '''5.2.18/All distributions''' bits does not cause this issue.

When this happens, I cannot properly shutdown my machine.  I have to hit the power button.

I tried it twice.  The second time after a clean boot.

My workaround is to revert to '''5.2.18'''

The strange thing is my laptop is also running Tumbleweed and I had no issue going to 5.2.20.

Let me know what debug information I can provide.  I know this information is a bit .. sparse to act upon.  ;)  

Thx!

{{{
[ 1518.687793] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Connection refused
[ 1588.685640] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[ 1698.682197] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[ 1768.680023] systemd-journald[2372]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
}}}
",Pablo Sanchez
17964,5.2.18 still not availale for RHEL / CentOS 7 -> fixed,VirtualBox 5.2.18,defect,2018-08-31T06:42:40Z,2018-09-12T12:12:23Z,2018-09-12T12:12:23Z,"Hello!

VB 5.2.18 is still not available for the above mentioned platform. Yesterday I tried to update and any update from 5.2.16 -> 5.2.18 was found, so finally I tried a workaround and installed a downloaded RPM manually (from http://download.virtualbox.org/virtualbox/rpm/rhel/7/x86_64/VirtualBox-5.2-5.2.18_124319_el7-1.x86_64.rpm, so it is really existiing and at it right place).

But that's what I still get from yum:
{{{
# yum --disablerepo ""*"" --enablerepo ""virtualbox"" list available
Loaded plugins: aliases, changelog, fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
Available Packages
VirtualBox-4.3.x86_64 4.3.40_110317_el7-1  virtualbox
VirtualBox-5.0.x86_64 5.0.40_115130_el7-1  virtualbox
VirtualBox-5.1.x86_64 5.1.38_122592_el7-1  virtualbox
}}}
Just as a try to get back to the ""standard install"" from REPO:
{{{
# yum reinstall VirtualBox-5.2
Loaded plugins: aliases, changelog, fastestmirror, langpacks, verify
Loading mirror speeds from cached hostfile
 * base: mirror.cuegee.de
 * epel: ftp-stud.hs-esslingen.de
 * extras: mirror.cuegee.de
 * updates: mirror.cuegee.de
Installed package VirtualBox-5.2-5.2.18_124319_el7-1.x86_64 not available.
Error: Nothing to do
}}}
Maybe this is a duplicate of another ticket, but I found any for RHEL/CentOS 7.

With regards.",HRZ d. Universität Bielefeld
17894,Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack not installing,VirtualBox 5.2.16,defect,2018-07-27T05:42:29Z,2018-07-29T13:38:10Z,2018-07-29T13:38:10Z,"Trying to install this Extension Pack on VirtualBox 5.2.16 but getting this error:

Failed to install the Extension Pack C:/Users/Public/Downloads/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-8664' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

OS: Windows 10 Pro
8GB RAM
450GB HDD (243GB free)
Using the Administrator account
Extension pack downloaded and checksum verified


",erch
17864,VirtualBox kernel modules do not build on Fedora 28,VirtualBox 5.2.14,defect,2018-07-11T06:26:13Z,2018-07-24T15:44:33Z,2018-07-24T15:44:33Z,"VirtualBox-5.2-5.2.12_122591_fedora26-1.x86_64

Issuing /sbin/vboxconfig fails.

There's multiple files being complained about containing the line
IPAddressDeny=any (""File /usr/lib/systemd/system/systemd-logind.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling""):

systemd-machined.service
systemd-udevd.service
systemd-journald.service
systemd-logind.service

Finally (and after commenting out IPAddressDeny=any for debugging purposes in named files) it still fails:
{{{
(...)
  gcc -Wp,-MD,/tmp/vbox.0/.SUPR0IdcClient.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClient""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/SUPR0IdcClient.o /tmp/vbox.0/SUPR0IdcClient.c
  gcc -Wp,-MD,/tmp/vbox.0/.SUPR0IdcClientComponent.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClientComponent""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/SUPR0IdcClientComponent.o /tmp/vbox.0/SUPR0IdcClientComponent.c
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPR0IdcClient-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='""SUPR0IdcClient_linux""' -DKBUILD_MODNAME='""vboxpci""' -c -o /tmp/vbox.0/linux/SUPR0IdcClient-linux.o /tmp/vbox.0/linux/SUPR0IdcClient-linux.c
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/SUPR0IdcClientComponent.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/SUPR0IdcClientComponent.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/SUPR0IdcClientComponent.o""; fi; fi;
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/linux/SUPR0IdcClient-linux.o"";
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/SUPR0IdcClient.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/linux/SUPR0IdcClient-linux.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/linux/SUPR0IdcClient-linux.o""; fi; fi;
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/SUPR0IdcClient.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/SUPR0IdcClient.o""; fi; fi;
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/VBoxPci.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/VBoxPci.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/VBoxPci.o""; fi; fi;
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:80,
                 from /tmp/vbox.0/linux/VBoxPci-linux.c:31:
In function ‘strncpy’,
    inlined from ‘vboxPciLinuxDevDetachHostDriver’ at /tmp/vbox.0/linux/VBoxPci-linux.c:436:9,
    inlined from ‘vboxPciOsDevInit’ at /tmp/vbox.0/linux/VBoxPci-linux.c:645:14:
./include/linux/string.h:246:9: warning: ‘__builtin_strncpy’ specified bound 64 equals destination size [-Wstringop-truncation]
  return __builtin_strncpy(p, q, size);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline ""/tmp/vbox.0/linux/VBoxPci-linux.o"";
  if [ ""-pg"" = ""-pg"" ]; then if [ /tmp/vbox.0/linux/VBoxPci-linux.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/tmp/vbox.0/linux/VBoxPci-linux.o""; fi; fi;
  ld -m elf_x86_64 -z max-page-size=0x200000   -r -o /tmp/vbox.0/vboxpci.o /tmp/vbox.0/linux/VBoxPci-linux.o /tmp/vbox.0/VBoxPci.o /tmp/vbox.0/SUPR0IdcClient.o /tmp/vbox.0/SUPR0IdcClientComponent.o /tmp/vbox.0/linux/SUPR0IdcClient-linux.o 
make -f ./scripts/Makefile.modpost
  find /tmp/vbox.0/.tmp_versions -name '*.mod' | xargs -r grep -h '\.ko$' | sort -u | sed 's/\.ko$/.o/' | scripts/mod/modpost   -i ./Module.symvers -I /tmp/vbox.0/Module.symvers  -o /tmp/vbox.0/Module.symvers -S  -w  -s -T -
  gcc -Wp,-MD,/tmp/vbox.0/.vboxpci.mod.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -DCONFIG_CC_STACKPROTECTOR -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-pie -I/lib/modules/4.17.3-200.fc28.x86_64/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DRT_ARCH_AMD64  -DKBUILD_BASENAME='""vboxpci.mod""' -DKBUILD_MODNAME='""vboxpci""' -DMODULE  -c -o /tmp/vbox.0/vboxpci.mod.o /tmp/vbox.0/vboxpci.mod.c
  ld -r -m elf_x86_64 -z max-page-size=0x200000 -T ./scripts/module-common.lds --build-id  -o /tmp/vbox.0/vboxpci.ko /tmp/vbox.0/vboxpci.o /tmp/vbox.0/vboxpci.mod.o ;  true
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.17.3-200.fc28.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 ""  ERROR: Kernel configuration is invalid."";		\
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";	\
echo >&2 ;							\
/bin/false)
mkdir -p /lib/modules/4.17.3-200.fc28.x86_64/misc
make -f ./scripts/Makefile.modinst
  mkdir -p /lib/modules/4.17.3-200.fc28.x86_64/misc ; cp /tmp/vbox.0/vboxpci.ko /lib/modules/4.17.3-200.fc28.x86_64/misc ; true /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko ; scripts/sign-file ""sha256"" ""certs/signing_key.pem"" certs/signing_key.x509 /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko || true && true /lib/modules/4.17.3-200.fc28.x86_64/misc/vboxpci.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory
  /bin/sh ./scripts/depmod.sh /sbin/depmod 4.17.3-200.fc28.x86_64 """"
}}}
After updating to VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64 there's an empty vbox-install.log after issuing /sbin/vboxconfig, vbox-setup.log shows:

Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module.
Building the PCI pass-through module.

No information on why it failed to build.",ThygWedd
17532,virtualbox-5.2 depends on libfontconfig1 (>= 2.9.0); (Ubuntu 14.04 LTS),VirtualBox 5.2.6,defect,2018-02-07T21:11:20Z,2018-02-07T21:11:20Z,2018-02-07T21:11:20Z,"install of virtualbox-5.2_5.2.6-120293~Ubuntu~trusty_amd64 fails on fully upgraded 14.04 LTS[[BR]]
[[BR]] uname -a[[BR]]
Linux vm530.loc 3.2.0-68-generic #102-Ubuntu SMP Tue Aug 12 22:02:15 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux[[BR]]

[[BR]]
See attached installer log, summary follows:[[BR]]
[[BR]]
The following packages have unmet dependencies:[[BR]]
 virtualbox-5.2 : Depends: libfontconfig1 (>= 2.9.0) but[[BR]]
2.8.0-3ubuntu9.2 is to be installed[[BR]]
                  Recommends: libsdl-ttf2.0-0 but it is not going to be installed[[BR]]

E: Unable to correct problems, you have held broken packages.",AndreasFG
17495,Échec de l'installation de l'extension,VirtualBox 5.2.4,defect,2018-01-22T21:49:35Z,2018-01-23T12:45:31Z,2018-01-23T12:45:31Z,"Échec de l'installation de l'extension C:/Users/moimeme
/.VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-5.2.6.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-32428' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


VBoxExtPackHelperApp.exe: error: Failed to delete the temporary extension pack directory: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-32428')


rcExit=1.

Code d'erreur : E_FAIL (0x80004005)
Composant : ExtPackManagerWrap
Interface : IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

",dedalios
17478,ExtensionPack Installation Error,VirtualBox 5.2.6,defect,2018-01-18T15:00:51Z,2018-01-18T18:06:15Z,2018-01-18T18:06:15Z,"Не удалось установить плагин C:/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.2.6-120293.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-1048' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')

rcExit=1.

Код ошибки: E_FAIL (0x80004005)
Компонент: ExtPackManagerWrap
Интерфейс: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

",zats
17417,VirtualBox crashes,VirtualBox 5.2.4,defect,2018-01-04T14:32:44Z,2018-01-05T08:37:09Z,2018-01-05T08:37:09Z,"When I craete a new SATA-HD, then the Client crashes if I create with right mouse button on SATA.

There runs a windows 2012 r2 server.

",rhino
16771,Qubes install ISO fails to run,VirtualBox 5.1.22,defect,2017-05-19T14:02:06Z,2017-12-18T22:58:20Z,2017-12-18T22:58:20Z,Am attempting to run install Qubes OS from ISO [https://www.qubes-os.org/downloads/] on 64 bit host using 64 bit Virtualbox and 64 bit VM environment. Was able successfully install Qubes on 1 of 3 different hosts: Dell Latitude E5420. Failed on Surface Pro 4. Also failed in Lenovo Think Center.,mutsuura
17378,/sbin/vboxconfig fails during upgrade of Vbox to 5.2.2,VirtualBox 5.2.2,defect,2017-12-18T19:52:19Z,2017-12-18T19:52:19Z,2017-12-18T19:52:19Z,"Current system is Fedora 28 x86_64 (Rawhide).

Install of VirtualBox released version fails during config. The developer version fails as well... with the same error message (see inclosed install log).",George R. Goffe
16333,"""The installer has detected running Virtual Machines"" message is confusing",VirtualBox 5.1.12,defect,2016-12-28T09:24:29Z,2017-12-13T10:41:25Z,2017-12-13T10:41:25Z,"This error message is shown if I happen to have the VirtualBox UI running when attempting to update VB on a Mac - even if all VMs have been shut down.

As ""klaus"" mentioned in #12392 the error message is confusing.",vpvainio
17202,Please add Ubuntu 17.10 (artful) Support to the PPA,VirtualBox 5.2.0,defect,2017-10-22T22:53:00Z,2017-12-04T13:43:20Z,2017-12-04T13:43:20Z,Please add Ubuntu 17.10 (artful) Support to the PPA,Neti_Netwalker
17344,VirtualBox 5.2.x installer: ProductID in MSI File and ProductID on installed system do not match,VirtualBox 5.2.0,defect,2017-12-04T13:22:11Z,2017-12-04T13:22:11Z,2017-12-04T13:22:11Z,"With the installation packages for VirtualBox 5.2.x on Windows the ProductCode that can be read from the MSI files, is not the ProductCode that is found on the system after Installation.

E.g.: 
||=Version=||=MSI value=||=""real"" value=||
|| 5.2.0-r118431 ||{1E6A323C-1BE9-49B6-8FDC-107307DBC6CE}||{9df09fcf-7f55-402e-aab8-67ffba56ea3b}||
|| 5.2.2-r119230 ||{9F5D10F9-A372-4B1E-BEB3-001B47E0C325}||{b4758fb7-76a2-4391-aca1-6bffcfc90c40}||
|| 5.2.3-119337  ||{8B91C2E7-6A86-43AE-8797-48A61E6C59AB}||{9988FC09-BE58-4DF3-9943-AC14E7A0882C}||

This breaks the common procedure ind automated software deployment:
1. extract ProductID from MSI
2. install MSI
3. check whether MSI for ProductID is installed",WRatzka
17258,vbox kernel modules should be signed for OL7,VirtualBox 5.2.0,defect,2017-11-09T17:47:36Z,2017-11-09T17:47:36Z,2017-11-09T17:47:36Z,"For OL7 running on a server with Secure Boot installation of VirtualBox will fail:

''fslin1:/root # yum install VirtualBox-5.1
...
Running transaction
  Installing : VirtualBox-5.1-5.1.30_118389_el7-1.x86_64                                                                              1/1

Creating group 'vboxusers'. VM users must be member of that group!

vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
  Verifying  : VirtualBox-5.1-5.1.30_118389_el7-1.x86_64                                                                              1/1

Installed:
  VirtualBox-5.1.x86_64 0:5.1.30_118389_el7-1

Complete!''

The reason for failure is the absence of module signature:

''fslin1:/root # modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Required key not available''

And the module is not signed:

''fslin1:/root # cd /lib/modules/`uname -r`/misc
fslin1:/lib/modules/4.1.12-94.3.9.el7uek.x86_64/misc # ls
vboxdrv.ko  vboxnetadp.ko  vboxnetflt.ko  vboxpci.ko
fslin1:/lib/modules/4.1.12-94.3.9.el7uek.x86_64/misc # modinfo vboxdrv.ko
filename:       /lib/modules/4.1.12-94.3.9.el7uek.x86_64/misc/vboxdrv.ko
version:        5.1.30 r118389 (0x002a0000)
license:        GPL
description:    Oracle VM VirtualBox Support Driver
author:         Oracle Corporation
srcversion:     8FBD7594E804ED618ED1A07
depends:
vermagic:       4.1.12-94.3.9.el7uek.x86_64 SMP mod_unload modversions
parm:           force_async_tsc:force the asynchronous TSC mode (int)''

There is no ''''signer'''', ''''sig_key'''' & ''''sig_hashalgo'''' in the above. Would you be able to sign VBox modules accordingly?",dbv
17231,Installing Grisoft's AVG into Win 7 SP1,VirtualBox 5.1.30,defect,2017-10-31T20:00:27Z,2017-10-31T21:01:12Z,2017-10-31T21:01:12Z,Nearly installed (97%) and it stopped with your 'Guru Meditation' screen,Lofty
17210,Updated to VB 5.2.0; install failed,VirtualBox 5.2.0,defect,2017-10-25T22:08:28Z,2017-10-25T22:08:28Z,2017-10-25T22:08:28Z,"I have tried to upgrade VirtualBox to 5.2.0 but the installation failed. Then I tried the ""latest
test (dev?) build (VirtualBox-5.2.1-118468-Linux_amd64.run) but the installation has again failed.

I must be doing something wrong since I am almost continually getting this error (see the enclosed log).

Am I doing something wrong? The error log suggests various versions of ""libelf"" but Fedora 28 (rawhide) doesn't
have any of these packages and as far as I know, never has.

Any help you can give me about this problem would be greatly appreciated.

Regards,

George...
",George R. Goffe
17120,Installation of 5.1 & 5.2 Beta failing for Windows 10 Pro,VirtualBox 5.1.28,defect,2017-09-29T00:07:54Z,2017-09-29T02:07:06Z,2017-09-29T02:07:06Z,"In multiple attempts to install on Windows 10 Pro 64 bit v1703 build 15063.608, VirtualBox fails to install. I've tried VirtualBox-5.1.24-117012-Win.exe, VirtualBox-5.1.28-117968-Win.exe, VirtualBox-5.1.29-118065-Win.exe and VirtualBox-5.2.0_BETA2-117563-Win.exe. I've attached a log from running from the command line as an admin using the --logging param. Any help would be appreciated.",ElysiumTacos
10081,"Updating damages existing ""pinned"" shortcuts",VirtualBox 4.1.8,defect,2011-12-24T21:47:27Z,2017-07-28T12:35:00Z,2017-07-28T12:35:00Z,"When you pin the shortcut to VirtualBox to the Start Menu or Taskbar in Windows 7, and then update VirtualBox (Min to Min[4.1.0 to 4.1.2], or Major to Major[3.x to 4.x]) the shortcut appears to be deleted, leaving a broken pinned shortcut that needs to be deleted, and then recreated.

No other software I have pinned appears to have this problem when performing updates.

Has happened with every version of VirtualBox I've had installed, starting around 3.1.8, possibly earlier.

Expected behavior should let existing shortcuts, pinned and otherwise, should still be functional after simple updates.",kookyman
16942,removing the deb package should also remove the systemd service,VirtualBox 5.1.24,defect,2017-07-25T06:44:32Z,2017-07-25T06:44:32Z,2017-07-25T06:44:32Z,"As said, a lot of people remove virtualbox-4.2 virtualbox-5.0 virtualbox-5.1, and they try to install the Ubuntu version.

The problem is that without a --purge, your virtualbox package doesn't remove the systemd services, leading to install errors
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1705940

DKMS: install completed.
Configurando virtualbox (5.0.40-dfsg-0ubuntu1.16.04.1) ...
insserv: script virtualbox: service vboxdrv already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error al procesar el paquete virtualbox (--configure):
 el subproceso instalado el script post-installation devolvió el código de salida de error 1
dpkg: problemas de dependencias impiden la configuración de virtualbox-qt:
 virtualbox-qt depende de virtualbox (= 5.0.40-dfsg-0ubuntu1.16.04.1); sin embargo:
 El paquete `virtualbox' no está configurado todavía.
  El paquete `virtualbox-4.2' que provee virtualbox no está instalado.


so, please remove your files when virtualbox is removed :)

thanks
",LocutusOfBorg
16909,kali linux is not installing,VirtualBox 5.1.22,defect,2017-07-18T08:26:15Z,2017-07-24T09:47:57Z,2017-07-24T09:47:57Z,i choosed the version debian 32bit and then i started the machine and clicked Graphical install after this all i see its a black screen,LazyDanu
16600,Strange icon under Fedora 25 KDE,VirtualBox 5.1.18,defect,2017-03-23T19:53:37Z,2017-07-16T09:41:40Z,2017-07-16T09:41:40Z,"Hi,

Under Fedora 21 and VirtualBox-5.0-5.0.36_114008_fedora18-1.x86_64.rpm I have nice KDE icon.

Now I'm trying to recreate look and feen under Fedora 25.
Instead of ""blue box"" I'm getting black square with green dots.

Screenshoots attached

Regards,
Mike",Mike446
16365,Error after clean Install VirtualBox 5.1.12 on Windows 7 64 bit.,VirtualBox 5.1.12,defect,2017-01-07T20:40:35Z,2017-03-17T10:14:38Z,2017-03-17T10:14:38Z,"Hello, I'm on Windows 7 64 bit.

After try to upgrade VirtualBox from 5.0.x to 5.1.12, I received following error:

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_INVALIDVALUE.

Error Code: 
REGDB_E_INVALIDVALUE (0x80040153)
Component: 
VirtualBoxClientWrap
Interface: 
IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

No one of any version the last stable or the previous one is not working, after install I received same errors. 

Tried to clean registry manually and via software, reinstalled any component of Virtualbox, no one was not help. ",aidjek
16456,"Windows 10: Installation hangs at ""NetLwf will be installed ...""",VirtualBox 5.1.14,defect,2017-02-05T21:22:34Z,2017-02-05T21:22:34Z,2017-02-05T21:22:34Z,"I tried to install VirtualBox 5.1.14 on the weekend on my computer (Windows 10 Version 1607).
Unfortunately the installation hangs at a certain point.
The log shows the following information:

{{{
InstallNetLwf: Installing NetLwf
NetLwf is not installed currently
NetLwf will be installed ...
Installing 1 INF files ...
}}}


I used a Windows 10 image to restore my computer and tried the installation several times, but it never worked.

If I performe the installation without the VBoxNetwork-features the installation works.

It would be really great if somebody could help me.
If you need any more logs just tell me.",Rafter
16433,The installer won't work error 2755 and when I can get it installed another problem happens.,VirtualBox 5.1.14,defect,2017-01-30T04:26:09Z,2017-01-30T04:26:09Z,2017-01-30T04:26:09Z,"The problem when I got virtualbox installed, it would tell me an error that it couldn't acquire the COM object. I have checked to make sore there are no corrupt registry files, I've deleted some of the old virtualbox files on my system, I even deleted the installer folder in windows32, along with deleting and removing virtualbox and reinstalling. I haven't been able to fix this problem, it was all working fine about a month ago and then one day when I decided to use VBox it just stopped working saying that it can't acquire the COM object ",Kingy
16312,RPM upgraid fails when VBoxSVC --auto-shutdown is running,VirtualBox 5.1.12,defect,2016-12-22T04:44:18Z,2016-12-22T04:44:18Z,2016-12-22T04:44:18Z,"When trying to upgrate VirtualBox with yum/rpm, the first attempt fails if VBoxSvc --auto-shutdown is running.  The preinstall script shuts down services, but only waits 1 second for VBoxSVC to terminate, when it takes closer to 10 (which is documented in the error message, but the script doesn't take into account!).  Thus the upgrade fails, but works if you try again after the service terminates.

The solution is to chane the 'sleep 1' on line 103 of /usr/lib/virtualbox/routines.sh to 'sleep 10' (or do a loop checking ever second for 10 seconds, or something like that).

{{{
# yum update
Loaded plugins: aliases, auto-update-debuginfo, changelog, fastestmirror, filter-data, keys, list-data, merge-conf,
              : priorities, ps, remove-with-leaves, rpm-warm-cache, show-leaves, verify
Loading mirror speeds from cached hostfile
 * base: mirrors.centos.webair.com
 * elrepo: mirrors.evowise.com
 * epel: mirror.symnds.com
 * extras: mirror.umd.edu
 * nux-dextop: mirror.li.nux.ro
 * updates: mirror.datto.com
Skipping filters plugin, no data
Resolving Dependencies
Skipping filters plugin, no data
--> Running transaction check
---> Package VirtualBox-5.1.x86_64 0:5.1.10_112026_el7-1 will be updated
---> Package VirtualBox-5.1.x86_64 0:5.1.12_112440_el7-1 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================
 Package                     Arch                Version                             Repository               Size
===================================================================================================================
Updating:
 VirtualBox-5.1              x86_64              5.1.12_112440_el7-1                 virtualbox               75 M

Transaction Summary
===================================================================================================================
Upgrade  1 Package

Total download size: 75 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for virtualbox
VirtualBox-5.1-5.1.12_112440_el7-1.x86_64.rpm                                               |  75 MB  00:00:05     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
A copy of VirtualBox is currently running.  Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox (in particular
the VBoxSVC daemon) to finish running.
error: %pre(VirtualBox-5.1-5.1.12_112440_el7-1.x86_64) scriptlet failed, exit status 1
Error in PREIN scriptlet in rpm package VirtualBox-5.1-5.1.12_112440_el7-1.x86_64
  Verifying  : VirtualBox-5.1-5.1.12_112440_el7-1.x86_64                                                       1/2 
VirtualBox-5.1-5.1.10_112026_el7-1.x86_64 was supposed to be removed but is not!
  Verifying  : VirtualBox-5.1-5.1.10_112026_el7-1.x86_64                                                       2/2 

Failed:
  VirtualBox-5.1.x86_64 0:5.1.10_112026_el7-1              VirtualBox-5.1.x86_64 0:5.1.12_112440_el7-1             

Complete!
}}}
",Joshua Megerman
16258,Install fails v5.1.10 - Linux 64 - Ubuntu,VirtualBox 5.1.10,defect,2016-12-02T10:42:58Z,2016-12-05T14:55:33Z,2016-12-05T14:55:33Z,"I downloaded the full installer for VirtuabBox, debian distro Linux 64bit.

The package manager reports an ""unsatisfiable Dependency"" on QT Core:

{{{
Error: Dependency is not satisfiable: libqt5core5a (>=5.6.0-beta)
}}}


I have scanned the debian repositories.  Sure enough there is No Stable package available to support this installer package.

I don't know what using the in-test version might be on my other stable system programs.

{{{
Package libqt5core5a

    wheezy-backports (libs): Qt 5 core module
    5.3.2+dfsg-4+deb8u1~bpo70+1: amd64
    jessie (stable) (libs): Qt 5 core module
    5.3.2+dfsg-4+deb8u1: amd64
    stretch (testing) (libs): Qt 5 core module
    5.7.1~20161021+dfsg-6: amd64
    sid (unstable) (libs): Qt 5 core module
    5.7.1~20161021+dfsg-6: amd64
}}}

I suggest it is infeasible to use this version of virtualbox on a stable system.  It might be OK for a test system or development system.  I had a mismatch of GTK versions one time and it caused all kinds of chaos with the GUI.  I don't recommend the experience.",Will
16003,"Remove the ""Start after installation"" option from Windows installer",VirtualBox 5.1.6,defect,2016-09-29T07:16:21Z,2016-10-07T15:30:29Z,2016-10-07T15:30:29Z,"It is becoming increasingly clearer that with Windows installers you have to install !VirtualBox with the ""Run as Administrator"" option after right-clicking on the installer. It is the only way to make sure that the drivers are installed as they should and are not rejected (silently sometimes) by Windows and UAC.

The problem is that if a simple user uses that tool, at the end of the installation when the installer offers to launch !VirtualBox, then !VirtualBox runs under the context not of the user that did the installation, but under the Administrator context. So if a user starts immediately to use !VirtualBox and creates a new VM, that VM won't be there next time the user re-launches !VirtualBox. It's going to be in the Administrator's account!

Solution: remove the ""Start after installation"" option at the end of the installation. The installer finishes and the user launches !VirtualBox under their own user context, as they would do it normally every other day.

PS. It doesn't have to be a simple user, driver installation fails sometimes even with an administrator user, so the ""Run as Administrator"" is becoming mandatory. Simply in that case the issue does not manifest itself.",Socratis
15882,Installer for VBox 5.1.4 doesn't honor non C: locations when creating shortcut,VirtualBox 5.1.4,defect,2016-09-03T17:18:27Z,2016-09-03T17:18:27Z,2016-09-03T17:18:27Z,"I install VirtualBox in G:\Program Files\Oracle\VirtualBox, not in the usual location, C:\Program Files\Oracle\VirtualBox. The ""Oracle VM VirtualBox"" shortcut is created to point to the nonexisting C:\Program Files\Oracle\VirtualBox\VirtualBox.exe, not G:\Program Files\Oracle\VirtualBox\VirtualBox.exe as I would prefer. This is new to 5.1.4. Manual intervention is required after installation. Note, this happened when upgrading from 5.1.2. Maybe the bug doesn't happen on a clean install.",trondfsi
15543,install path environment var not set,VirtualBox 5.0.22,defect,2016-06-22T14:56:42Z,2016-06-22T15:03:11Z,2016-06-22T15:03:11Z,"The VBOX_MSI_INSTALL_PATH environment variable is not set by the 5.0.22 installer.

Tried uninstalling/re-installing, running as administrator, rebooting. nothing helped

Uninstalling and reverting to the 5.0.20 installer set the env var as expected

Installation was on a brand new Windows 10 machine (build 10586.164)",dansgeo
14546,Can't install VirtualBox on Windows 10,VirtualBox 5.0.2,defect,2015-09-05T20:27:46Z,2016-02-28T09:08:32Z,2016-02-28T09:08:32Z,"I am not able to install VirtualBox nor 5.0.2 or 5.0.x revision 102467 on my Windows 10 laptop. Previous I updated Windows 8.1 to Windows 10 and all works fine. Now after clean install of Windows 10 i can't use VirtualBox again. I think problem is related to VirtualBox network drivers. I enclose a log file where there is some info:

InstallNetLwf: Installing NetLwf
NetLwf is not installed currently
NetLwf will be installed ...
Installing 1 INF files ...
Installing INF file ""C:\Program Files\Oracle\VirtualBox\drivers\network\netlwf\VBoxNetLwf.inf"" ...
Install failed, hr (0x80070005)
VBoxNetCfgWinInstallComponent failed, hr (0x80070005)
Installation failed, rolling back installation set ...
",sal3tra
15089,Unable to setup base OS using virtual box,VirtualBox 4.3.28,defect,2016-01-28T23:40:50Z,2016-02-10T08:50:11Z,2016-02-10T08:50:11Z,"Hi Team,

I tried Oracle Virtual Box 5.12 and 4.2.28 but unable to start the ubuntu VM.
Seeing below error every time. I got my system reimaged with client Windows 7
{{{
00:00:01.107602          VDInit finished
00:00:01.107602          Loading settings file ""C:\Users\a371216\.docker\machine\machines\default\default\default.vbox"" with version ""1.14-windows""
00:00:01.107602          Loading settings file ""C:\Users\a371216\VirtualBox VMs\manualUbuntu64\manualUbuntu64.vbox"" with version ""1.14-windows""
00:01:42.302389          ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false
00:01:42.349395          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
}}}",naveenlekhwar
15126,"""X"" in corner does not close dialog box.",VirtualBox 5.0.14,defect,2016-02-08T14:44:40Z,2016-02-08T14:44:40Z,2016-02-08T14:44:40Z,"The ""X"" in the upper right corner does not close the dialog box to close it you must chose the ""OK"" button.",SWillis
15007,installing virtualbox on windows 10 version 1511 throws VERR_SHARING_VIOLATION,VirtualBox 5.0.12,defect,2016-01-05T04:59:25Z,2016-01-05T14:20:07Z,2016-01-05T14:20:07Z,"so yea, just downloaded the latest version of virtualbox, and tried installing it, got the installer to run correctly only to try restarting the installer process from process explorer (due to installer not doing anything at all possibly due to windows issue yet to be discovered or pinpointed) and now upon the thing restarting, it throws that error, and no matter how many times I redownload the installer, it throws this error every time....even if I delete the file from all existance and redownload it, it still throws said error.",mmd123
11589,Don't create a desktop shortcut by default,VirtualBox 4.2.8,defect,2013-03-13T19:10:55Z,2015-10-21T13:03:30Z,2015-10-21T13:03:30Z,"Please note that Microsoft specifically mentions this point in the Windows Customer Experience Guidelines for developers:

QUOTE BEGIN
If you do only one thing...
Don't abuse the desktop—keep users in control. If your target users are likely to use your program frequently, provide an option during setup to put a shortcut on the desktop, unselected by default.
QUOTE END

http://msdn.microsoft.com/en-us/library/windows/desktop/aa511450.aspx

While you're at it, remove the quick launch shortcut default as well.",gencha
10436,"Virtual Box install fails (rollback, MSI code 1603) on Windows 7 64 host",VirtualBox 4.1.12,defect,2012-04-13T17:57:17Z,2015-10-15T13:42:19Z,2015-10-15T13:42:19Z,"I have read the posts, howtos and such and still cannot determine why my install is failing (rollback initiated during install) MSI error code 1603. 

Host: Windows 7 64 bit

Tried command line install without USB drivers. Still fails.

The only driver log created was setupapi.app.log. It and the install log are attached.

Any help would be greatly appreciated.",bobheck
14603,"Installation fails on Windows 7 trying to access ""quick launch"" folder",VirtualBox 5.0.4,defect,2015-09-16T23:55:50Z,2015-09-16T23:55:50Z,2015-09-16T23:55:50Z,"Our company employs a domain policy to direct each user's ""Application Data"" folder to a network share. Attempting to install VirtualBox 5.0.4 fails when attempting to access the ""Microsoft/Internet Explorer/Quick Launch"" sub-folder of ""Application Data"" because it resets network connections (thereby cutting off access to network shares) prior to accessing that folder. Upon failing to access the quick launch folder the installation fails (giving the user no option to continue even though the problem is minor) and rolls back the installation, leaving the existing host-only ethernet adapter drivers in a corrupted state.

I have tried the following steps to work around this problem:

1. Tell the installer not to add VirtualBox to the quick launch or start menu. (The installer ignores the user's request and still tries to access the quick launch folder)
2. Tell the installer not to install the network device drivers. (The installer resets network connections even though this is unnecessary)

Possible solutions to fix this problem:

1. Add VirtualBox to the Quick Launch and Start Menu (if the user requests it) *before* resetting network connections; or
2. After installing the network device drivers, ensure that network connections are properly re-established before attempting to access the Quick Launch and Start Menu folders; or
3. Give the user the option of continuing with the installation even if adding VirtualBox to the Quick Launch and Start Menu folders fails.

The same problem occurs when attempting to upgrade to version 4.3.30. I would really like to upgrade to a more recent version of VirtualBox (I'm stuck on 4.3.26) but I can't because I simply can't install any newer version.
",srgerg
14281,Mac OS X Installer can't install because VirtualBox is running,VirtualBox 4.3.30,defect,2015-07-15T11:22:34Z,2015-08-19T15:19:45Z,2015-08-19T15:19:45Z,"In trying to upgrade Boot2Docker this morning, I ran into an issue where the installer would not proceed as it claimed VirtualBox was still running. I then tried to install VirtualBox 4.3.30, upgrading from 4.3.28, and the VirtualBox installer was gated on the same issue asking me to stop all VMs and processes. A quick process check showed the following:

{{{
mbp:~ me$ ps aux | grep VB
me             1135   0.2  0.0  2451240   7088   ??  S     7:10AM   0:00.05 /Applications/VirtualBox.app/Contents/MacOS/VBoxXPCOMIPCD
me             1137   0.2  0.1  2532164  11260   ??  S     7:10AM   0:00.13 /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC --auto-shutdown
me             1147   0.0  0.0  2450180    684 s000  S+    7:10AM   0:00.00 grep VB
}}}

If I kill the processes using kill -9, the installer then works. I am running on Mac OS X 10.10.4. I am not sure if this is an issue with the 4.3.30 installer or if it's an issue with 4.3.28 with lingering processes?",damnhandy
14138,Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf',VirtualBox 4.3.28,defect,2015-05-19T18:16:23Z,2015-06-18T18:24:59Z,2015-06-18T18:24:59Z,"I get this error installing on Windows 8.1:


{{{
DIFXAPP: INFO:   VBoxUSBMon.inf: checking signature with catalog 'C:\Program Files\Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.cat' ...
DIFXAPP: ERROR:  Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf' ('C:\Program Files\Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.inf'). (Error code 0x800B0003: The form specified for the subject is not one supported or known by the specified trust provider.)

}}}

",Mark Richman
14196,Install fails with fatal error but no other message,VirtualBox 4.3.28,defect,2015-06-15T21:30:47Z,2015-06-16T17:31:04Z,2015-06-16T17:31:04Z,"It gets most of the way through the install then it rolls back and says there was a fatal error. But, it never says what the error was. I've collected an msiexe /lx install log that I'm attaching. It's the only info I have right now. I'm running Windows 7 as the host.",Gungwald
3654,Bridged Networking does not find any adapters,VirtualBox 2.2.0,defect,2009-04-08T17:08:02Z,2015-06-10T20:15:06Z,2015-06-10T20:15:06Z,"When configuring a guest in version 2.2.0 under Windows Vista (I have x64, some others have reported with x32), under the bridged network configuration, the only selection for ""Bridged Network Adapter"" that I can choose is ""Not selected.""  This means that I cannot configure the network to work in bridged mode.  This has been reported on the forum: [http://forums.virtualbox.org/viewtopic.php?f=6&t=16202&start=0].",brigad@rpi.edu
4956,Installer fails with error 1603,VirtualBox 3.0.6,defect,2009-09-11T16:49:56Z,2015-06-05T09:14:31Z,2015-06-05T09:14:31Z,"Trying to install version 3.0.6 on Windows Vista.
After all the confirmation the installer starts. But after seconds the scrollbare runs back and an error is showed:

Virtual Box Installer
Installation of MSI failed
Error: 1603

",Nagi
14164,Problem with installing VirtualBox on Windows 7,VirtualBox 4.3.28,defect,2015-06-02T08:04:01Z,2015-06-02T08:04:01Z,2015-06-02T08:04:01Z,"When I run the installer on my maschine (Windows 7 Enterprise), the installer seams to do what it is supposed to do. But when I afterwards try to start VirtualBox, the main windows of the programm is shown and almost immediately, it crushes down.
Please find the picture with the error screen and also the error text cutted out into a text file attached.
Solution for the problem is the following procedure:
The installer created a folder named "".VirtualBox"" under my user folder here on windows. As I compared some other installations from other maschines, in my new installation was one file missing named ""vbox-ssl-cacertificate.crt"". After adding this particular file to that folder, VirtualBox was able do run again.
Question: What is the problem for the installer that it fails to create this file during the installation routine?
I even ran the installation routine as admin and it didn't make any difference.
",Jonas Bassl
14115,4.3.28 installation failed,VirtualBox 4.3.28,defect,2015-05-14T19:55:06Z,2015-05-21T09:05:49Z,2015-05-21T09:05:49Z,"Hi,
I tried to install 4.3.28 but I had a bluescreen during installation saying DPC_WATCHDOG_VIOLATION.
I tried after to install the 4.3.26 again and it failed.
I tried to do all sorts of fix found on your forums but nothing worked.
I link to this bug report a log of the last installation I tried",Josk
7040,"Windows 7 host, VBox 3.2.4 cannot do bridged networking",VirtualBox 3.2.4,defect,2010-06-21T23:21:05Z,2015-05-19T17:18:58Z,2015-05-19T17:18:58Z,"Upgraded from 3.1.4 to 3.2.4 on a Windows 7 Ultimate 64-bit host

Existing VMs would not start (E_FAIL). Checking the settings highlighted a problem with the network adapter.

The VMs all use bridged networking. The dropdown for the host network adapter to bridge was empty, and nothing could be selected.

Tried creating a new VM in 3.2.4, same problem - can't set network adapter to bridged networking, because I can't select a host adapter to bridge.

Downgrade to 3.1.8 - everything works as before.
",Mike Benson
11712,Install Makes Windows 8 Host Boot Fail,VirtualBox 4.2.12,defect,2013-04-15T00:12:55Z,2015-04-09T12:31:56Z,2015-04-09T12:31:56Z,"This is bug: When I run the Virtualbox 4.2.12 install with its default settings, Windows will not finish booting on the next start up. I'll leave it try to boot for a while, kill the power, start it up and repeat until the Windows 8 auto recovery kicks in. Windows 8 will do a system restore t the point just before installing Virtualbox. Virtualbox will no longer be installed and the system will reboot  and operate normally. I ran the whole install Virtualbox, system repair cycle several times to confirm nothing else I did was tied to the problem. I eventually installed Virtualbox by not installing anything that looked like it was related to networking. With that install configuration Windows booted properly several times. I ran several clients in Virtualbox and they all were able to connect to the internet.

Machine Information: I am running Windows 8 x64 as my host. It is not an upgrade. I did a fresh install from CD, though I have since installed numerous other items. The laptop runs an AMD A8-4500, has 16 GB of RAM, and a sizable SSD. Because I develop for windows phone, I have hyper-v enabled and it has several network adapters setup. I use Virtualbox because hyper-v is inadequate for some things, so I have to have them both concurrently. I had previously used them concurrently without issue, but then I kept running into wireless networking issues (no internet access over WI-FI) definitively caused by Virtualbox somehow. As such I had no choice but to uninstall Virtualbox (though Windows seemed not to remove all of the settings related to Virtualbox's network adapter) and to start using hyper-v in its place.  Hyper-v was inadequate in some regards, so I installed Virtualbox 4.2.12 and got the above bug.

If I can help fix this issue or provide any useful information, even if it means retesting that whole mess installing nightly builds or anything else, please let me know as I am more than happy to help! I can be contacted directly if needed at [reportedbyname] {A T} [gmail address]",jmessenger235
13713,VirtualBox fails to create bridged or host-only network adapter on some Win7 desktops - Error FAIL (0x80004005),VirtualBox 4.3.20,defect,2014-12-23T16:09:02Z,2015-03-25T14:34:59Z,2015-03-25T14:34:59Z,"Detected in:  VirtualBox-4.3.20-96997-Win.exe

On some of our Win7 desktops with Broadcomm gigabit 57xx ethernet adapter, When installing or configuring VirtualBox, it returns error FAIL x8004005 and fails to create the virtual ""host-only"" and/or bridged network adapter.  Switching to NAT also fails with a similar network-related error (cannot find network adapter for PXE boot or similar). 

This error is occurring only on some (~10%) of our Qa desktops, but all have identical hardware and configurations running similar recent Win 7 builds. 

Note that this error was also occurring also under Vbox 3.18 and VBox 3.16, for these same desktops, and is similar to many open defects already logged with oracle. 

We have tried install/uninstall numerous versions of Virtual Box, as local and domain Admin, with AVG antivirus disabled, as well as uninstall + manual registry and driver-file cleaning as per FAQs, + system restores, and nothing fixes it. For these affected desktops, Vbox is unable to work.

Note that this error is very similar to open issue logged with Oracle, on which there is no resolution, but it seems very suspicious that it's working for most of QA and RnD, except for those recent windows builds.

Scenario 1: 
------------------
On install, or subsequently from :
 ==> Vbox/File/Preferences/Network/Host-Only/ ==> try to create a new ""host-only"" adapter:
Result Code: E_FAIL (0x80004005)
- In Device manager, every time this is attempted, we get a new ""unknown"" network device.
- Manual device driver update fails (see attached screenshot)
 
Scenario 2:
-----------------
On any guest image
==> Settingas/Network==> select ""Bridged"" network adapter ==> save and start guest VM:
Result Code:  E_FAIL (0x80004005)
Component: 
Console
Interface: 
IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}


Similar issues logged @ Virtual Box:
--------------------------------------------
   * https://www.virtualbox.org/ticket/13690
   * https://www.virtualbox.org/ticket/13681
   * https://www.virtualbox.org/ticket/13654
   * https://www.virtualbox.org/ticket/13481

See attached vbox ""setupapi"" log files and screenshots
--------------------------------------------",mkorning
13875,Uninstaller doesnt remove all drivers,VirtualBox 4.3.22,defect,2015-02-21T11:30:57Z,2015-02-21T11:30:57Z,2015-02-21T11:30:57Z,"Hello,

The VirtualBox uninstaller on Windows does not remove the following drivers even after multiple reboots:

VirtualBox Host-Only Ethernet Adapter: 
\SystemRoot\system32\DRIVERS\VBoxNetAdp.sys

VirtualBox Bridged Networking Service: 
\SystemRoot\system32\DRIVERS\VBoxNetFlt.sys

This has the added effect of showing these devices to end-users when calling GetAdaptersAddresses and specifying the GAA_FLAG_INCLUDE_ALL_INTERFACES flag.

The uninstaller should add these drivers to the PendingFileRenameOperations registry key allowing Windows to remove them on system restart.",dmex04
12910,respect host-only settings on update / upgrade,VirtualBox 4.3.10,defect,2014-04-04T08:22:32Z,2015-02-20T12:51:47Z,2015-02-20T12:51:47Z,"Every time I updated / upgraded my VBox installation my Host-only Adapter settings are changed. I have to reconfigure my settings all the time. This is very annoying, because the problem exists for years.",kirsche40
13663,Repeat installation without reboots in between does not work.,VirtualBox 4.3.12,defect,2014-12-01T10:55:34Z,2015-02-16T10:54:38Z,2015-02-16T10:54:38Z,"*Steps to reproduce*
1. Download VBox 4.3.12 (x64 in my case). 
2. Install the setup. 
3. Uninstall the setup. A dialog prompts for reboot. Select 'No'.
4. Again install the same setup. 
5. Upon complete installation, a reboot prompt appears. Select 'Yes' this time. 
6. Upon reboot, try to start a VM (simple windows 7 installation .vdi)

*Observation*
VM does not start. 
Kernel driver missing error is shown. ",praseo
8985,Use 'addgroup' instead of 'groupadd' in installer,VirtualBox 4.0.8,defect,2011-05-29T05:57:03Z,2014-02-27T17:32:49Z,2014-02-27T17:32:49Z,"When testing one of the generic Linux builds (e.g. 'VirtualBox-4.0.8-71778-Linux_x86.run') on a minimal distribution that lacks the 'groupadd' command the 'vboxusers' group will not be created.

Example: TinyCoreLinux, which is based on BusyBox (download: http://distro.ibiblio.org/tinycorelinux/3.x/release/tinycore-current.iso, currently at version 3.6)

The issue could be easily avoided if on those systems in 'install.sh' a command like ""addgroup -S $GROUPNAME"" instead of ""groupadd $GROUPNAME"" would be executed.

After checking a few of the ""big"" (or should one rather say ""bloated"") distributions (e.g. Natty Narwhal or FC-14) I've realized that not all are having 'addgroup' in their base, so first a check of the availability of the respective command would be required.",maronz
11876,should change char to wide character in VBoxStub.cpp,VirtualBox 4.2.12,defect,2013-06-18T07:54:47Z,2013-06-18T07:54:47Z,2013-06-18T07:54:47Z,"
If a user name is not english(such as East Asia Lang.-Korean, Japanese..), current stub code can not extracts msi and cab file.

or one of way is

do not use user's temp folder. (like C:\TEMP_VIRTUALBOX) but it is not good way.

",Woof
11333,configure script rejects --prefix,VirtualBox 4.2.6,defect,2012-12-26T07:05:03Z,2013-02-05T12:01:26Z,2013-02-05T12:01:26Z,"as far as i can see, there is no way to teach vbox' configure script the used prefix.

sabotage linux uses """" (empty, i.e. ""/"") as prefix. there is no /usr.",John.Spencer
11096,No Host-Only Network Adapter after upgrading from 4.2.0 to 4.2.2,VirtualBox 4.2.2,defect,2012-10-21T01:05:49Z,2012-10-21T03:25:17Z,2012-10-21T03:25:17Z,"
There appears to be a flaw in the Windows installer script, probably custom actions.

Upgrading from 4.2.0 to 4.2.2 on a Windows 7 x64 SP1 host produces the following:

""--Error Renaming Connection-- Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.""

The msi logs indicate the installation was 'sucessful'. However in addition to the 'Proxy' issue already reported, the Host-only Networks section of VirtualBox Settings is completely blank.
",Bob Kosch
10156,Windows Guest Additions lacks silent reboot option,VirtualBox 4.1.8,defect,2012-01-11T03:59:00Z,2012-01-11T03:59:00Z,2012-01-11T03:59:00Z,"VBox: 4.1.8

Guest: Windows XP

VBoxWindowsAdditions.exe has ""/S"" flag for silent install, but lacks a flag for silent reboot, which is a problem for unattended install.

This problem prevents wish #5810 from finishing.

-Technologov, 11.Jan.2012.",Technologov
4753,ost-only network adapters settings change after reinstall,VirtualBox 4.1.4,defect,2009-08-11T15:32:38Z,2011-10-21T05:30:43Z,2011-10-21T05:30:43Z,"Every time I reinstall (mostly when updating to a new version) VirtualBox, my host-only network adapter settings are changed... I found out about this when the internet in the guests stopped working. The first time it took me a while to discover that the problem was on the changed settings, I never though they would be different for any reason.

The host-only settings for each adapter has two tabs, ""Adapter"" and ""DHCP Server"".

Since I have the DHCP Server disabled, I don't know if it happens to those settings. But for the Adapter, I change the IP and Network Mask to match my needs and every time I update (last time was 3.0.2 -> 3.0.4), those settings are reset to the default values and because of that, my network connection stops working in the guests because it can't find the Adapter IP I specified.

Don't you agree that any settings for custom configurations shouldn't be changed when the user re-installs or upgrades to a new version? I mean, I changed the settings for a reason, I'm not expecting them to change unless I explicitly change them.",Nazgulled
9004,"Neo-layout keyboard in host is not supported, regression from Bug #2595?",VirtualBox 4.0.8,defect,2011-06-01T09:56:10Z,2011-09-30T21:22:07Z,2011-09-30T21:22:07Z,"I am using Virtualbox 4.0.8 on Linux Debian Host (Debian SID) with a NEO2 Keyboard layout (see http://www.neo-layout.org). If I use this keyboard while starting Virtualbox, several keys don’t work: for example [CAPS]+[l] for “-” etc. If I overwrite VBoxKeyboard.so with the version of VBoxKeyboard.so attached to Bug #2595, everything works fine.",Johannes Fichtinger
8606,Files remain installed and locked by Windows after uninstall or upgrade,VirtualBox 4.0.4,defect,2011-03-21T20:32:27Z,2011-05-17T18:24:20Z,2011-05-17T18:24:20Z,"Upon upgrading from v4.0.2 to 4.0.4 I was unable to launch any VMs. I discovered that vboxdrv.sys, vboxnetadp.sys and vboxusbmon.sys were still from v4.0.2 and one of them was locked. Upon rebooting the machine and manually removing the files I was able to install 4.0.4 successfully.",Patrick Headley
8828,Back button in program installer doesn't work,VirtualBox 4.0.6,defect,2011-05-03T05:17:22Z,2011-05-03T05:17:22Z,2011-05-03T05:17:22Z,"This is while installing the software on WINDOWS (not sure about other systems) When you get to the last screen on ""Oracle VM VirtualBox 4.0.6 Setup"", the back button does nothing.",Jimmy
8637,Inappropriate Runlevel for openSUSE 11.4,VirtualBox 4.0.4,defect,2011-03-27T13:01:30Z,2011-03-27T13:01:30Z,2011-03-27T13:01:30Z,"/etc/init.d/vboxdrv and /etc/init.d/vboxweb-service contain runlevel 4 
in the openSUSE 11.4 RPM package, however, runlevel 4 is not used at all 
in openSUSE and thus leads to errors when trying to change any of the 
runlevel scripts.

- No Log-Attachment needed for this -",Michael Kromer
7773,USB does not work with NIS or LDAP login,VirtualBox 3.2.10,defect,2010-11-29T11:29:03Z,2010-11-29T11:29:03Z,2010-11-29T11:29:03Z,"When users are authenticated via NIS or LDAP and uid and gid are provided via NIS or LDAP ordinary users can not mount USB devices in guests onless the provided uid and/or gid are identical on the host and the provided uid and gid from NIS or LDAP.

The problem is that when a user is installing Virtualbox the installation script apparently scans the local group and passwd files and if user and group vbox* is not found then these users and groups are created locally and the information created is used in the following installation process.",Michael Rasmussen
1752,Software Installation not passed Windows Logo testing,VirtualBox 1.6.2,defect,2008-06-20T18:34:53Z,2010-10-05T22:06:06Z,2010-10-05T22:06:06Z,"During installation a dialog box appears warning that:

""The software you are installing has not passed the Windows Logo testing to verify its compatibility with Windows XP.  (Tell me why this is important)

Continuing your installation of this software may impair or destabilize the correct operation of your system either immediately or in the future.  Microsoft strongly recommends that you stop this installation now and contact the software vendor for software that has passed Windows Logo testing""

Some users may take Microsoft's strong advice and not install VirtualBox.",Jerry Waldorf
4678,Linux host running on MacBook Hardware: Default release key should be left-winkey,VirtualBox 3.0.4,defect,2009-08-05T02:03:49Z,2009-08-05T08:16:12Z,2009-08-05T08:16:12Z,"Here's a simple one:

The default key to release a captured mouse from the VBox window is right-ctrl. Quite rightly it is set to Left-Command when running on an OSX host, because some hardware, such as a MacBook Pro, doesn't have such a button, and you'll be unable to free your mouse without some annoyance.

However the same decision isn't taken when you run on Linux (or, I imagine, Windows,) running on a MacBook. It'd be neat if the installer would figure out that we're on an Apple device and set the release key to something different!",Chris Smowton
