we have a driver that needs to be started really early during the boot
process (ideally before any storage controller devices are initialized).
It seemed that setting driver's load order group to Boot Bus Extender
and placing its tag into begginning of the list does the job pretty
well. At least until recently.
Well, in our company universe, there exist one laptop, running Windows
10 1803, that makes an exception. It seems that the measures described
in the previous paragraph are not enough. So, is it possible to do
anything else to assure our driver will be initialized like one of the
first? Or maybe, there is an UEFI settings forcing Windows to
pre-load/pre-initialize some of its drivers earlier? We actually do not
need to be really the first driver to initialize but we need to be "in
Does ELAM help in this case? Anyway, I expect it requires some extra
signing compared to regular drivers.
Of course, I can make our driver a lower filter of a device class like
HDC but I would really like to avoid this since it makes the driver
mandatory for successful boot of the machine.
Thank you for any suggestions.