DisplayLink drivers plus McAfee application control aka Solidcore

[Boyd]

Hello,

having major problems getting DisplayLink drivers to function without errors while using McAfee Application and Change Control software v7 (aka Solidcore) on Windows 10 Surface Pro devices.

What it comes down to is that each application seems to reference or call the DisplayLink driver in a slightly different way, using a different parent process name. This means that once you fix one driver issue by whitelisting a DisplayLink DLL to resolve one scenario, (eg dlumd9.dll, dlumd10.dll, dlumd11.dll, dlumd32.dll or dlumd64.dll), once you then open another application which calls a DisplayLink DLL in a different way, another error is generated (a DisplayLink driver DLL is blocked by Solidcore).

We've whitelisted multiple DisplayLink executables, parent processes, DLLs, and MSI files that make up the DisplayLink driver package (and there seems to be about a bazillion of them!), however are continuously running in to blocking issues when in Solidcore Enabled mode.

What we need is some very detailed technical information from DisplayLink about how the driver functions at a very low level, eg a flow diagram describing the decision tree it uses and actions taken when a DisplayLink dock is connected, so we know what we can whitelist to make this driver work with any application without having to whitelist a DLL one by one every time we find a new issue (which is now a daily occurrence).

We've had multiple McAfee support tickets open which have resolved individual issues one by one, however we keep having to open a new case each time because each scenario is different, and we can't seem to track down one whitelist rule which will stop everything from erroring.

I've just logged a help request through the DisplayLink website, and also emailed technical_enquiries@displaylink.com for help, so will see if I get any feedback from that.

Any help would be appreciated if anyone else has encountered this issue.

[AlbanRampon]

Hello Boyd,

You will not get details on how our driver work posted on a public forum. Competitors will be looking for that information to try and gain market share on the leader.
How it works also depends on the OS you have and the graphics hardware. Finally how it works also depends on which application is calling because the different applications use the graphics subsystem differently. The same way they use the Intel/nVidia/AMD... graphics differently.
This means that how it works also has to evolve from one version to the next!

Please note that McAfee also blocks the addition of network adapters.

Kind regards,
Alban

PS: A bazillion files...