As we know we cant use coinstallers in inf files anymore, a strange decision since they have been around since time immemorial, so what is the suggested replacement?
We were calling wevtutil im in a coinstaller, are we supposed to use an exe from now on, ie, this is the death of inf only driver installs?
Very surprised at this change, it is a big loss of functionality for no reason that I can see!
Apparently you are supposed to use the AddSoftware directive to connect a UWP app downloaded from the microsoft store to your driver. There is so much wrong with that I don’t know where to start. Personally I would go the other way and use a legacy msi installer to install both the driver and whatever win32 based application support you need.
It’s been enough months since I did this that I’m unsure of it, and I am no longer at AMD to check what I did, but I think that this: (https://learn.microsoft.com/en-us/windows-hardware/drivers/install/inf-addeventprovider-directive will get you where you want to go (eventually).
There is so much wrong with that I don’t know where to start
This. So, totally, this.
Yes, the AddEventProvider is the replacement for calling wevtutil
As for AddSoftware, you can package an executable with your driver to be executed (type 1), or specify a link to something in the store (which can be UWP, win32, or whatever else the store allows) which will be automatically downloaded and installed (type 2). One note is that certain SKUs or product types may not execute type 1 installs, so we recommend using type 2 if possible.