-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Unable to open the main window #268
Comments
Having similar issue: nothing opens on launch, no main window, no system tray icon . Functionality seems to be working though. 10.0.17763 Build 17763 |
One work around: |
Aah, thanks for that quick fix :) System try icon is now there, however the main settings window is completely blank :O I guess I'll do a reboot, nothing else going on right now... |
@Qingtian-Zou @eagleEggs |
Yep, after reboot same thing. Will track there - Thanks @enricogior |
|
No I don't think this issue should be closed. The problem with start at login is different from the blank settings window. |
Hi @Qingtian-Zou @Qingtian-Zou, @eagleEggs
Can you provide more information on your system configuration:
Thank you. |
Have been using PowerToys for some days, and below is what I find: The system tray disappearing only happens the first time I reboot my computer. After that, the same issue does not happen, during which I have rebooted my computer for 4 or 5 times. The computer is for personal use. There is no 3rd party antivirus or shell program installed. |
I have installed PowerToys on another Win10 PC of mine, checked "start at login", and rebooted. The problem does not appear. I guess the trigger is not rebooting, but I have not idea what is the other possible causes. |
This may be out of the scope, but I find something very interesting when I try to re-do what I did when I first install PowerToys: Firstly, uninstall PowerToys, and reboot. After that, re-install PowerToys. During the installation process, uncheck "start at login". After installation, in the main settings window, I check "start at login", create one custom FancyZone layout, save configurations, and then reboot. Now, after the this second reboot, I double click on the PowerToys system tray icon, and two PowerToys main windows appear. One is almost empty, with onely one tab "General settings", tab title "PowerToys General Settings", and the save button on the right, so I close it. The other window seems good, but nothing works. For example, in "FancyZones" tab, I click "edit zones", but nothing happens; I check and uncheck some options and click on save button, but only get the circle rolling without stop. After discarding the changes, I am able to close the second window. Then I double click again on the PowerToys system tray icon to reopen the main window. This time everything works fine. |
Hi @Qingtian-Zou You can either build the binaries yourself from the dev/enricogior/debug-trace branch: https://github.com/microsoft/PowerToys/tree/dev/enricogior/debug-trace or download the zip file from the release assets: First uninstall PowerToys, then install it again leaving all the default checkboxes. The unsigned-debug-build.zip contains a |
@Qingtian-Zou |
This is now fixed in PowerToys 0.14.0 https://github.com/microsoft/PowerToys/releases |
Environment
Steps to reproduce
Reboot.
Expected behavior
An icon should appear in system tray, on which I can double click to open the main window. Or I should be able to open the main window by clicking PowerToys in the start menu.
Actual behavior
No icon appears in system tray. (Though it was there right after install&run before I reboot my machine.) Clicking on PowerToys in start menu brings up a dialog asking for privielge escalation, but nothing happens after then, no matter I click "yes" or "no".
The PowerToys seems to be running. I hold WIN and I see the shortcut hints. I hold down SHIFT and drag windows and I see FancyZone react. However, my FancyZone configuration disappears. Now I only have one zone that takes up the whole screen.
Screenshots
The text was updated successfully, but these errors were encountered: