Upgrading Windows 10 1511 to higher version with DisplayLink installed

[Cas]

What is the proper process on handling the installation of the DisplayLink Corporate MSIs when you upgrade from Windows 10 1511 to a higher version (1607 or 1703)?

I have been searching this forum but I have not found the answer I am looking for.
Currently we install the RS1 version of the Corporate MSI after the upgrade is finished, but on rare occasions after the MSI is installed, a process is started to remove the same version

Three log files have been found in %TEMP% either starting with DLC or DLP together with 2 tmp files starting with AIBB and the MSI GUID of the TH2 and RS1 Corporate MSIs.

Can some guidance be given on the upgrade process?

Thanks!
Cas

[AlbanRampon]

Hello Cas,

They use different DisplayLink drivers.
Windows doesn't really "update" from 1511 to 1607, it installs 1607 and then copy data over from the old install.
The old driver is removed, on purpose, when the flighting takes place.
Then, I imagine the computer received the new driver from Windows Update transparently.

Should these computers not have access to the Internet, then the process would be to do the OS upgrade, which will remove the old driver architecture, and then, when the new OS build is installed, install the new driver. Please note that the MSI is different for 1607 onwards than for the old Windows.

Kind regards,
Alban

[Cas]

Hello Alban,

Thanks for your response. I am aware of the way Windows 10 "upgrades", sorry for using the confusing terminology

The Windows Update driver update is disabled in our corporate environment, so the DisplayLink driver does not get installed via Windows Update.

We use the method you describe, 1607 "upgrade" is ready, then we run the RS1 MSI, so the TH2 MSI is left untouched on the machine, is this OK?
On some systems immediately after the RS1 MSI was succesfull, proof of this from the MSI log we create during install, another MSIexec process is started which removes the software again. We have been trying to figure out why, could one of the Custom Actions in the RS1 MSI cause this?

Thanks again,
Cas

[AlbanRampon]

Hi Cas,
I'll need to check with our dev the order of things.
I expect the RS1 MSI to neuter the TH2 driver, like it does with a WU install.
Would you have the logs on hand so I can have a look and consult?
Our customer support tool gathers this as described in my signature (3rd link).

I hope we did not forget to put the GUID in the Windows migration blocker list. The logs will tell me which MSI you are using, along with the SetupAPI Device/Application logs.

Kind regards,
Alban

[Cas]

Hi Alban,

Yesterday I have sent several logs to the mail address that is referenced in the third link, hope this helps.

Regards,

Cas

[AlbanRampon]

Hi Cas,
My colleague James will pick it up then.
As he was looking after IT deployments in a corporation before joining DisplayLink, he's got the experience needed here. I'll talk with him on Monday.
Kind regards,
Alban