Opened 2 years ago
Last modified 2 years ago
#20691 new defect
Can't install virtualbox to other hard drive with msi parameter
Reported by: | Owned | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 6.1.30 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
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:
Change History (9)
comment:1 by , 2 years ago
comment:2 by , 2 years ago
You could attach the log file.
Either way, I don't see any obvious problem in the log file. Pretty close to the end it says
Windows Installer a installé le produit. Nom du produit : Oracle VM VirtualBox 6.1.30. Version du produit : 6.1.30. Langue du produit : 1036. Fabricant : Oracle Corporation. Réussite de l’installation ou état d’erreur : 0.
With that message I would think that the install as such works. Or is this impression wrong?
Does VirtualBox start afterwards? Is this about not being able to run VMs after installing?
comment:3 by , 2 years ago
No i can't join the log file (limit exceeded). Virtualbox work after install but is not the problem... the problem is the argument used for install virtualbox in other hard drive, it doesn't work... TARGETDIR seems broken, if you can fix this...
comment:4 by , 2 years ago
this is not my first ticket concerning this bug, it will also be forgotten? :(
comment:5 by , 2 years ago
From my perspective it is the only ticket... you confirmed in #18121 that the issue is solved.
comment:6 by , 2 years ago
After a short investigation: The "monolithic" VirtualBox MSI installer does not check the TARGETDIR property at all. It does check the property INSTALLDIR, however, so that's what one needs to set.
This is the (simplified, of course you can re-add your quite specific options) working command line:
msiexec /i VirtualBox-6.1.30.msi /qb INSTALLDIR="D:\Program Files\Oracle\VirtualBox"
Side note: It seems that of one explicitly creates a MSM based installer when building VirtualBox then TARGETDIR would be used instead. Note that the MSM based installer isn't available "in the wild", because it tends to be bigger and there isn't a real benefit for the vast majority of the users.
comment:7 by , 2 years ago
My old ticket was solved because ive make a bad apparently...
tested with INSTALLDIR and doesn't work...
comment:8 by , 2 years ago
The log shows that something is wrong with the VBoxUSB.inf file in the Windows driver store (which always is at C:\Windows\System32\DriverStore). Don't see this here, the install on other drives simply succeeds. Could it be that you tried doing an upgrade install with simultaneously changing the INSTALLDIR?
No immediate idea what could cause such "file not found" issues for stuff which should be in the driver store.
comment:9 by , 2 years ago
Hello,
is not a upgrade but a fresh install with cmd (elevated privileges) msiexec /i VirtualBox-6.1.30.msi /qb INSTALLDIR="D:\Program Files\Oracle\VirtualBox"
log:
http://tutocss.free.fr/VirtualBox-6.1.30-install.log
cannot join here and cannot use pastebin or equivalent...