DisplayLink Forum - View Single Post

GBurt · 08-06-2020, 03:39 AM

Same. We've been using the DisplayLink MSI packages with more-or-less this (current) argument from our app deployment system for over a year now. This one gives 1603, every time. Test environment was 5 different HP laptops (elitebooks, X2G2 & others) running Win10 1909 with July patches.

It is launched by System user, to avoid UAC

${WinSysDir}\msiexec.exe /i c:\Temp\DisplayLink\DisplayLink_Win10RS.msi /norestart /qb /lv c:\ProgramData\NSW\DisplayLink\install-log-9-4-m0.txt

I've also tried manually running the MSI. Same deal, 1603.

Exe install works fine mind you. Does anyone have some silent arguments for that as a stopgap? Otherwise I think I'll just ignore this version pending further notice.

08-06-2020, 03:39 AM	#3
GBurt Junior Member Join Date: Aug 2020 Location: Australia Posts: 1	Ditto Same. We've been using the DisplayLink MSI packages with more-or-less this (current) argument from our app deployment system for over a year now. This one gives 1603, every time. Test environment was 5 different HP laptops (elitebooks, X2G2 & others) running Win10 1909 with July patches. It is launched by System user, to avoid UAC ${WinSysDir}\msiexec.exe /i c:\Temp\DisplayLink\DisplayLink_Win10RS.msi /norestart /qb /lv c:\ProgramData\NSW\DisplayLink\install-log-9-4-m0.txt I've also tried manually running the MSI. Same deal, 1603. Exe install works fine mind you. Does anyone have some silent arguments for that as a stopgap? Otherwise I think I'll just ignore this version pending further notice.