Installation of DisplayLink Software fails

[kudustream]

Hi,

I'm trying to install displalink software 8.2 M3 (tried also M2) on windows 10 and when installation reaches registry writing it rolles back and says it was interrupted.

Please see logs attached.

Really counting on your help.

Thanks!

[AlbanRampon]

Hello,

I'm sorry to read there is an issue here.
There seems to be an issue with your driver store on Windows.
From the setupapi.dev.log, I can see the audio, Ethernet and video driver all fail with the following:

!!! sig: Failed to install catalog 'dlidusb.cat' as 'oem23.cat'. Error = 0x8E5E03FA
sto: {DRIVERSTORE IMPORT END: exit(0x8e5e03fa)} 21:06:31.689
inf: Opened INF: 'C:\WINDOWS\System32\DriverStore\FileRepository\dl idusb.inf_amd64_83dd40014b39272d\dlidusb.inf' ([strings])
sto: Flushed driver database node 'DRIVERS'. Time = 109 ms
sto: Flushed driver database node 'SYSTEM'. Time = 0 ms
sto: Rolled back driver package publishing.
sto: Rolled back driver package registration.
sto: Rolled back driver package import.
!!! sto: Failed to import driver package into Driver Store. Error = 0x8E5E03FA

Then, I look before and I can see from Line 4375 that the problem also occurs with Intel graphics driver.

I would recommend you check the disk, access rights, and try to repair the Windows installation as Error = 0x8E5E03FA is unlikely to come from both Intel and DisplayLink drivers.

[kudustream]

Hi Alban,

Thanks so much for your reply.

I'll really appreciate if you could me a clue where to look to change those access rights.

Thanks again

[AlbanRampon]

Hello,
I haven't seen this error before so it's a bit shooting in the dark with a water pistol to try to kill a fish. But, that aside, here is how I would personally start to look at it.

Windows has a tool which looks for corruption of system files. It doesn't always detect the problem and, even if it detects it, the tool doesn't always fix the issue.
The first step would be to check the drive doesn't have corruption.

1. Run a disk check.
In the Windows file explorer, right click on your system driver, then select properties, then tools, then Check. If there are errors, correct them and reboot. Then check there's none left.

2. Run the System File Checker tool
This is the Microsoft tool looking for system file corruption which might not find it. Here is the official way of using it. Here is the way to use it from a website I always advise to users as I find it very clear. I advise you choose Option 2.

There are other ways to add drivers to the driver store, but I doubt they will work.
I believe what you need first it to address this driver store corruption. I've seen that error mentioned when having issues with Windows Update (WU) components. I'm not sure how it could be relevant to you as you're not using WU here, but it could be that an update has locked the driver store, this I know is possible... Therefore, if all fails, you can go through the very manual process of going through the steps described in that Windows KB. The wizard did not solve my issues, so I recommend going the long way straight away... But my issue may have had a different root cause.

Kind regards,
Alban