I'm working with several computers that were imaged using Sysprep, mostly similar models, but a few from a different manufacturer. I can boot into Windows without issues when Secure Boot is disabled, which I need to do to restore the image. Once I finish the Out-of-Box Experience (OOBE), everything runs smoothly and Intune handles updates well. However, when I enable Secure Boot, I run into signature verification failures. I've tried several fixes including BIOS updates, `bootrec /fixmbr`, `bootrec /fixboot`, and `bootrec /rebuildbcd` (which shows '0 OS found'). I also used GParted to adjust partitions as the image was created on a 256GB disk while most computers have 500GB or 1TB disks. I'm hoping someone with more experience with Secure Boot can help me understand how I might have broken it and how I can repair the boot issue. I'd really like to use Secure Boot as part of my compliance policy in Intune. Thanks!
1 Answer
You might need to update your Secure Boot certificate, as that can often lead to verification problems. You can check out resources like the one on GitHub for guidance. Just keep in mind that this could involve re-imaging some machines, which isn't ideal if you're looking to avoid that.
That looks like a hefty project. Just to clarify, are you suggesting I have to re-image all the workstations? That's not really feasible for me right now, so I'll have to explore other options.