VirtualBox

Changes between Version 335 and Version 336 of Testbuilds


Ignore:
Timestamp:
Nov 10, 2023 11:10:07 AM (4 months ago)
Author:
Klaus Espenlaub
Comment:

update attestation and notarization status for test builds

Legend:

Unmodified
Added
Removed
Modified
  • Testbuilds

    v335 v336  
    2525== Installing Windows test builds ==
    2626
    27 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.
    28 
    29 '''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.
     27The Windows test build packages are working precisely like a usual !VirtualBox installer packages. They are now going through Microsoft's Attestation Signing (since May 2023, 6.1.45 and 7.0.9). No need to run the installer with special options or disable UEFI secure boot any more. Don't forget to re-enable UEFI secure boot if you disabled it previously to be able to run !VirtualBox test builds.
    3028
    3129== Installing macOS test builds ==
    3230
    33 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 [https://developer.apple.com/library/archive/documentation/Security/Conceptual/System_Integrity_Protection_Guide/ConfiguringSystemIntegrityProtection/ConfiguringSystemIntegrityProtection.html 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).
     31The test builds are now going through Apple's notarization (since July 2022, 6.1.37 and 7.0.1). No need to disable System Integrity protection any more. Don't forget to re-enable SIP if you disabled it previously to be able to run !VirtualBox test builds.
    3432
    3533The 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.

© 2023 Oracle
ContactPrivacy policyTerms of Use