Stardock will be closed for the week starting on Monday, June 29th and we will be returning on Monday, July 6th. We will be monitoring support tickets and forums during this time but expect delays in responses during this time.
Stardock Forums
When a UAC prompt is displayed (but not focused), I cannot click any part of the taskbar any more. I have to Alt-Tab to the UAC prompt.
Hello,
Sorry to hear you are having issues.
What version of Windows ( Full Numbered ) ?
Version of Start11 ?
AzDude
Stardock Community Assistant
There is a newer version of Start11 v1.24
go to your account page My Downloads.
Give that a try ..
No change. I can easily reproduce by right-clicking the taskbar and selecting Task Manager.
Hello,
Sorry to hear you are having issues. I can't get UAC prompt when I right click on my taskbar and open task manager. It just open. But if I run CMD with admin right. I get the UAC prompt but I can not make it inactive until I click yes or no on that thing. Refer screenshot below.
Basj,
Stardock Community Assistant.
I tried to record a video but this is difficult since the secure desktop isn't captured and my UAC prompts display on the secure desktop. The problem seems to only happen when I have a window snapped to take up half the display (like when you drag all the way to the left or right edge).
I still cannot reproduce your issue. I think it is best if you can run cleanboot and see if any other application is in conflict with Start11 and causing the issue. https://forums.stardock.com/505872/start11-support-faq#cleanboot.
Thank you,
Basj,
Stardock Community Assistant
I believe I've nailed down exactly what's causing this after creating a new user.
I like having the "focus follows mouse" setting enabled, which can be accomplished like in this article: https://winaero.com/enable-xmouse-window-tracking-windows-10/. I have ActiveWndTrackTimeout set to 0. It seems to be a focus issue.
This is not an issue with Start11. I can confirm that I do also see the issue with the standard Windows 11 taskbar. (Presumably the behavior was different in Windows 10; I don't remember seeing this previously.)
I'm guessing I can work around this by setting ActiveWndTrackTimeout to a small non-zero value, but I'll give it a try when I have more time.
Thanks!
Awesome, glad your worked it out.
Thank you for reporting back for others which might be in similar situation , 
Basj,
Stardock Community Assistant
Welcome Guest! Please take the time to register with us.