[bernie]

Thanks for the additional info. The fact that McAfee used to be on this machine leaves open the possibility that this machine is still affected by the known McAfee bug where it leaves vbscript disabled, even after uninstall. Disabling or uninstalling McAfee won't bring vbscript back in these cases - McAfee has changed the Windows Registry to have vbscript point to a dummy dll.

Unfortunately, I see McAfee has changed or moved their download page for their "McAfee Consumer Products Removal Tool" cleanup tool.

Another quick way to check if vbscript is disabled, is to run this simple command from a command line. If vbscript is enabled it will return "vbscript enabled":
echo Wscript.echo "vbscript enabled" > test.vbs && cscript test.vbs

If it returns an error, vbscript is still not enabled on this machine.
If it returns "vbscript enabled" then DisplayLink's installer must have some extra dependencies.

Would you be able to run this line? And does it report vbscript enabled, or some other error?

Thanks for this help in understanding what you're seeing!