Windows 10 postponed installation not working

[buerkli]

Hello,

When i run "msiexec /i %SETUP%\DisplayLink_Win10RS.msi /norestart /quiet" without docking connected, everything works fine. The DisplayLink Manger and the graphics driver are udpated immediately.

If i execute the command with the docking station connected , only the DisplayLink Manager is updated to V9.1, the graphics drivers stays on V8.6 (even after a reboot).

I cannot find any log in C:\Windows\Temp\ called PostponedDriverSwap*.log.

Kind regards

[astruzyna]

Hello,

Our Engineering team asked if you could check a few things:

1. Please check if PowerShell, Task Scheduler and Events Log are available.

2. Please go to C:\Program Files\DisplayLink Core Software and check if Driverswap powershell script and PostponedDriverSwap application exist in this folder

3. Please check if the tasks DisplayLink_DriverUpdate_Boot and DisplayLink_DriverUpdate_PnP are present and active in the Task Scheduler

4. Please run the msiexec command with /l*v argument in other to generate the msi log and send that to us

DisplayLink logs are saved in the TEMP/TMP system variable. Please look for the log in this location.

Please attach the logs to your reply, Thank you.

Kind regards,
Aga

[buerkli]

Hello,

I think we found the failure:

In the log of the .msi file you can find this error:

"MSI (s) (B4:CC) [13:41:07:113]: Invoking remote custom action. DLL: C:\Windows\Installer\MSICE26.tmp, Entrypoint: RunPowerShellScript
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:
Die Datei "C:\Users\Testuser1\AppData\Local\Temp\pssCE2B.ps1 " kann nicht
geladen werden. Die Datei
"C:\Users\Testuser1\AppData\Local\Temp\pssCE2B.ps1 " ist nicht digital
signiert. Sie k”nnend dieses Skript im aktuellen System nicht ausf�hren.
Weitere Informationen zum Ausf�hren von Skripts und Festlegen der
Ausf�hrungsrichtlinie erhalten Sie in "about_Execution_Policies" unter
"http://go.microsoft.com/fwlink/?LinkID=135170"..
+ CategoryInfo : Sicherheitsfehler: ( , ParentContainsErrorRe
cordException
+ FullyQualifiedErrorId : UnauthorizedAccess
CustomAction PreparePostponedDriverSwap returned actual error code 1603 but will be translated to success due to continue marking"

Our Powershell execution policy is set to "AllSigned".
If we change it to "RemoteSigned" everything works fine. But we are not allowed to change this setting on all machines.

Can you advice us how to solve this problem?
Kind regards

[astruzyna]

Hello,

Thank you for your feedback. Solution to this issue is planned for our next 9.2 driver where we will no longer use PowerShell scripts. We will let you know when an alpha/beta driver is available so that you can test the fix. Thank you for raising this issue with us.

Kind regards,
Aga

[buerkli]

Hello,

Thank you very much for your support.
We are looking forward V 9.2

Kind regards

[astruzyna]

Hello,

We have released an Alpha version of our 9.2 driver.

This is the first public preview of DisplayLink driver 9.2 for Windows. It has undergone limited system tests and is only suitable for beta testing, to evaluate the software.

9.2 Alpha delivers:
- Improvements to Windows 10 postponed installation: when pushing the MSI to users, driver will be updated straight away if no DisplayLink product is detected, or at the next machine reboot if a device is detected:
--- Now available for Windows 10 .exe,
--- For .msi: Task Scheduler is now replaced by Service.

9.2 Alpha .msi for testing of postponed installation features.

Please test it and let us know your feedback. Thank you.

Kind regards,
Aga

[astruzyna]

Hello,

Our 9.2 M0 driver is now available with Postponed Installation on Windows 10.

Driver version 9.2 M0 onwards removes user interruption caused by driver updates (temporary loss of video, audio and Ethernet during driver swap) while the users are working with their dock on their machines.

From now on, IT can now centrally distribute the driver to all clients and when the MSI driver executes:

• Driver will be updated straight away, if no DisplayLink product is connected,
• Driver will be updated at the next machine reboot/plug-unplug, if DisplayLink device is detected in use.

The feature requires following Windows components:

• Windows Service

Power Shell is no longer required.

Please let us know if your issue with Postponed Installation has been resolved with this driver version. Thank you.

Kind regards,
Aga