-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Powertoys not properly starting on system start #9959
Comments
I have an interesting update. Just now I restarted my System and can confirm that, immediately after startup, all services work. Then, one or two seconds later, they stop behaving correctly. |
@enricogior wonder if this is related to #9790 |
Hey, sorry for the late answer:
I'm especially curious since it does work for a short moment, then seem to go non-functional. |
Here the promised report with it not working after a short period on reboot. |
Still seems to be a problem. (v0.33.1) |
@enricogior ton of the logs here are blank. |
Can I somehow provide better logs by enabling that Debug mode? I can confirm this problem still appears regularly on two of my machines (and a third one that is no longer in my possession had this problem as well). |
To detail the symptoms of this: Some tools don't seem to be defunct completely: |
I may be seeing the same problem when I restart. PowerToys is missing in the system tray but its process is running. I end the process, relaunch PowerToys, and all seems to well again. |
As an update: I haven't noticed the problems since upgrading, maybe for a few days now. I think I haven't seen it since 0.36, but I have not done extensive testing. |
0.37 seems to have corrected the issues I was seeing, so far. I didn't install 0.36. |
@stevemagruder @glittle |
I spoke too soon. I just had to restart due to a device driver update, and PowerToys isn't in my system tray after the restart. |
@stevemagruder |
Here it is: |
@stevemagruder Then restart Windows and let us know if PowerToys still doesn't auto-start. |
There's no errors or even any warnings or info messages about PowerToys in the Event Viewer Windows Log. |
I just wanted to check in to say the issue is still occurring for me with PowerToys 0.37.2. |
While it hasn't been a problem for me for a while, it has started appearing again (I believe yesterday). After booting, PowerToys Keyboard Manager did not work until I manually disabled and reenabled it in settings. |
It's still occurring for me with PowerToys 0.41.4. |
@stevemagruder |
I had to end the PowerToys Runner task and restart it first. |
Never mind - now they are appearing. I'll attach the last one. |
@stevemagruder |
I don't know if a module as such is causing the overall issue of the disappearing tray icon, but the modules I have currently enabled are Color Picker, File Explorer add-ons, Image Resizer, Keyboard Manager, PowerRename, PowerToys Run and Shortcut Guide. The process is running and I know this as I can bring up the Shortcut Guide and I see the task in Task Manager. |
Also, here's an aspect I'm not sure has been brought up before: Sometimes I see a filler space in my tray icons, like an icon is supposed to be there but is invisible and unclickable. And my latest Windows configuration is Windows 10 Home 21H1, build 19043.1147, Windows Feature Experience Pack 120.2212.3920.0, Release Preview Channel. |
As a quick test, I turned off all the modules, then restarted my system. The PowerToys tray icon is still not displaying after restart. This must be an issue in the base code unrelated to modules. |
@stevemagruder Can you try disabling PowerToys Run from Settings and then see if the issue is still there? |
The issue is still there. What you just described is a subset of my "quick test" above. |
Hi @stevemagruder , |
That looks to be it. I added a delay to TaskBarX's startup in Task Scheduler, and I saw as it started, it wiped out PT's tray icon. |
@stevemagruder , |
I have it set to 15 seconds now. The fix for the issue related to PowerToys was unchecking the Extra setting "Show Tray icon". TaskbarX's tray icon was somehow interfering with PowerToys and even some other tray icons, although not as consistently as with PowerToys. |
@jaimecbernardo I'm going to add this as a known compatibility issue with TaskbarX. @hpr1999 are you also using TaskbarX or a similar application? If disabling/delaying that application resolves the issue with PowerToys we can mark this as resolved. |
As far as I can remember, I was never using TaskbarX (and I'm not sure what kind of similarity would be important, but I'd also say I wasn't using similar software). However, I have not been able to reproduce this error in a long time, especially since I've moved hardware, but even on the machines where it used to happen. From my perspective, this issue was probably fixed in some version along the way, at least for me. Now, the only problem I have at startup is Fancy Zones erroring out, but I believe that to be a different issue due to different symptoms. |
@dedavis6797 did you confirm this with taskbarx? The original issue creator says he doesn’t have the issue anymore so I’m assuming these are different issues and need to be tracked in different issues. |
I can create a separate issue to track TaskbarX compatibility against. We can close out this issue as it seems to have been resolved. @hpr1998 for the FancyZones erroring out issue you're facing, can you create a new issue with a description of the error and steps to repro so we can investigate? |
ℹ Computer information
📝 Provide detailed reproduction steps (if any)
✔️ Expected result
PowerToys runs as before.
❌ Actual result
PowerToys don't work until a) PowerToys is manually quit and restarted or b) the toys in question are manually disabled and restarted in the settings.
📷 Screenshots
N/A
I'm sorry if there is an issue to track this already, I have searched extensively but they all seemed to be either closed or showing different symptoms.
I can add that this behaviour occurs / occured on three different devices of mine with wildly different hardware.
Do you have any idea what could cause this, and, if it's not a known issue, what system configuration could potentially cause trouble to the startup mechanism across my different devices?
I'll be happy to supply more information as needed.
The text was updated successfully, but these errors were encountered: