Multiple Display configuration lost after resume from sleep
 

I've got the Anker USB 3.0 Dual Display Universal Docking Station running on Asus N56VZ laptop with Windows 8.1. I have my laptop connected to three external displays (laptop HDMI, laptop VGA, and display link DVI), and I keep the laptop's native display turned off. The display link performs well during regular use. However, I experience a problem when my monitors go into standby (after 5 minutes of inactivity) and then are activated again (by mouse or keyboard activity). Normally my external monitors continue to display my desktop exactly as I left it. But with the display link monitor connected, after resuming from standby *all* my external monitors remain in standby, and only my laptop native screen powers back on. Furthermore, my laptop becomes unresponsive for a good 15 seconds after resuming from standby, with the laptop monitor showing a badly scaled desktop screen during this time. Each time this happens, I need to reconfigure my multi-monitor screen configuration which is very inconvenient. **Note**, at no point is my laptop put in sleep or hibernation mode, only the monitors are powered down.

I've got all the latest video drivers and DisplayLink drivers installed. Attached is the debug files which include logging information during the monitor standby and resume cycle.

Is there a fix or workaround for this issue? In the meantime, I adjusted my power management settings so that my monitor is never powered off/put to standby.

Just installed the 7.5 M0 driver. Problem above still persists.

Hi,

I've raised a bug for this internally.

Do your USB connected monitors ever resume from monitor power save?

Thanks,
James

Yes, each of my displays work again after I manually reconfigure the multiple displays in windows. I found a quicker way to restore my multi display configuration in Windows 8.1: I press [Windows logo key]+P to bring up the Project sidebar options, then I select "Second screen only". I have to do this ever time I resume from sleep.

Thanks I've updated the bug with this info.

James

Happy to report that all the issues I reported in this thread are now resolved for me. Not sure what exactly fixed it, but I've recently updated to 7.5 M2 and also applied the Update 1 for Windows 8.1