Start menu opens behind other windows when no windows active on primary monitor (w/ Classic Shell)

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

Matt Davis

2 discussion posts

I'm having a strange problem using DisplayFusion with Classic Shell, it started when I upgraded to the Windows 10 Anniversary Edition.

Whenever I click the start button on my secondary monitor, the start menu is hidden behind all other opened windows on the monitor. I've noticed that it only happens when there is no active window on my primary monitor, but as soon as I close the last window or move it to my secondary monitor, the issue comes back.

I've tested this on a fresh installation with only DisplayFusion and Classic Shell installed, it only happens when both are being used together, on Windows 10 version 1607+

Is there anything that can be done about this?

Dec 14, 2016 • #1

Do you have auto-hide enabled on your taskbars?

Dec 15, 2016 • #2

Matt Davis

2 discussion posts

I do not currently, I have tried with that option both disabled and enabled, the issue persists.

Dec 16, 2016 • #3

Kendoka

9 discussion posts

I have this too. (I have a game in borderless windowed mode on the primary monitor)

It doesn't happen with the original start menu

Dec 16, 2016 • #4

I can't seem to reproduce this here. Could you guys attach debug logs? Here are the steps:

On the Troubleshooting tab, change the Logging drop-down to "L2: Log Detailed"
Reproduce the issue and note the time so we'll know where to check in the log file
Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
Disable debug logging after sending the log

Dec 20, 2016 • #5

Kendoka

9 discussion posts

I tried to open the start menu 3 times at 23:07, files are attached.

• Attachment [protected]: DebugInfo.html [154,479 bytes]

• Attachment [protected]: DisplayFusion.log [1,355,807 bytes]

Dec 21, 2016 • #6

Thanks! I don't see anything out of the ordinary in the logs. Could you attach a backup of your Classic Shell settings, as well as a backup of your DisplayFusion settings?

Dec 21, 2016 • #7

Direct1221

3 discussion posts

I have been getting the same issue since I upgraded to the Anniversary Edition of windows.

Only using the Taskbar out of DisplayFusion Pro (On Steam) 8.1.1 and Classic Shell 4.3.0

Here are the settings files for both classic shell and display fusion pro I am using.

With a game Windowed Full screen or nothing on main display the start menu goes behind any windows open on the screen. Below is a screenshot of it happening.

http://img.imgland.net/jBkjLLt.png

• Attachment [protected]: DisplayFusion Backup (2017-04-21 @ 14-45, 8.1.1.0).reg [86,562 bytes]

• Attachment [protected]: Menu Settings ClassicShell.xml [386 bytes]

Apr 21, 2017 • #8

Direct1221

3 discussion posts

The last picture did not show the start menu, this one is the one that shows the start menu behind the window.

http://img03.imgland.net/qjO8N_0.png

Apr 21, 2017 • #9

@Direct1221: Could you attach a debug log? Here are the steps:

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Reproduce the issue and note the time so we'll know where to check in the log file
Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
Disable debug logging after sending the log

Apr 24, 2017 • #10

Direct1221

3 discussion posts

12:58:30PM/12:59:30PM

I had opened the start menu 10 times. every time it had went behind the open windows on second monitor.

• Attachment [protected]: DebugInfo.html [157,654 bytes]

• Attachment [protected]: DisplayFusion.log [1,027,249 bytes]

Apr 24, 2017 • #11

Thanks! Nothing unusual in the logs, and when I restored your Classic Shell and DF settings on my test machine (with the exact same monitor layout as yours) I still can't reproduce it. I wonder what I'm missing here. If you disable all startup programs, except for DF and Classic Shell, then reboot, are you still able to reproduce this? I'm just wondering if there might be a third contributing factor.

Apr 28, 2017 • #12