It's expected that the button doesn't change, because what's happening is just that DisplayFusion is hooking the maximize to monitor, and resizing the window to fit the split instead.

However, clicking the button or double-clicking the titlebar should still restore the window. It might be that for some reason Windows is remembering the window size as being fit to the split. If you manually resize the window smaller, then maximize it and restore it, does it go back to the smaller size?

Could you send over a debug log for this issue?

• On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L2: Log Detailed" and click Apply
• Maximize a window to a split, then try to restore it 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

Thanks!

Ah sorry, I need one more thing enabled for the logging. In the Advanced Settings, can you set "Log Level for Hooks" to 2, then restart DisplayFusion again and reproduce the issue?

Thanks! Are you using the stable build of Chrome, or one of the dev or Canary builds?

Quick question here, when you drag the Chrome window around, does the DisplayFusion "move to next monitor" button stay with the window, or does it lag behind? I'm wondering if the window isn't getting hooked properly, even though the log seems to indicate that it is.

Thanks!