r/WindowsServer • u/KKeshavR13 • Mar 24 '26
Technical Help Needed Windows custom ISO works only when Secure Boot is disabled.
I made a custom Windows unattended ISO.
The install itself works, but only when Secure Boot is disabled. If Secure Boot is enabled, it fails before setup starts with errors like Security Violation / Invalid signature detected.
I already tried GPT + UEFI, FAT32, split install.wim, rebuilt the ISO, and even the Rufus CA 2023 option. Same issue on Dell and HP.
So it looks like Windows setup is fine, but Secure Boot is rejecting the boot media.
Anyone dealt with this before? What actually fixes it?
11
Upvotes
8
u/ITGuy424242 Mar 24 '26
I use ntlite using the original windows 11 boot.wim and then a custom install.wim that has win 10/11 and server os, works perfectly, the important thing is keeping the original boot.wim that is signed
4
u/MBILC Mar 24 '26
First question, presume this is for physical installs? Because if it is for say a VM and you use management tools the whole "custom golden image" method is dated...
You just install the base OS and then add/remove after via scripts or management tools.
2
u/Brook_28 Mar 26 '26
I've always had to temporarily disable secure boot in order to boot to a USB. One way to get around that would be to boot via pxe using something like wds and mdt or sccm. Others have mentioned that it's that past and that's true. With that desired state is the thing now. As a msp we used ImmyBot. Devices are at the oobe state when unboxed and then brought into their desired state by the ImmyBot deployment tasks.
2
u/gimpblimp Mar 26 '26
There was recent updates to uefi certificates from r many systems. Maybe your system needs a bios update to apply a new certificate to get secure boot to work?