DisplayLink Forum - View Single Post

KBL · 08-20-2013, 11:55 AM

Hi James,

I have tried that a few times, with the same result.

I have noticed something that I think may be causing the problem though....

The driver that the new update is trying to replace is version 2.01.032 replaced with 2.1.36.0.
However, I have noticed that the current driver installed is 2.0.32.0. I therefore assume that as the expected driver is not present it is not completely the correct update.

I will now try to update 2.0.32.0 with 2.01.032 before trying the final update.

Fingers crossed.

KBL

Well this is puzzling, I can't find any reference to 2.01.032 online really.

08-20-2013, 11:55 AM	#7
KBL Junior Member Join Date: Aug 2013 Posts: 13	Hi James, I have tried that a few times, with the same result. I have noticed something that I think may be causing the problem though.... The driver that the new update is trying to replace is version 2.01.032 replaced with 2.1.36.0. However, I have noticed that the current driver installed is 2.0.32.0. I therefore assume that as the expected driver is not present it is not completely the correct update. I will now try to update 2.0.32.0 with 2.01.032 before trying the final update. Fingers crossed. KBL Well this is puzzling, I can't find any reference to 2.01.032 online really. Last edited by KBL; 08-20-2013 at 12:37 PM.