DisplayFusion doesn't show the icons to move the window to next monitors, since a few days

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

If you are experiencing any issues with your desktop wallpaper or taskbar buttons
please download and install the latest DisplayFusion beta version before contacting support.

<< Discussions Reply

Stephaen

3 discussion posts

Hi there,

DisplayFusion doesn't show the icons to move the window to next monitors, since a few days (don't know exactly since when, maybe after last Windows 11 update).

I checked that the icons are activated in the "Functions" settings menu.
I checked that "TitleBar Buttons: Don't Hide for Top-Tab Web Browsers" is activated (but anyway the problem appears on all windows, not only browsers)

I'm using version 12.1.1 on Windows 11 25H2 (26200.9457). I tried with version 12.1.2 beta 1 but it doesn't solve the problem
I also uninstalled DisplayFusion and reinstalled it, with no success.

Could somebody help?

Best regards

18 days ago • #1

Could you send me a debug log for this issue?

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and then click "Clear Log"
Try opening a few new windows that should get titlebar buttons 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!

16 days ago • #2

Stephaen

3 discussion posts

Hello Keith,

Done. I opened at 08:52 am following applications: IrfanView, Notepad, Chrome and DVBViewer Pro. Log attached.

BR.

• Attachment [protected]: DisplayFusionDebugInfo.zip [82,906 bytes]

16 days ago • #3

Thanks! It looks like you have a rule on the Settings > Compatibility tab for iTunes with the "Disable TitleBar Buttons (all applications)" option enabled. If you change that one to the "(this application only)" version of the setting, that should fix this up.

Please let me know if not