-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[Installer] explorer.exe closed and not restarted upon install of v0.17.0 #2515
Comments
Hi @Aragorn450 |
I have not been able to replicate it, which is not too surprising. I'm assuming it was a fluke, but figured I should report it anyway in case someone else also says they had the same issue in which case, it'd be less likely to be a fluke. |
@Aragorn450 |
@enricogior Can I suggest at least warning people before you kill explorer? Especially if the new version is going to allow auto-updates, I'd be pretty upset if in v0.18 or some future release it suddenly auto-updated in the background and decided to kill explorer without notice. Note: I did a search but if I somehow missed this already being part of a future update I apologize. :) |
@hexxellor |
@enricogior Excellent! I did notice #2730 but wasn't sure from the status if that solution worked or not, etc. Thanks for the clarification. I really appreciate it. 👍 |
tracking in #2730 |
Environment
Steps to reproduce
Install v0.17.0, may need to have a previous install (v0.16.1 was my initial install) first.
Expected behavior
Upon install, explorer.exe should be restarted to show the user their desktop.
Actual behavior
My desktop was closed during the install and I had solid backgrounds with no task bar because explorer.exe was closed. When the install was complete and PowerToys was started, it stayed this way. I had to CTRL + ALT + DEL to open Task Manager and then ran explorer.exe manually after verifying it was no longer in the running tasks.
This could certainly be something unique to my configuration. I will do whatever I can to help provide more details as needed.
The text was updated successfully, but these errors were encountered: