by TeraByte Support(PP) » Sat Dec 09, 2017 4:32 pm
If you're using the TBWinRE.cmd script, you could edit the line in the script and add the /forceunsigned option if you wanted to make the fix. For example, in the ":: Add Drivers" section:
Dism /image:"!tbpath!\mount" /Add-Driver /driver:"!tbpath!\Drivers" /recurse /forceunsigned
If you're using the TBWinPE/RE Builder program (TBWinPE.exe), it should already force unsigned drivers if using the DISM API is supported and enabled. If using this method, can you provide a complete log of the build where it errors?
Otherwise, if using Builder, but not the DISM API, it can be looked into to add support for the option in that mode.
Paul Purviance
TeraByte Support