Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Windows Software

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old 08-06-2020, 03:39 AM   #3
GBurt
Junior Member
 
Join Date: Aug 2020
Location: Australia
Posts: 1
Post 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.
GBurt is offline  
 

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 07:45 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.