VirtualBox-7.0.3-154539-Win Install fail - rollback. 7.02 OK

[AndyCot]

I have tried to install VirtualBox-7.0.3-154539-Win.exe and it fails to install. 7.0.2 installs.

Attached (in the zip) are the logs for 7.02 & 7.0.3-154539.

The 7.03 failure looks like it's to do with the "Driver package 'VBoxSup.inf' is WHQL signed." as comparing the two files the error differences start as the following :

7.0.2:
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...

7.0.3-154539
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'

I am using Windows 11 22H2 fully updated as of yesterday's updates.

I am running 7.0.2 and will keep an eye out for 7.03 updates to see if the certificate issue is fixed.

[fth0]

Did you read and follow the instructions on the VirtualBox test builds page, especially the part regarding the --force-install-timestamp-ca option?

[AndyCot]

No. 7.00 beta works and so have all of the other RC/ beta's I have installed.

Will give it a go.

[fth0]

7.00 beta works and so have all of the other RC/ beta's I have installed.

That's because RCs and BETAs are attestation signed just like the Release versions. For test builds, it's allegedly too much effort.

[AndyCot]

Old 6.1.35 test builds were okay on Windows 10, but since then I have upgraded to Windows 11 after playing with it as a guest as the original W11 21H1 did not support my dev tools properly.

The --force-install-timestamp worked. Depending on the installer used some allow you to programmatically check things and this would be a good one to check and if it was not installed then ask the user if it's okay to install the certificate. I could not see what installer was used even in a hex editor/

[fth0]

I could not see what installer was used even in a hex editor/

Why do it simply, if you can do it complicated.

Try "VirtualBox-7.0.2-154219-Win.exe -?".