Windows - Software - Install Oracle VM VirtualBox (64-Bit)

What the Oracle VirtualBox installer does

This Automox Worklet™ deploys Oracle VM VirtualBox 64-bit to Windows endpoints. VirtualBox is Oracle's open-source x86 and AMD64 hypervisor used for running Linux, Windows, and BSD guest operating systems on a single host. The Worklet downloads the signed installer from the Automox API cache, runs it with --silent and --ignore-reboot, and confirms placement through the Windows uninstall registry.

The evaluation phase reads the Windows uninstall registry to detect whether Oracle VM VirtualBox is already present. The Worklet inspects both HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall, so the check catches installs registered under either bitness. Endpoints that already have VirtualBox are marked compliant and skip remediation, which keeps the policy safe to schedule on a recurring cadence.

The remediation phase downloads VirtualBox.exe from the Automox API cache into the Automox agent working directory, runs the installer with --silent and --ignore-reboot, removes the downloaded file, and re-queries the uninstall registry to confirm success. The Automox cache pins the version, so every endpoint in the policy lands on the same VirtualBox build rather than whatever happens to be on Oracle's download page on a given day.

Why deploy VirtualBox at fleet scale

VirtualBox is a recurring per-user request on developer, QA, and training fleets. Installing it one laptop at a time loads the help desk queue and lets the installed version drift across the team within a quarter, which breaks guest-OS reproducibility between engineers.

Target one policy at the group that needs VirtualBox and every endpoint resolves to the same build pinned in the Automox cache. A new endpoint joining the group inherits VirtualBox on its next evaluation cycle without a help-desk ticket, and 32-bit endpoints that get pulled into the group are no-oped by the remediation script rather than failing.

How VirtualBox deployment works

1. Evaluation phase: On a 64-bit Windows OS, the Worklet enumerates both HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall, filtering DisplayName for Oracle VM VirtualBox. A match exits 0 and marks the endpoint compliant. No match exits non-zero and queues remediation. On 32-bit Windows the evaluation reads the 32-bit uninstall path and the remediation script immediately exits 0, since the 64-bit installer is not applicable on that architecture.

2. Remediation phase: The script downloads VirtualBox.exe from the Automox API cache into the Automox agent working directory using a System.Net.WebClient call, then launches it through Start-Process -Wait with the arguments --silent --ignore-reboot. The --silent flag suppresses the installer UI; the --ignore-reboot flag prevents the installer from triggering a restart so the Automox agent stays in control of the maintenance window. After Start-Process returns, the script deletes the .exe and re-queries the 64-bit uninstall registry to confirm the DisplayName is now present.

VirtualBox deployment requirements

• 64-bit Windows 10, Windows 11, or Windows Server with PowerShell available to the Automox agent (32-bit endpoints exit compliant without action)

• Hardware virtualization enabled in firmware (Intel VT-x or AMD-V) for guest VMs to boot once VirtualBox is installed; the installer itself does not require it

• Outbound HTTPS reachability from the endpoint to the Automox API cache (api.automox.com) so the installer download can resolve

• Administrative context for the Automox agent (the default agent service account already satisfies this) so the installer can write under C:\Program Files\Oracle\VirtualBox

• No policy variables to configure; the cache URL and silent-install flags are baked into the remediation script

• Free disk space for the transient installer download plus the installed application footprint under C:\Program Files\Oracle\VirtualBox

Expected state after VirtualBox deployment

After successful remediation, C:\Program Files\Oracle\VirtualBox contains the VirtualBox.exe, VBoxManage.exe, and VBoxHeadless.exe binaries. The Windows uninstall registry shows an "Oracle VM VirtualBox" entry under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall with a populated DisplayVersion, and the VirtualBox Manager shortcut appears in the Start menu for the logged-in user. The Automox activity log captures the exit code from the installer and the post-install registry confirmation.

Validate from PowerShell with Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object DisplayName -like 'Oracle VM VirtualBox*' to confirm DisplayName, DisplayVersion, and InstallLocation. Run "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version to print the installed VirtualBox build string from the binary itself; this is the cleanest evidence to capture in change-control tickets. The --ignore-reboot flag means VirtualBox is installed but the host networking driver may not be fully active until the endpoint reboots, so guest VMs with bridged networking may require a one-time restart before they come up. Subsequent Worklet evaluations find the uninstall key and exit without re-running the installer, so the policy is safe on a daily or weekly schedule.