How can we verify that an installer ( eg of an AV or anti-exe ) will install only drivers & kernel modules that are co-signed by Microsoft?
How to verify an installer will only install drivers co-signed by MS
- Thread starter notabot
- Start date
Please provide comments and solutions that are helpful to the author of this topic.
- Status
Secure boot will break after the fact that non ms signed drivers have been installed. The motivation of the question is actually “how can we know that installing xyz does not break secure boot”
What is UEFI Secure Boot?
UEFI is a more advanced firmware interface with many more customization and technical options. Secure Boot is something of a security gate. It analyzes code before you execute it on your system. If the code has a valid digital signature, Secure Boot lets it through the gate.
Must be using Windows 8 or newer. The code can also be signed by the pc manufacture. Hope this answers your question.
UEFI is a more advanced firmware interface with many more customization and technical options. Secure Boot is something of a security gate. It analyzes code before you execute it on your system. If the code has a valid digital signature, Secure Boot lets it through the gate.
Must be using Windows 8 or newer. The code can also be signed by the pc manufacture. Hope this answers your question.
It doesn’t - installing an unsigned ( not co-signed by MS ) driver will break secure boot - the question is, how can know before running an installer ( which amongst other things installs drivers ) if any drivers to be installed will be co-signed , after they’ve installed it’s too late, secure boot will be broken
- Jul 3, 2015
- 8,153
If secure boot is enabled, on a recent version of Windows that enforces co-signed drivers, the program installation will fail with a Windows error message about incompatible drivers. If you are stubborn and install the program anyways, Windows won't boot, or will boot but not load those drivers..
- Status
Similar threads
