Windows 10 1607 black screen after update

[AlbanRampon]

Originally Posted by tlh119

The device is a Toshiba Dynadock-U and there are no mass storage devices plugged into it.

Thank you Tlh119, you have actually a third thing! You have a custom device supporting a special resolution for Thosiba.
I've added your logs for investigation to understand this device. As it's from 2007, it is not too fresh in anyone's memory so not sure what we can do yet.
Please keep an eye on the future Release Notes for ID 23485 in case I don't report progress here.

[tlh119]

Originally Posted by AlbanRampon

Thank you Tlh119, you have actually a third thing! You have a custom device supporting a special resolution for Thosiba.
I've added your logs for investigation to understand this device. As it's from 2007, it is not too fresh in anyone's memory so not sure what we can do yet.
Please keep an eye on the future Release Notes for ID 23485 in case I don't report progress here.

Thank you. I will hold off rolling back for now so if there is anything else I can do to help, let me know.

[NedFlanders]

Originally Posted by AlbanRampon

Thank you Tlh119, you have actually a third thing! You have a custom device supporting a special resolution for Thosiba.
I've added your logs for investigation to understand this device. As it's from 2007, it is not too fresh in anyone's memory so not sure what we can do yet.
Please keep an eye on the future Release Notes for ID 23485 in case I don't report progress here.

I am in the same boat. I also tried R8.0 M2 unsuccessfully (I have a Toshiba Dynadock-U as well). I still have my Windows 7 work laptop connected to Dynadock as is my desktop running Windows 10. I am still using the dynadock to connect to my mouse and keyboard on the Windows 10 machine but ever since the last windows cumulative update when I switch my USB port to the dynadock - windows (on my Win10 machine) is reinstalling the displaylink driver and this grabs the monitor before my video card can so I end up with the blank screen until I fire up my second monitor and switch to it long enough to get into device manager and uninstall or disable the display link driver and then back to my main monitor.

I am going to keep this up for a little while longer, but the Toshiba Dynadock might find itself flying through the back yard in a week or two if this keeps up.

[AlbanRampon]

Hello Ned, and all,

# Release Notes and Tracking Numbers
The Release Notes are the text file indicating changes between releases.
Next to the download, you have a text icon linking to them.
The ID 23485 is the internal tracking number under which reference this particular item is handled.
For instance, if you take 8.0 M2 Release Notes you will see the first item talks about Dell Display Manager and has (22933) at the end of the line.

# Product Obsolescence
DisplayLink does not design, manufacture, or sell any end product. We are a semiconductor vendor. What is in the end product by reference is not known to us until you send me the logs for that device. The manufacturer may change their design without notifying us, we are just one of their many suppliers of components.
Initially affected have been some products DisplayLink stopped selling 8 years ago, but not all of them are. DisplayLink stopping selling a chip does NOT mean the product is end of support because it's not DisplayLink who is responsible for the support, but the people making the devices: they may have million of spares and therefore continue support it. This is the same way nuclear plants have spare devices for the life of the plant, decades after the silicon vendor has stopped building the chips.

# Anniversary Update
What we have today is a very particular case: new operating system, with new way of doing things... which is now standard. The graphics subsystem of Windows 10 Anniversary Update is new, the fact Microsoft stopped increasing the 10 should not be believed it's the same version. The same way Apple releases a new Mac OS 10 every year.
I know it's not really helpful to solve everything, but that's what we have.

So let me summarise the current status, now we have 8.0 M2 issued.

# What Started Working Again on 8.0 M2 and Windows 10 builds >10586
1. Devices Based on DisplayLink First Generation Chip
DisplayLink stopped selling these chips about 10 years ago. I hope you can understand the priority was to support recent products. I am still adamant most companies wouldn't even bother about such old products, yet we have made them work again on 8.0 M2 because we want our products to work as long as we economically can!!!
These products work differently and are not firmware upgradable. Provided the implementation used doesn't have mass storage, then these now work again on 8.0 M2. I talked with my colleague and I'm changing the knowledgebase article to be clearer on this.

# What is Still Not Working With 8.0 M2, Only on Windows 10 builds >10586
1. Devices with mass storage or auto-install
This is not a particular DL-xxx reference because it's nothing to do our chip, it's the implementation chosen by the manufacturer. To answer your question about choice Ned, the only product listed on our website affected is the Diamond Multimedia WPCTPRO.
We currently don't have a workaround.

2. Toshiba Dynadock model circa. 2007
These devices are custom to enable higher resolution than their previous generation. We are looking into it now we have a reproduction of the issue.
The products affected have the Hardware ID USB\VID_17e9&PID_0113 (see in Device Manager).
Older products under that same commercial name under Hardware ID USB\VID_17e9&PID_0110 will now work on 8.0 M2.
Please don't throw it through the garden just yet...
Depending on the results of the investigation, I will be able to let you know if/when we can deliver something to address this. I expect a developer to start the analysis today.

# Summary
I hope you take my transparence in the spirit intended: we are working through the different items we can, and reporting things we can't handle ourselves to who can do something about them.
Unfortunately, I don't have unlimited engineering resources in my hands, therefore I have to prioritise what our customers request me to do with with the rest.
Everyone's feedback here has been key for me to understand how I prioritise the engineers' work, so thank you for taking the time to report your issues as otherwise they might not have been looked at: we can't fix something we don't know is a pressing issue.

Kind regards,
Alban

[AllenL]

I have installed 8.0 M2 on a clean machine and cannot get anything other than a black screen as well.

I have several HP HSTNN-S01X docking stations that are now just USB hubs because the DisplayLink drivers do not work.

Please assist if possible.

[AlbanRampon]

Hello Allen,
From the Device Manager, it looks like you have a "HP USB DOCK USB Device" with auto-install instead of the DisplayLink mode.
Can you check?
If that's the case, then you are hitting the limitation there is with the Win10 USB driver mentioned in this thread.
Kind regards,
Alban

Originally Posted by AllenL

I have installed 8.0 M2 on a clean machine and cannot get anything other than a black screen as well.

I have several HP HSTNN-S01X docking stations that are now just USB hubs because the DisplayLink drivers do not work.

Please assist if possible.

[RichardL]

Hi - I have just suffered the Windows 10 Anniversary update and have the black screen. My product has Hardware ID USB\VID_17e9&PID_0113, for which I understand a fix is being worked on. As and when this problem is resolved will you send the people on this thread an email to let them know?
Thanks and Good Luck
RichardL

[Pstocks]

Hi:
Any update on the dynadock fix yet please. I have been without the ability to use my additional monitor for a week now.
Thank you for your support.
Pete

[AlbanRampon]

Hi Pete,

The Toshiba Dynadock-U has been re-enabled for a couple of weeks now.
This article talks about this: http://support.displaylink.com/knowl...10-anniversary
And the email address to explain what you wish, providing the log files is in my forum post signature.

Kind regards,
Alban

[bernard23]

Hi Alban,

I have the same issue as well for my Windows 10 HOME Anniversary Update.
After installing the latest 8.0M2, the USB device keeps on turning on and off once I power up the WPCTVPRO. The USB device and the receiver will try to connect with each other for few seconds but will disconnect, and it will go on and on but the connection will not be stable.
In device manager, samsung host ready usb device, will always show under disk drives, even though i already turn on the receiver, on which the usb device suppose to switch to a Display adapter once the receiver is on.
Please see the attached logs of my computer for your further info.

Thank you and I hope that there will be a fix to this problem of mine.

PS. I've tried every suggestions in the forum and in support page but up to date i still can't work my WPCTVPRO to my Windows 10 desktop.