Did anybody test boot.wim integration or on-the-fly adding at real Secure Boot hardware?
I did. Both methods don't work.
- Integrated boot.wim: Secure Boot will prevent the boot.wim to load, saying the driver's signature is not verified - even when "loadoptions", "nointegritychecks", "testsigning" are set.
- On-the-fly boot.wim: Boot.wim is loaded and the Setup GUI shows up, but the driver can't be installed. As Steve said, the USB is even disappeared. Re-run the drvload command, it will output the "Unable to load etc..." error.