Hello,
Licensing and redistribution agreement is one reason.
The setup.exe does other things the INF can't do.
Also, as the driver does NOT send (installation) ANY metrics to DisplayLink server, we can't know the size of deployments to prioritize work if we don't get any data.
I already receive technical support tickets with people not sure what driver they should download for Windows when there is only one.
I do not have the intention to add drivers most users don't care about and confuse more people, creating unhappy end users and more tickets to reply to.
It is not up to the user to care about what build of Windows is running: one executable that does what is needed.
DisplayLink driver does NOT have any kernel mode component of the driver on Anniversary Update onwards, so something else is BSoDing or the wrong driver was installed (proving my point above). You would have to analyse the memory dump to give what is crashing, but you've already demonstrated it doesn't work anyway
Knowing which element is creating the BSoD is unlikely to be enough to make things work, especially if the OS doesn't allow you to manage displays.
Kind regards,
Alban
|