v6.1.37 Test Build 152627 - Fails to Install

[Jacob Klein]

v6.1.37 Test Build 152627
... fails to install.

It says
"Oracle VM VirtualBox 6.1.37 Setup Wizard ended prematurely"
and
VirtualBox Installer
Installation failed! Error: Fatal error during installation.

Tested on Windows 10 Release Preview (19045.1865), and Windows 11 Dev Channel (25169.1000)
... since those are all that I have readily available.

Is the installer busted for this VirtualBox Test Build?

Oracle VirtualBox v6.1.36 Build 152435
... continues to install fine.

[fth0]

The background reason probably is that the VirtualBox kernel drivers of the VirtualBox test builds are not attestation signed.

[Jacob Klein]

Would that explain why 6.1.35 Test Builds installed fine, but the 6.1.37 Test Build 152627 doesn't install?

[fth0]

AFAIK, the VirtualBox kernel drivers of theVirtualBox test builds were never attestation signed, so that cannot be the sole reason. The certificate handling in different Windows versions and the sets of certificates used in different VirtualBox versions are a very complex topic (*) that has undergone several changes in the previous years. VirtualBox 6.1.36 again replaced some of the certificates used.

(*) To give you a little impression, here is my personal overview over the 17 certificates used by VirtualBox 6.1.36 for all VirtualBox kernel drivers (expand the view to see them all at once ):

Code: Select all

10.11.2006 10.11.2031 [SHA1] 0CE7 0563  DigiCert Assured ID Root CA
22.10.2013 22.10.2028 [SHA2] 0409 92C1    DigiCert SHA2 Assured ID Code Signing CA
23.02.2021 17.04.2024 [SHA2] 0F52 3065      Oracle Corporation
09.06.2022 10.11.2031 [SHA2] 0124 18C5    DigiCert Trusted Root G4
23.03.2022 23.03.2037 [SHA2] 0736 B6C8      DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA
29.03.2022 15.03.2033 [SHA2] 0A7A 8508        DigiCert Timestamp 2022 - 2

08.11.2006 17.07.2036 [SHA1] 18DA 4EB6  VeriSign Class 3 Public Primary Certification Authority - G5
08.02.2010 08.02.2020 [SHA1] 5200 4958    VeriSign Class 3 Code Signing 2010 CA
23.12.2013 23.12.2016 [SHA1] 51CA 7E92      Oracle Corporation

01.01.2014 01.01.2015 [SHA?] ???? ????  VirtualBox for legacy Windows Only Timestamp CA
01.01.2014 01.01.2015 [SHA2] 2F45 5528    VirtualBox for legacy Windows Only Timestamp Kludge 2014

23.06.2010 24.06.2035 [SHA2] 28CC 3B1E  Microsoft Root Certificate Authority 2010
15.10.2014 15.10.2029 [SHA2] 3300 1906    Microsoft Windows Third Party Component CA 2014
09.09.2021 01.09.2022 [SHA2] 3300 8B26      Microsoft Windows Hardware Compatibility Publisher
30.09.2021 30.09.2030 [SHA2] 3300 3605    Microsoft Time-Stamp PCA 2010
28.10.2021 26.01.2023 [SHA2] 3300 E13C      Microsoft Time-Stamp Service
02.12.2021 28.02.2023 [SHA2] 3300 F32C      Microsoft Time-Stamp Service

[Jacob Klein]

Something new is happening with the .37 test builds, then. I'll try to find an install log file. Not sure where to look.

[fth0]

Try C:\Windows\INF\setupapi.dev.log.

[Jacob Klein]

When I run the installer with option "--logging", I'm able to get an install log file in C:\Users\{User}\AppData\Local\Temp

See attached to compare these:
VBoxInstallLog - 6.1.36 r152435.txt
VBoxInstallLog - 6.1.37 r152676.txt

The main problem appears to be:
DIFXAPP: ERROR: Signature verification failed while checking integrity of driver package 'VBoxSup.inf' ('C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.inf'). (Error code 0x800B0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.)

Is it possible that 6.1.35 Test Builds were WHQL signed, but 6.1.37 Test Builds are not?
Note: I don't have my 6.1.35 Test Builds anymore, but I'm sure they worked.

Log comparisons:

6.1.36 r152435:

Code: Select all

DIFXAPP: INFO:   ENTER:  DriverPackageInstallW
DIFXAPP: INFO:   VBoxSup.inf: checking signature with catalog 'C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.cat' ...
DIFXAPP: INFO:   Driver package 'VBoxSup.inf' is WHQL signed.
DIFXAPP: INFO:   Copied 'VBoxSup.inf' to driver store...
DIFXAPP: INFO:   Copied 'VBoxSup.cat' to driver store...
DIFXAPP: INFO:   Commiting queue...
DIFXAPP: INFO:   Copied file: 'C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.sys' -> 'C:\WINDOWS\system32\DRVSTORE\VBoxSup_BDE744C98864AE594E53FDDC04157964151FDB76\VBoxSup.sys'.
DIFXAPP: INFO:   Installing INF file "C:\WINDOWS\system32\DRVSTORE\VBoxSup_BDE744C98864AE594E53FDDC04157964151FDB76\VBoxSup.inf" of Type 1.
DIFXAPP: INFO:   Installing legacy driver 'C:\WINDOWS\system32\DRVSTORE\VBoxSup_BDE744C98864AE594E53FDDC04157964151FDB76\VBoxSup.inf'
DIFXAPP: INFO:   Service 'VBoxSup' was started
DIFXAPP: SUCCESS:Installation completed with code 0x0.
DIFXAPP: INFO:   RETURN: DriverPackageInstallW  (0x0)
DIFXAPP: INFO:   ENTER:  DriverPackageGetPathW
DIFXAPP: SUCCESS:Found driver store entry.
DIFXAPP: INFO:   RETURN: DriverPackageGetPathW  (0x7A)
DIFXAPP: INFO:   ENTER:  DriverPackageGetPathW
DIFXAPP: SUCCESS:Found driver store entry.
DIFXAPP: INFO:   RETURN: DriverPackageGetPathW  (0x0)
DIFXAPP: INFO: driver store entry for 'C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.inf' is 'C:\WINDOWS\system32\DRVSTORE\VBoxSup_BDE744C98864AE594E53FDDC04157964151FDB76\VBoxSup.inf'.
DIFXAPP: INFO: The component Id '{D3E2F2BB-569F-46A2-836C-BDF30FF1EDF8}' is now set to point to driver store: 'C:\WINDOWS\system32\DRVSTORE\VBoxSup_BDE744C98864AE594E53FDDC04157964151FDB76\VBoxSup.inf'
DIFXAPP: INFO: A reboot is not needed to install the component '{D3E2F2BB-569F-46A2-836C-BDF30FF1EDF8}'.
DIFXAPP: RETURN: InstallDriverPackages() 0 (0x0)

6.1.37 r152676

Code: Select all

DIFXAPP: INFO:   ENTER:  DriverPackageInstallW
DIFXAPP: INFO:   VBoxSup.inf: checking signature with catalog 'C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.cat' ...
DIFXAPP: ERROR:  Signature verification failed while checking integrity of driver package 'VBoxSup.inf' ('C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.inf'). (Error code 0x800B0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.)
DIFXAPP: INFO:   Successfully removed '{D3E2F2BB-569F-46A2-836C-BDF30FF1EDF8}' from reference list of driver store entry ''
DIFXAPP: INFO:   RETURN: DriverPackageInstallW  (0x800B0100)
DIFXAPP: ERROR: encountered while installing driver package 'C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.inf'
DIFXAPP: ERROR: InstallDriverPackages failed with error 0x800B0100
DIFXAPP: RETURN: InstallDriverPackages() 2148204800 (0x800B0100)
CustomAction MsiInstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 18:06:48: InstallFinalize. Return value 3.

[fth0]

First of all, WHQL/HLK/HCK signing and attestation signing are similar in that in both cases the drivers are provided to Microsoft, where they are signed using the Microsoft certificate chains. This happens for the VirtualBox release updates (e.g. VirtualBox 6.1.34 and 6.1.36), but usually (*) not for the VirtualBox test builds (e.g. VirtualBox 6.1.35 and 6.1.37).

(*) There were a few exceptions from that rule in the past, which could be or not be the key in your previous experience.

Several users of the VirtualBox 6.1.35 test builds have reported the same error (0xE0000247, 0x800B0109, 0x800b0100) in the past that you're experiencing with the VirtualBox 6.1.37 test build.

[Jacob Klein]

Hmm... I haven't had any Test Build install failures like this in a long while, like months, and I've tested nearly every one.
Something is different with the 6.1.37 Test Builds.

[multiOS]

The test builds have been updated to 6.1.x revision 152676. You might want to retry to see if you still get the same problem.

[Jacob Klein]

Is v6.1.37 Test Build 152676 installing right for you?
It's still failing to install for me.

[fth0]

Something is different with the 6.1.37 Test Builds.

One thing that's different are the SHA-1 based certificate chains. But the SHA-2 based certificate chains didn't change, and Windows 10/11 should ignore/reject the SHA-1 certificate chains anyway. Which brings me to an idea:

Mount the VirtualBox Guest Additions ISO on the host (!), open a Command Prompt with administrator privileges, navigate to the cert folder of the virtual DVD and execute the following command, then retry the installation:

Code: Select all

VBoxCertUtil.exe add-trusted-publisher vbox*.cer --root vbox*.cer

If it works and if you can revert the changes on your host, try each of the three certificates in the folder on its own. Start with vbox-legacy-timestamp-ca.cer. Or start the whole experiment first with this certificate alone. I'm curious what you'll discover.

[Jacob Klein]

Sorry, but I don't want to manually add any certificates, unless it is a new requirement of using Test Builds.
We need someone to reproduce the problem and find out why it's happening. I've tried to help.

[BlueMonday19]

v6.1.37 Test Build 152627
... fails to install.

It says
"Oracle VM VirtualBox 6.1.37 Setup Wizard ended prematurely"
and
VirtualBox Installer
Installation failed! Error: Fatal error during installation.

Tested on Windows 10 Release Preview (19045.1865), and Windows 11 Dev Channel (25169.1000)
... since those are all that I have readily available.

Is the installer busted for this VirtualBox Test Build?

Oracle VirtualBox v6.1.36 Build 152435
... continues to install fine.

I have the same problem with 6.1.37, none of these newer builds will work. I get the same error during install. It's annoying that the previous version uninstalls itself before failing. 6.1.35 and 6.1.36 are working.

[fth0]

Sorry, but I don't want to manually add any certificates

No problem, we can both do what we like to do, since we're not working for the VirtualBox development. At least officially.

BTW, if you take a look at the command line help of the VirtualBox Windows Installer, you'll notice a new --force-install-timestamp-ca option that is supposed to automatically install the vbox-legacy-timestamp-ca.cer certificate.

Anyway, thanks for your support.