MicrosoftFabrizioDegni exactly, currently anyone can get any garbage drivers certified because Microsoft don't have access to source code. I even tested that by publishing this: https://github.com/olljanat/BlueScreenOnce (Windows certified driver which purposely causes blue screen). However, I don't believe that all the experts on this are working for Microsoft and anyway it is just wasting resources to build multiple drivers for same purpose like case is now when every EDR vendor build their own driver which why I'm proposing to open source this part. EDRs can then still compete with their user mode parts.
jdrch I mean drivers which are needed by EDR products. Veeam does not directly belong to that category but I see that also their CBT driver is using StartType=0 like EDR drivers do. That probably should be denied and replaced with new start type which also makes sure that driver normally get started also in safe mode (which I believe is reason to use StartType=0) but which allow Windows to skip driver in case it prevents system from starting. Then only real boot critical disk, etc drivers would use StartType=0.
