MenuTools icon indicating copy to clipboard operation
MenuTools copied to clipboard

[Bug]: Failed to create tray icon at startup warning

Open Sevastienn opened this issue 4 years ago • 8 comments

MenuTools produces this warning at the start of the system for no apparent reason. Despite this warning, MenuTools is running and working as intended.

Screenshot 2020-12-03 161311

Sevastienn avatar Dec 03 '20 16:12 Sevastienn

MenuTools produces this warning at the start of the system for no apparent reason. Despite this warning, MenuTools is running and working as intended.

Screenshot 2020-12-03 161311

It seems this warning can be avoided by setting a 30-second delay for the MenuTools task in task scheduler.

Sevastienn avatar Dec 04 '20 20:12 Sevastienn

What Windows are you using?

When you see the alert, did you see the icon on the tray icon?

TBH I need to do a review on this, but I've been very busy this past month.

navossoc avatar Dec 04 '20 21:12 navossoc

Thank you for the quick reply. This is definitely not something urgent.

As of the operating system, I run Windows 10 Build 20270.

As of the tray icon, it seems like an intermittent bug. Often the icon is created and you can see it in the tray despite the alert. Sometimes the icon is not created and MenuTools is indeed not running after the alert appears and sometimes there is no issue at all. That is what made me think there might be a conflict with some other program starting at startup of the computer and why I tried to delay the start of MenuTools by 30 seconds which seems to have completely resolved the issue.

Sevastienn avatar Dec 05 '20 17:12 Sevastienn

@Sevastienn yes, seems the issue is related on how Microsoft handles the "new initialization" of programs on the background. Probably explorer is not ready yet, so that is the major issue.

navossoc avatar Dec 05 '20 17:12 navossoc

Yes, that seems likely. Anyway, the delay seems to be effective in avoiding the issue. By the way, thank you for an amazing piece of software!

Sevastienn avatar Dec 05 '20 17:12 Sevastienn

+1 I've been getting this issue too, but adding the 30-second delay in Task Scheduler did the trick. Thank you for mentioning that!

SlyAceZeta avatar Jul 22 '21 20:07 SlyAceZeta

@Azekthi I always get that error when rebooting after a Win 10 update - another reboot and it's gone, but thanks for the heads-up 👍

fade2gray avatar Jul 22 '21 22:07 fade2gray