VirtualBox test builds

Here we provide you with regularly updated links to recent builds. If one of these links does not work at any time feel free to ask us to update it on IRC or the development mailing list. See below for information about installing Linux packages. Regularly installing stable or development test builds and using them in your day-to-day work is one of the best ways you can help us improve the VirtualBox user experience. And if you do not have a support contract, a willingness to use test builds increases your chances of receiving informal support. (And using development test builds increases the chances of your voice being heard in our development process.)

Please be aware that

  • snapshots (and saved states of running machines) taken with more recent branches or development builds are likely not to work with older branches or releases.
  • The version of the Guest Additions contained in a package is usually one or two revisions older than the package revision. If in doubt, download the Guest Additions build as well (or instead).

Stable branch builds

If you are experiencing some problem with VirtualBox and want to find out whether it has been fixed before you file a bug report, if you want to help our quality testing, or if you just want a particular fix early, you may wish to try out a test build of the current release series.

These builds are expected to be almost as stable as released versions, and we accept bug reports against them. They may contain some features which we plan to include in a future stable release but not necessarily the next. For any mission critical use of VirtualBox we of course always recommend purchasing a support contract.

Development branch builds (bottom of page)

If you make any sort of mission-critical use of VirtualBox - particularly if you do not have a support contract - you are advised to regularly try out our development branch builds to make sure that everything you depend on still works as you expect. Catching problems at the development stage greatly improves your chances of having them solved before they reach a stable release, and increases your voice in the development process. The builds are usually usable for day-to-day work - we use them ourselves - for people who can deal with occasional surprises. Please report development build problems on IRC or the developer mailing list, not on the bug tracker.

A list of things worth testing for in test builds can be found here: Regression Testing.

Pick out your area of interest.

Installing Linux test builds

Test builds for Linux hosts are generally packed up in a shell script installer with the extension ".run". To install them, you first need to remove your existing VirtualBox installation (but not your virtual machines - they will continue to work with the test build) and then execute the installer. To remove the test build again, execute the installer with the parameter "uninstall" on the command line.

Installing Windows test builds

The Windows test build packages are working precisely like a usual VirtualBox installer packages, with one difference: they will not work (the error message will point to unsigned drivers) if you install them on Windows 10 if your system has UEFI secure boot enabled. To make these test build work you need to disable UEFI secure boot in the system's UEFI config.

New starting with 6.1.37 test builds: On Windows 10 and 11 you'll need to run the installer from the command line and specify the option --force-install-timestamp-ca. This only needs to be done once on a particular system. The symptom for not having this in place is failing VirtualBox driver installs.

Installing macOS test builds

The test builds are not going through Apple's notarization (would be too much effort to do this for every test build we upload). This means if you're using macOS 10.14.5 or later the kernel extensions will not load if you're using the default security settings. If you really want to use such a test build, you need to disable System Integrity Protection (as long as you're running test builds, we're strongly encouraging you to re-enable SIP once you're back to using an official release of VirtualBox).

The test builds for macOS/ARM64 work in principle on Macs with M1 or M2 CPU. However, they are developer previews with known issues (including serious performance ones) with all recent guest operating systems.


Latest 6.1.x test builds

Windows6.1.x revision 159049
macOS6.1.x revision 159049
Linux 64-bit6.1.x revision 159049
Linux EL6 64-bit6.1.x revision 159049
Linux EL7 64-bit6.1.x revision 159049
Linux EL8 64-bit6.1.x revision 159049
Solaris6.1.x revision 159049
Solaris IPS6.1.x revision 159049
Guest Additions6.1.x revision 159049
Extension Pack6.1.x revision 159049
SDK6.1.x revision 159049

Latest 7.0.x test builds

Windows7.0.x revision 159210
macOS7.0.x revision 159210
macOS/ARM64 BETA7.0.x revision 159210
Linux 64-bit7.0.x revision 159210
Linux EL7 64-bit7.0.x revision 159210
Linux EL8 64-bit7.0.x revision 159210
Linux EL9 64-bit7.0.x revision 159210
Solaris7.0.x revision 159210
Solaris IPS7.0.x revision 159210
Guest Additions7.0.x revision 159206
Extension Pack7.0.x revision 159208
SDK7.0.x revision 159210

Development snapshots

Windowsdevelopment revision 159220
macOSdevelopment revision 159216
macOS/ARM64 BETAdevelopment revision 159221
Linux 64-bitdevelopment revision 159220
Linux EL7 64-bitdevelopment revision 159220
Linux EL8 64-bitdevelopment revision 159220
Linux EL9 64-bitdevelopment revision 159220
Solarisdevelopment revision 159220
Solaris IPSdevelopment revision 159220
Guest Additionsdevelopment revision 159218
Extension Packdevelopment revision 159219
SDKdevelopment revision 159220

Last modified 8 weeks ago Last modified on Aug 4, 2023 8:02:33 PM
Note: See TracWiki for help on using the wiki.

© 2023 Oracle
ContactPrivacy policyTerms of Use