Thanks for the prompt reply. I followed your instructions. After the second reboot, the taskbar on my secondary monitor was painted correctly for about a second, then it was un-painted.

I tried creating the local account as per the provided instructions. I customized the taskbar similarly to how I did so in my primary account. I didn't notice the problem in the local account, even after signing out and then signing back in. Fences and Windhawk started up with the local account too, but I did not configure either application in the local account.

I also didn't notice the problem today in my primary account. I believe the issue is intermittent, possibly caused by a race condition between Windows and Start11 (whoever paints the taskbar last wins).

Although I have not noticed the issue again since re-installing Start11 and testing it in the local account, I agree with you about a possible conflict between Windhawk and Start11. I have the following mods installed that affect the taskbar, though not all of them are enabled:

• Taskbar Labels for Windows 11 (disabled)
• Taskbar minimize/restore on scroll (disabled)
• Taskbar Thumbnail Reorder (enabled)
• Taskbar tray icon spacing (enabled, it only affects the primary taskbar which is always painted correctly)
• Virtual Desktop Preserve Taskbar Order (enabled)

Since the issue has been intermittent, I will disable Windhawk entirely if I notice the issue again. If the issue does not occur again after several days, then we could reasonably conclude that a conflict with Windhawk is the likely source of the issue. As a precautionary measure, I added " C:\Program Files (x86)\Stardock\* " to Windhawk's process exclusion list.

I must say that we cannot offer any formal support if any Windhawk enhancements are enabled due to how they work.  You run the risk of introducing conflicts and excluding the Stardock directories will not help as many of the Stardock apps run in other processes as part of how they work.

I notice you mentioned Winaero Tweaker too. That still might cause conflict. 

Thank you,

Basj,
Stardock Community Assistant