Tranquil IT Forum

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,

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.

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

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,

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

All the machines in question are on version 7.

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.