V7.9 Display Link Drivers wont install on Windows 10

[Marty]

Hi,
I have upgraded to Windows 10 and tried several times to install V7.9 of the DisplayLink drivers with no success. I am using a Targus USB3 Universal Dock with power (ACP71AU). I have used the cleanup tool to remove the version that was installed with my Windows 8.1 installation (v7.7). But when installing I get the error message, "DisplayLink Core Software setup was interrupted..."
I have attached the results of the Displaylink Support tool.
Any help would be most appreciated.
Thanks,
Marty

[JamesH]

Hi,

Please try the first section of this FAQ:
http://support.displaylink.com/knowledgebase/articles/679177-troubleshooting-software-installation-upgrade

Thanks,
James

[Marty]

Hi James,
Have tried all of this and just can't get the driver to even install.
Marty

[sbeilfuss]

Hi,

Please try the first section of this FAQ:
http://support.displaylink.com/knowledgebase/articles/679177-troubleshooting-software-installation-upgrade

Thanks,
James

We have 3 separate machines here that also do the same thing. One Toshiba z20t, one Surface Pro 3, (and I need to get the detailes of the 3rd). The z20t was a Insider Preview upgraded to final code, the Surface Pro 3 was a Win8.1 system upgraded to Win10. All running Win10 Enterprise.

Just as the others, I have run the cleaner, tried manual cleanup, ran both the general EXE download, as well as the corporate IT MSI packages. The EXE gives the above mentioned errors, the MSIs run for a while quietly - but in the end - the drivers are not there.

[sbeilfuss]

OK...I did what I should have done a couple tries ago...I added the logging switch to the msiexec command-line - looks like it is the Powershell Execution policy! Looks like the installer kicks off an Powershell script that is un-signed. In a corp environment where we have our PowerShell policy set 'safe' and only allowing signed code - this is going to be an issue.

=== Logging started: 8/6/2015 22:23:23 ===
Action start 22:23:23: INSTALL.
Action start 22:23:23: AI_ResolveKnownFolders.
Action ended 22:23:23: AI_ResolveKnownFolders. Return value 1.
Action start 22:23:23: AI_DATA_SETTER_33.
Action ended 22:23:23: AI_DATA_SETTER_33. Return value 1.
Action start 22:23:23: VerifySupportedOs.
Dumping PowerShell invoke log ...
--> Found PowerShell path: C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\powersh ell.exe
--> PowerShell Script Execution Result Code: 1
--> PowerShell Script Execution log:
File C:\Users\sbeilfuss71920a\AppData\Local\Temp\pss8D2 6.ps1 cannot be loaded. The file
C:\Users\sbeilfuss71920a\AppData\Local\Temp\pss8D2 6.ps1 is not digitally signed. You cannot run this script on the
current system. For more information about running scripts and setting execution policy, see about_Execution_Policies
at http://go.microsoft.com/fwlink/?LinkID=135170.
+ CategoryInfo : SecurityError: (:) , ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnauthorizedAccess
CustomAction VerifySupportedOs returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 22:23:25: VerifySupportedOs. Return value 3.
Action ended 22:23:25: INSTALL. Return value 3.
MSI (s) (D8:4C) [22:23:25:615]: Product: DisplayLink Core Software -- Installation failed.

MSI (s) (D8:4C) [22:23:25:617]: Windows Installer installed the product. Product Name: DisplayLink Core Software. Product Version: 7.9.296.0. Product Language: 2057. Manufacturer: DisplayLink Corp.. Installation success or error status: 1603.

=== Logging stopped: 8/6/2015 22:23:25 ===

[JoeyM]

I followed the instructions and uninstalled DisplayLink, did the cleaner process... downloaded the latest DisplayLink software but it won't install. See attached image for error. Any suggestions?

[sbeilfuss]

OK...confirmed for my case, this was our Powershell security policy (setting Powershell Execution Policy to "AllSigned"). After getting the guys to security exclude me from the policy (reverting default Execution policy of "Remote Signed") - this installed no problem.

=steve

[Niels]

I can confirm this is the issue.

After turning off the execution policy we could install the drivers without issues.

I wrote this script to make it easier.

Set-ItemProperty -Path HKLM:SOFTWARE\Policies\Microsoft\Windows\PowerShel l -Name Executionpolicy -Value Unrestricted
\\fileserver\share\DisplayLink_7.9M0.exe -silent -noreboot
Set-ItemProperty -Path HKLM:SOFTWARE\Policies\Microsoft\Windows\PowerShel l -Name Executionpolicy -Value allsigned