Just reverted to 7.3.4 for testing other issues, seeing where clicking Start Menu on DF taskbar on Win 10 Enterprise x64 open Start Menu clicking a second time without moving mouse causes Start button to turn black but doesn't close Start Menu. A third click closes the Start Menu.

The coloration of the DF Start button doesn't seem to match Windows either - on DF taskbar, on hover, the button shows black background, then click changes to (in my case) darker blue background than rest of taskbar, then second click turns black, then third click turns darker blue, closes Start Menu, then turns black after a second like hover is suddenly recognized again.

The Windows Start button turns a lighter (less saturated) blue when hovered, turns darker blue background on click while mouse button is down then reverts to lighter blue with Start Menu showing, turns darker blue button (Windows flag) on second click while mouse button is down, then closes Start Menu on release, never changing background from hover lighter blue.The hover lighter blue background is a bit darker than the lighter blue background of the focused application's taskbar icon.

BTW, clicking the DF Taskbar Start button opens the Start Menu on the 2nd monitor, but pressing the Windows key opens the Start Menu on the primary monitor and moves it to the secondary monitor. I have DPI scaling, but it is set identically on both monitors, which are the same size and resolution.

A longer delay between the first and second click seems to make no difference, the behavior is the same - I waited five seconds.

I upgraded back to 8.0 beta 4 and still have the same issue.

Attached is a Debug Log All where I clicked the DF Taskbar Start Menu button twice.

I just noticed the right-click on the DF Taskbar Start Button doesn't open the Win+X menu like the normal Windows Start Button.

Also, have you considered updating the list of Windows 10 known issues?

I have started seeing a new issue that seems in the same area - after a while, the DF Start Menu button still changes color but no longer opens the Start Menu.

This is generally followed by the DF taskbar buttons stop responding, then the Windows taskbar stops putting icons in the right place, then window refreshes are corrupted, the DF icon no longer responds to right-clicks, and then I have to kill DF to restore normal operation.

In Windows 10, Windows Task Manager doesn't appear to have those options, but I normally use Process Explorer so I have added those columns and will try to track what is happening.

Also some parts of the issues may have been related to the other subject I posted on the Focus Event.

I just observed some bad screen effects and pulled up Task Manager and took a screen shot:

DisplayFusion.exe has Handles 17393, Threads 24, User Objects 3518 and GDI Objects 9999. When I restarted DF, GDI went down to 214 and handles to 1040, though the handles seems to be fluctuating quite a bit and the GDI objects seem to go up slightly every time I close and re-open Task Manager. They also go up a few times when I click the next monitor button, but then seem to hold steady. DF also had stopped responding to right-clicks.

Explorer showed Handles 4491, Threads 138, User Objects 1307 and GDI Objects 2917.

A neat new feature is the Start Menu is only opening on my secondary monitor/taskbar now and not on my primary monitor, even when I click the Start Button on the primary taskbar. Once I slowly clicked three times on the DF taskbar Start button (to open and close the Start Menu), the Start Menu started working properly on the primary monitor.

DF is showing 6860 Handles and 3714 GDI objects right now. Attached is troubleshooting.

I uninstalled the program and rebooted yesterday evening. Today GDI Handles has climbed from 1665 just after lunch to 3997 right now.

A few hours later and it hit 9999 when I wasn't watching. I had to kill the DisplayFusion task and restart, which resulted in 96 GDI Handles.

I will try turning off triggers one by one.

I tried disabling the new window trigger and the focus trigger and the GDI Handles seem to stabilize at a nice, low number. I re-enabled the triggers one at a time, and the GDI Handles grew with each enabled, much faster when just the focus trigger was enabled. I put a return statement at the top of the functions called for each trigger, and the GDI Handles grew, though possibly smaller than before. I have now set each trigger to run a new, empty scripted function I created and will see if GDI Handles are still used up.

With the Focus and Window Created triggers both set to run an empty scripted function, set to Process FIlename "*.*", I see the GDI Handles constantly climbing. With them disabled, they do not climb.

It seems like there is a GDI Handle leak in the Triggers themselves, or the Run Function in a Trigger.

Great. I wonder if it is shared code with other triggers, as with both triggers disabled I see a (very) slow increase in GDI handles used by DF as I run.

I still have some more limited Window Create triggers restricted to certain processes enabled.

The new version appears to have corrected any GDI leaks with triggers. I am using my custom move window triggers again.

But, the original Start Menu not closing (should have been) on second click issue is still there on the DF Taskbar - unlike the standard Start Menu button, the DF Start Menu stays open on the second click.

You asked that the first time

No, the delay does not matter - it only closes on the third click.