[Updater; Runner] Optimized notifications
See original GitHub issueLike suggested by @crutkas and me in PR #2141 we should optimize the updaters’ toast notifications. If you have further ideas please comment them.
It would be nice if someone of the other project contributors could create the necessary PRs. ⚠ Please add screenshots of the new notifications, so that other contributors don’t have to run your code to see the changes.
Screenshot of the current toast notification:

1. Adding version numbers
The following texts are examples and the images are created with an image editing tool. If I have forgotten some texts feel free to also add them a version number.
a) update is available
| Variant 1 (short version) | Variant 2 (long version) |
|---|---|
![]() |
![]() |
- My favorite is the short version.
- Feel free to write in the comments which version you prefer.
b) update successfully installed
Update to version 0.17 of PowerToys successfully installed.
c) update failed
Update to version 0.17 of PowerToys failed.
d) Old version detected
We have detect an old version (0.15.2) of PowerToys installed on your System. Want you remove it?
e) Uninstall old version failed ℹ Here the version number is important that the user knows which version he has to uninstall.
Error: Uninstalling the old version (0.15.2) failed. Please uninstall it manually.
2. Optimice button layout
I think we could optimize the message by adding an title for the time dropdown like this:

3. Metered connections
I don’t known how we actually react on metered connections. But a notification like this would be a great idea:
An update to PowerToys is available. The update will be downloaded when the internet connection is not metered anymore.
<Version_Info>
4. Definition of “is ready to install”
In the update notify we have the following text: An update to PowerToys is ready to install.
Is the update downloaded already when this notification gets shown or must text been like the following: An Update to PowerToys is ready to download and install.
Issue Analytics
- State:
- Created 3 years ago
- Comments:39 (12 by maintainers)



Top Related StackOverflow Question
For 0.17 we should be good as we are. We don’t have a lot of time to test more changes, we can revisit it in 0.18 or more likely in 0.19.
@htcfreek oh, that’s a great find! I’ll add it.