7.1 M0 moves all open windows to internal display after standby resume

LatencyMachine · 01-11-2013, 01:59 PM

[Toshiba Dynadock 3. HP M7-1015DX. Core i7 w/HD4000 gpu. Win7 x64]

After updating to 7.1 M0, my multiple monitor window layout is lost upon resuming from standby. What happens, is that any windows that were present on the DisplayLink monitors are all shoved over to the laptop's internal display.

Being a software developer I always have several windows open, such as debuggers, source code editors, reference material, etc, that are usually carefully laid out. It is a nuisance to lose this every time I go into standby.

Please look into this issue, and let me know if there is anything further I can contribute to help you reproduce the issue.

Dan · 01-11-2013, 06:45 PM

Can you provide some logs after sleep/resume? It sounds to me like your devices are reenumerating which could cause the problem you are seeing.

If the OS sees displays go away, the windows will snap back to the primary.

There have been quite a few issues with S3 causing VBUS pulses on some systems.

Our report tool can be found here: http://www.displaylink.com/support/ticket.php?id=269

01-11-2013, 01:59 PM	#1
LatencyMachine Junior Member Join Date: Jan 2013 Posts: 4	7.1 M0 moves all open windows to internal display after standby resume [Toshiba Dynadock 3. HP M7-1015DX. Core i7 w/HD4000 gpu. Win7 x64] After updating to 7.1 M0, my multiple monitor window layout is lost upon resuming from standby. What happens, is that any windows that were present on the DisplayLink monitors are all shoved over to the laptop's internal display. Being a software developer I always have several windows open, such as debuggers, source code editors, reference material, etc, that are usually carefully laid out. It is a nuisance to lose this every time I go into standby. Please look into this issue, and let me know if there is anything further I can contribute to help you reproduce the issue.

01-11-2013, 06:45 PM	#2
Dan Banned Join Date: Nov 2009 Posts: 104	Can you provide some logs after sleep/resume? It sounds to me like your devices are reenumerating which could cause the problem you are seeing. If the OS sees displays go away, the windows will snap back to the primary. There have been quite a few issues with S3 causing VBUS pulses on some systems. Our report tool can be found here: http://www.displaylink.com/support/ticket.php?id=269