DisplayFusion appears to have issue of reliably launching the start menu (by both clicks and keyboard). Video attached.

The problem gets worse when the system comes back from S3 sleep, in most cases totaly unresponsive, i'm force to wait, (ie. go make a cup of coffee and come back) for the start menu to come up. Quiting Display fusion doesnt solve the problem, as the remaining windows taskbar will be affected as well. Problem improves (slightly) when system is rebooted, but come back shortly after.

Also if the start menu DOES come up after the lag [often than not], it is not in 'focus' (as in i can start typing and windows will search the start menu immediately, like in vanilla windows 11), trying to click the search field to activate it will not work.

Quiting Display Fusion does not return the start menu to its vanila/unmodded state of reponsiveness. Only dispabling DF from starting with windows and restarting would.

System is Windows 11 24H2, Display Fusion 12.0.1, i5-4960K 32GB RAM, multi/dual monitor set up with dual taskbars

Hi! I can confirm there are several problems with DisplayFusion when coming back from suspension. Killing the app and opening it again fixes everything.

Let me clarify: There are two issues

Launching/clicking the Windows Start Menu on the taskbar lags, (there is a very noticiable delay after clicked or windows key is pressed on the keyboard)

Launching/clicking the Windows Start Menu on the taskbar is unresponsive to being launched/clicked after system resumes from S3 Sleep, sometimes with the search field unable to be accessed

Restarting/Quit&relaunch Displayfusion does temporarily solve the second issue arrising form waking from Sleep, but does not solve the first issue. It will happen again when the system goes to sleep. and with the startmenu unresponsive, it is a pain to relaunch displayfusion, as i rather not have its icons around on the desktop, and startmenu search field is the primary way i (quickly) launch apps

First issue is documented via video attached in first post, i have made the file unprotected.

> The first issue is somewhat expected. We have to poll for the start menu to open and then pull it to the correct monitor, if you repeatedly press the start button while that's happening there will be some weird results. We'll see if we can make any improvements there going forward though.

The repeating presses in quick succession exaggerated was to demonstrate the issue. In practice, the lag in the menu coming up, does happen for reasonably often key presses and causes me the subsequent key inputs to the search field to be missed. I am used to using the startmenu like the commands+space on a macintosh, end expects the startmenu to come up instantly (and it does in vanila windows 11) but it unfortunate that m'soft didnt keep the multimonitor taskbar behaviour in past versions of windows.

And requested the log file is attached.

For me, it was happening with the previous version as well. I found in the changelog you had fixed something related to this, but it isn't fixed completely.

Sorry I am unable to confirm that, as the first time i ran Display fusion (it was 12.0.1) was after i purchased a licence for Displayfusion.

**by first time i meant first time in many years (decades)

Answering for previous behaviour, no it does not respond at times,it was as if i didn't launch it by mouseclicks or keyboard. Lag unresposnive is on both windows task bar and DF task bar. And even persists [on the windows taskbar] after exiting DF via icon taskbar > right click > exit. Only a reboot would return it to normal.

On a different note: a few days ago i installed Windows Update** [2026-01 Security Update (KB5074109) (26100.7623)] for Win 11x62 24H2, and it appears to have alleviated most of the start menu non responsiveness in Display Fusion (occurring after S3 sleep), although the issues i reported still does occur, bit the previous of unresponsiveness, is much less, what remains is a slight lag, and startmenu jumping around as it being pulled to a different monitor. Loss of cursor/keyboard focus to the startmenu search still does occur, but pressing the start menu click/or keyboard button a few more times seemed to have it behave properly again

**: Note i also did tweak a few things in the registry due to microsoft screwing around with the startmenu again (they changed how things looked from my usual pre KB5074109 update start menu) and i had enough, i got rid of bing web search and edited a sqlite file to get rid of microsoft apps store search integration. I also updated nvidia studio display drivers while i'm at it. Not sure which fixed what but happy with the results so far.

PS: I'm looking forward to the update that do tweak the performance of the system hook startmenu/taskbar on a secondary monitor