I've installed a driver, signed with a new certificate (issued a month ago), on a fresh windows 10 machine (version 1803). Since this is a non-pnp driver, by installing I mean copying files to machine and registering under Services key in registry.
I've enabled secureboot in the machine (and checked with powershell that it is indeed enabled).
It was my expectation that the driver will not load, due to new restrictions on windows 10 regarding signature. But it load just fine. What am I missing ?
(I've also looked through the eventlog to see if there was a registered event about the driver not being properly signed or something like that, but didn't see that either).
Am I missing something ? Are there any more specific cases I need to answer to, in order for the driver not to load ?
I'm basing my data on this :https://docs.microsoft.com/en-us/windows-hardware/drivers/install/kernel-mode-code-signing-policy--windows-vista-and-later-