Windows 10 Driver Issue

[zburns]

I'm running 7.9M0 on a Windows 10 RTM (running on a MacBook Pro) via BootCamp. So it's an odd configuration, but works, except for the Pluggable DisplayLink device.

It did work for a bit, then the screen went blank. Couldn't get it to come back. So I did the EndUserCleaner and reinstalled the 7.9M0 drivers again and it just never picked up the device.

It's not a cable issue. If I boot into Mac with the Mac 2.x drivers - I have no issues. Everything works as it should.

I followed the debugging steps on the Windows 10 side...

1.) Display Link Software 7.9M0 is installed
2.) Display Link Service is running
3.) Display Link USB device Manager DOES NOT show in the device manager, but it shows a high speed 3.0 USB hub that has an ESET (my virus scanner) driver attached to it also - could this be an incompatibility?
4.) The product ID of the device is: USB\17E9.....

Does this make sense?

Zack

[zburns]

I also have pictures of the problem in the USB area...

http://www.zackburns.com/files/public/tmp/dl1.jpg

http://www.zackburns.com/files/public/tmp/dl2.jpg

http://www.zackburns.com/files/public/tmp/dl3.jpg

http://www.zackburns.com/files/public/tmp/dl4.jpg

http://www.zackburns.com/files/public/tmp/dl5.jpg

[JamesH]

Hi,

Could you try reinstalling with the ESET software disabled?

Thanks,
James

[zburns]

I completely removed the Display Link software (using the End User Removal tool). Then rebooted.

I complete removed the ESET Antivirus software. Then rebooted.

Left DisplayLink device unplugged. Installed software 7.9M0 and plugged in the DisplayLink device when prompted at first start - nothing happened. Nothing has been happening every time except for the very, very, very first time.

So I clicked Skip

The software prompted a reboot, so I did so.

Partial items detected, but the network and video still didn't work. Just the USB connected keyboard, mouse and iPhone was detected via USB.

Also note the item in the USB says the following and now does NOT have a link to the ESET driver. Just the standard microsoft driver.

VID=2109
PID=0811
REV=3198

[zburns]

Just downloaded 7.9M2 - released today and went through the above steps and .... no dice. Still doesn't work.


Checking the error log I still see the Microsoft USB 3 driver stopped because the device reported a problem. :confused:

[zburns]

I'm also reading that people have done the following in the technical preview (not RTM) that removal of all the DisplayLink software, running the cleaner, then rebooting, and taking the Windows Update version of the driver helps, but I haven't tried it. Is this "sanctioned" by DisplayLink?

[zburns]

I so desperate I tried the Windows driver approach, but it said I was using the most up-to-date driver (even as of Microsoft's recent cumulative update today - KB3081448).

I went looking for other types of docking stations that I could purchase, but looks like they all use DisplayLink drivers, etc. So kinda scared to purchase anything from any other vendor.

If anybody (or even support) can figure this out, I'd appreciate it.

[JamesH]

Hi,

Thanks for the additional information.

Some further questions:
1. Has the docking station ever worked?
2. Do you have the latest version of ESET installed? http://support.eset.com/alert49/
3. Can you attach the output from this tool:
http://support.displaylink.com/knowledgebase/articles/533818-how-can-i-report-issues-to-displaylink

Thanks,
James

[zburns]

Answers to your questions:

1.) Yes on a Lenovo Yoga Pro 2 (under Windows 8.1)
1.) Yes on a MacBook Pro Retina 2015 (under Mac OS 10)

2.) Yes ESET is current - version 8.0.319.0
2.) Also tried with ESET disabled AND removed - same result

3.) Attached - I uploaded one before I connected and after I connected the DisplayLink docking station.

Thanks for your help.

[zburns]

FYI - I'm also working with Pluggable on this also - I'll report back.

[zburns]

Well, I worked with Plugable and they've stated that it's a hardware issue. The unit was purchased back in October 2013 (no hardware version number on unit). I tested with another unit (hardware version REVB2) purchased in September 2014 and this works perfectly. No issues.

:):):):):):):):):):):):)