DisplayLink DL-1x0 or auto install devices do not work in Windows 10 Anniversary

[AlbanRampon]

Hello everyone,

For those who have a very old product (DL-1x0 chip), including products with PID 0x01AE, these chips were end of lifed 8 years ago but we will have a fix available. You may understand our priority was not to test on end products which were designed so long ago that Windows 10 wasn't even dreamed about...

People with PID 0x01AE, please ask for a development build in your technical support ticket (details on how to create a support request in my signature). Everyone, attach a zip of your log files and do explain the behaviour you are having. We won't send a development build if your issue may be elsewhere. The development build is being prepared on Monday.
If you don't give all the information, then it will take more time because we will have to ask for it.

Older drivers are being removed when you upgrade to the latest Windows 10 build 14393 on purpose. We have changed the driver architecture to take benefit of the brand new DisplayLink USB graphics native support in the new Windows. So we deliberately added a migration blocker in the OS. "DisplayLink Manager" service is also removed because it is not needed anymore as the OS gives us all we need.
Sometimes the migration blocker doesn't work properly. If you are having issues, before creating a support ticket, please do the following:
1. Disconnect all devices using DisplayLink technology
2. Remove your corrupted installation using our End User Cleaner. You MUST execute it with "Run as administrator..." even if your user has admin privileges because Windows doesn't ask in about 1% of the installations.
3. Reboot
4. Connect the devices using DisplayLink technology. It will fetch what is needed from Windows Update.


The new driver had thousands of working installs before the Windows 10 anniversary update was rolled out generally. Otherwise, Microsoft would not have agreed to have that driver on Windows Update for their brand new Windows feature at general availability/RTM...

The main benefit of the new native DisplayLink USB graphics support in the OS are:
- lighter driver
- no dependency on the primary graphics card driver so now even compatible with the Windows 10 basic driver
- seamless upgrade: no need to reboot for an update or even first install. No flashing. Of course, out of the millions of devices plugged in to Windows computers, there is a percentage of Windows OS upgrade not happening properly.

Any other specific question, please ask in a new thread for clarity.

Kind regards,
Alban

[MadeforVermont]

Hi, I am definitely having this problem after upgrading to the Windows 10 Anniversary update. My Plugable UD-3000 worked perfectly with my HP L2245wg display and ethernet adapter. Now, I have constant issues with the ethernet dropping and switching back to wireless, and the display dropping it's connection. The only way to fix it is to unplug the power from the Plugable docking station. I did update all drivers available. bios, graphics, chipset, wireless. I uninstalled the display port software ran the cleaner, unplugged everything and shut down. I then plugged everthing back together and started the computer. It did install the display port using the windows software, but not I am having constant problems. Thanks for looking into this.

[dsa]

Hello Support,

Instead of belittling your long-time customers with condescending nonsense like this...

Originally Posted by AlbanRampon

For those who have a very old product (DL-1x0 chip), including products with PID 0x01AE, these chips were end of lifed 8 years ago but we will have a fix available. You may understand our priority was not to test on end products which were designed so long ago that Windows 10 wasn't even dreamed about...

perhaps you should fully test the products you state are supported in the release notes for your latest driver packages.

I have the same issue as others on Window 10 AU and understand that sometimes there are challenges with older hardware but don't talk down to your loyal users in the forum while at the same time stating in driver releases that their hardware is supported.

From the 8.0M1 Release Notes:

H. Supported Hardware
=====================
Devices supported:
- DL-6950
- DL-5500 / DL-5700 / DL-5900 / DL-5910
- DL-41xx
- DL-3100 / DL-3500 / DL-3700 / DL-3900 / DL-3950
- DL115 / DL125 / DL165 / DL195
- DL120 / DL160

[jacklabombe]

I agree with DSA. I am managing a room full of these DL-1x0 chips (PID 0x01AE) and operated flawlessly until this Windows 10 Anniversary story.

Displaylink, please resolve this ASAP I need this working by the end of the month!!!

[lawrence.kerr]

Waited for the updated driver release from DisplayLink and the same story, the usb gets found but driver fails to initialise. Have a small team full of these devices; upto 16 purchased from Maplin Electronics most inside the last 6 months as they did work with Windows 10. At approximately £50 each that is £800 which we just don't have the budget to replace this year. Currently have Anniversary Update deferred but some workstations already updated. Between DisplayLink and Microsoft you need to get your acts together.

PS I don't care about the 200 Billion devices you claim to have working with Anniversary Update but I do care about the 16 devices that consistently show the same error.

[rcorradini]

I agree....This is not fixed...I have 4 of these devices and all not working after win10 anniversary update on 2 different machines....When are you going to fix for the rest of us?

[Wim]

Hi All

There are multiple issues being discussed in this thread. I understand the frustration that your devices no longer work and we are fixing this. To summarise, there are 2 problems in this thread:

There are devices based on the DL-1x0 family, originally made for Windows XP but we are still committing to supporting these devices. I suspect there are not many PC components you bought for XP and can still download the latest Windows 10 drivers for. We needed to get a driver out for Windows 10 Anniversary edition and support for these devices was something that was cut to make the date.

However we do have a fix, and these devices will be supported from 8.0 M2, released at the end of August. If you contact us at http://support.displaylink.com we can make a development build available now.

The other problem in this thread are devices that switch to mass storage, to auto install drivers. This affects a small number of products that have been available and is a more complex fix, as it is trying to make a device work that was never designed for Windows 10. We want to fix this in a release soon, but don't have a fix or a schedule yet.

I'm going to close this thread and make the subject fit the actual root cause before it turns into a dumping ground for many different problems that people are finding with Windows 10 Anniversary update.

Thanks

Wim