I have already done that! And on my laptops
UAC is off and my account is member of local Administrators group.
I do install all the options and obviously I do accept the signing warning for the drivers...
It simply doesn't work for the account used for the upgrade! It works if I use another account as I wrote! But if I do a rollback to v4.2.16 everything works as expected.
Right now I cannot fill a "regular" bug because I have changed my Oracle SSO email address and cannot reuse my old nickname...

(what a "mess"...)
The VB's logs are
more than just cryptic, but maybe there is an option somewhere to generate a more verbose one??
The quickest solution is the rollback to v4.2.16 but I do not want!!