Are you using a third-party Start menu app, or just the normal Windows 10 Start menu?

Could you send me a copy of your troubleshooting info? Here are the steps:

• Open the Settings > Troubleshooting tab
• Click the "Export Info to File" button
• Reply with the file attached

Thanks! So when you say that it's opening/closing quickly on the second monitor, is that the monitor on the right or the left?

Ah ok, that makes sense then. We can't hook the Start menu in Windows 10, so we have to open it and rely on polling to find it and move it. Unfortunately it's not quite fast enough to catch it before the Start menu shows on the Primary monitor first

For Vivaldi, could you provide some more details on the issue there? Are you not able to click on anything on the taskbar, or just the Start menu won't open?

If you enable "Allow taskbar reloading while full screen..." on the Settings > Taskbar tab, does that fix up the Vivaldi issue?

Ok, can you attach a backup of your DisplayFusion Settings? (Settings > Options > Export)

Thanks!

Thanks! When I have Vivaldi full screen on the second monitor, and it has focus, the taskbar doesn't show up, which is expected. If I click on something on the primary monitor, then move my mouse over the bottom of the second monitor, the taskbar shows up. Can you check to see if that's the same way yours is behaving as well?

Ah ok, thanks! I'm seeing the same behaviour here, but it happens even without DisplayFusion running. Seems to be a Vivaldi bug

Back to the Start menu issue. When you click the Start button on the Primary monitor, it flashes on the second monitor first, then moves to the Primary. Does this happen even after a fresh reboot? Or only after you've opened the Start menu on the second monitor once?

Any chance you can attach a video of that Start menu issue? Also, can you send a debug log for it?

• 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
• Click the "Export Info to File" button on the Settings > Troubleshooting tab
• Reply with the file attached
• Disable debug logging after sending the log

Ah yep, thanks for the video! I should have asked you to send one before asking all my other questions. That's pretty much the expected behaviour. We can't hook the Start menu in Windows 10, so we have to poll for it to see if it's visible and then move it. If the polling hits right at the right time, you won't see it flicker on the Primary monitor before opening on the second, but if the menu opens right when one polling interval has ended, you'll end up seeing it briefly on the Primary before it gets detected and moved to the second monitor.

Hopefully!