Hello,
The new package uploaded on April 20, 2025 to your repository, containing Oracle VirtualBox version 7.1.8, is not working.
Silent installation fails.
This is not a problem with wapt but with VirtualBox itself. The `--silent` argument, required for silent installation, is no longer recognized by the VirtualBox-7.1.8-168469-Win.exe executable.
Pending a fix from VirtualBox, this package should be removed from your repository.
Regards,
tis-virtualbox not working
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
we've looked into this internally, but we've mainly noticed that during an upgrade, the machine needs to reboot for the installation to work!
There's no problem with a fresh install.
we've looked into this internally, but we've mainly noticed that during an upgrade, the machine needs to reboot for the installation to work!
There's no problem with a fresh install.
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello again,
to be more precise, the `--silent` option "works" in the sense that the installer exits correctly with an error message (1603) in case of issues in silent mode, and with a popup asking to reboot when launched manually, and that it works during a reinstall after reboot.
The installation AND the update went smoothly on LUTI, so on a clean VM, the installation and upgrade work fine. It must therefore be related to a state with a Vbox that has been outdated. We did indeed see the problem on internal machines, but it disappeared after a reboot.
We'll see if it's possible to make the Vbox installer behave better. If you have more information on the different behaviors, we'd appreciate it.
Sincerely,
Denis
to be more precise, the `--silent` option "works" in the sense that the installer exits correctly with an error message (1603) in case of issues in silent mode, and with a popup asking to reboot when launched manually, and that it works during a reinstall after reboot.
The installation AND the update went smoothly on LUTI, so on a clean VM, the installation and upgrade work fine. It must therefore be related to a state with a Vbox that has been outdated. We did indeed see the problem on internal machines, but it disappeared after a reboot.
We'll see if it's possible to make the Vbox installer behave better. If you have more information on the different behaviors, we'd appreciate it.
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
thank you for this information.
However, if the update is attempted without restarting the machine, the tis-VirtualBox package uninstalls the old version, and the installation of the new version fails due to the variable:
silentflags="--silent --msiparams REBOOT=ReallySuppress ALLUSERS=2 VBOX_INSTALLDESKTOPSHORTCUT=0 VBOX_START=0 VBOX_INSTALLQUICKLAUNCHSHORTCUT=0".
I understand that simply not performing the upgrade without a restart avoids this problem.
My concern is that I manage a fleet of 560 machines, and 60 of them have this package. Some machines cannot restart frequently, or even ever; my only way to keep them up to date is to run the updates without a restart.
Therefore, would it be possible to include a safeguard in the VirtualBox package to cancel the update if it is launched without a restart?
If that's not possible, could you help me package it that way?
Regards,
thank you for this information.
However, if the update is attempted without restarting the machine, the tis-VirtualBox package uninstalls the old version, and the installation of the new version fails due to the variable:
silentflags="--silent --msiparams REBOOT=ReallySuppress ALLUSERS=2 VBOX_INSTALLDESKTOPSHORTCUT=0 VBOX_START=0 VBOX_INSTALLQUICKLAUNCHSHORTCUT=0".
I understand that simply not performing the upgrade without a restart avoids this problem.
My concern is that I manage a fleet of 560 machines, and 60 of them have this package. Some machines cannot restart frequently, or even ever; my only way to keep them up to date is to run the updates without a restart.
Therefore, would it be possible to include a safeguard in the VirtualBox package to cancel the update if it is launched without a restart?
If that's not possible, could you help me package it that way?
Regards,
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Benoit,
the package performs an uninstallation because there were older versions of vBox that weren't upgrading correctly. If you upgrade from version 6 or 7 to the latest version, it might work properly and avoid having to uninstall it beforehand. We'll test this internally; you can test it on one of your machines to see how it behaves.
Regards,
Denis
the package performs an uninstallation because there were older versions of vBox that weren't upgrading correctly. If you upgrade from version 6 or 7 to the latest version, it might work properly and avoid having to uninstall it beforehand. We'll test this internally; you can test it on one of your machines to see how it behaves.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
I encountered the same installation failure issue with an exit error at version 1603 on an update to version 7.1.6 previously installed via WAPT.
I completed the installation, let me explain:
During the package execution, the previous version was uninstalled. By monitoring the uninstallation and package progress, I deleted the remaining contents of the "C:\Program Files\Oracle\VirtualBox" folder. After the uninstallation, the subsequent package deployment installed VirtualBox 7.1.8 without any problems and completed successfully.
Unfortunately, following this action, none of my VMs were working anymore. I must admit, I wasn't exactly gentle with the process.
So I reverted to version 7.1.6 (by uninstalling 7.1.8 via the settings and removing the 7.1.8 package) using the corresponding package, and removed all my VMs from the list without deleting the folders. I then re-imported my VMs by double-clicking the .vbox file of each one.
I think it's leftover files from previous installations that are interfering with the installation.
Once I started with a clean version of 7.1.6, the 7.1.8 package installed correctly.
Another important point:
For some versions of VirtualBox, VirtualBox extension packs no longer install because the file in the package is named Oracle_VirtualBox_Extension_Pack-XXXvbox-extpack, while setup.py attempts to install it: `
for ext in glob.glob("Oracle_VM_VirtualBox_Extension_Pack-*.vbox-extpack")`.
Note that the "_VM" part of the name has been missing for some time now (perhaps since version 7.0).
Best regards.
I encountered the same installation failure issue with an exit error at version 1603 on an update to version 7.1.6 previously installed via WAPT.
I completed the installation, let me explain:
During the package execution, the previous version was uninstalled. By monitoring the uninstallation and package progress, I deleted the remaining contents of the "C:\Program Files\Oracle\VirtualBox" folder. After the uninstallation, the subsequent package deployment installed VirtualBox 7.1.8 without any problems and completed successfully.
Unfortunately, following this action, none of my VMs were working anymore. I must admit, I wasn't exactly gentle with the process.
So I reverted to version 7.1.6 (by uninstalling 7.1.8 via the settings and removing the 7.1.8 package) using the corresponding package, and removed all my VMs from the list without deleting the folders. I then re-imported my VMs by double-clicking the .vbox file of each one.
I think it's leftover files from previous installations that are interfering with the installation.
Once I started with a clean version of 7.1.6, the 7.1.8 package installed correctly.
Another important point:
For some versions of VirtualBox, VirtualBox extension packs no longer install because the file in the package is named Oracle_VirtualBox_Extension_Pack-XXXvbox-extpack, while setup.py attempts to install it: `
for ext in glob.glob("Oracle_VM_VirtualBox_Extension_Pack-*.vbox-extpack")`.
Note that the "_VM" part of the name has been missing for some time now (perhaps since version 7.0).
Best regards.
