Notifications - popups vs history

pokeefe0001 · Dec 27, 2023

There seem to be two mostly unrelated aspects of Windows notifications: the popups that display for a few seconds (Are those "toasts"?) and the history of notifications shown by clicking the Notifications icon. Is there any way to control those independently? For instance, I appreciate the popups created by Macrium Reflect saying a backup has started/finished, but I don't need a history of those. On the other hand, when I was trying to get task scheduler to run a script when the the computer was going to sleep. In this case a popup would be meaningless but a record of the notification would provide diagnostic information. (And in this case either the script or the notification failed; there was nothing in the notification history list.)

Is there a way a way to control these two aspects of notifications? All I can find in the Settings is a yes/no setting for individual notifications.

trumpy81 · Dec 27, 2023

Go to Settings > System > Notifications and scroll down to the program you want to control. Click on the program name to expand the actions panel where you can set many different aspects of notifications for that program.

You can control Banners (not Toasts) and notifications in the Notification Center (when you click on the Taskbar Bell icon).

pokeefe0001 · Dec 28, 2023

trumpy81 said:
Go to Settings > System > Notifications and scroll down to the program you want to control. Click on the program name to expand the actions panel where you can set many different aspects of notifications for that program.

You can control Banners (not Toasts) and notifications in the Notification Center (when you click on the Taskbar Bell icon).

View attachment 82503

Thank you. I missed that. That worked fine for the notifications from my backup programs. However, I don't see how to easily apply it to script-issued notifications. This perhaps due to my ignorance of Powershell. I stole the following PS script from somewhere a long time ago:

Powershell:

[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")

$objNotifyIcon = New-Object System.Windows.Forms.NotifyIcon

$objNotifyIcon.Icon = "C:\Batch_Files\Info.ico"
$objNotifyIcon.BalloonTipIcon = "Info"
$objNotifyIcon.BalloonTipText = "Test Notification issued."
$objNotifyIcon.BalloonTipTitle = "Test"

$objNotifyIcon.Visible = $True
$objNotifyIcon.ShowBalloonTip(1000)

When I run it Settings>System>Notifications "Notifications from apps and other senders" list, sorted by most recent, shows "Windows Power Shell" at the top. Accurate but not very specific if I have more than one script issuing notification. Is there a way to attach a name or identifier to the script (or notification) so that the Settings can be applied to a specific script (or notification) rather than to all notifications issued by Powershell scripts?

trumpy81 · Dec 28, 2023

I am no expert when it comes to Power Shell, I can usually fumble my way around, but that's all.

A quick Google revealed this, which may be of some use:

Setting IDs per PowerShell script

I have a PowerShell script, which fills the Usrid custom attribute with EMP$ID value. $ID is a continuous number, which is normally stored in a text file and continuously written after setting the ...

stackoverflow.com

pokeefe0001 · Dec 28, 2023

I usually can't even fumble my way around in PowerShell, but I have a strong feeling that discussion you linked to isn't about the whatever-it-is that indexes the "Notifications from apps and other senders". I guess I want to know what identifies an app or other sender. (Later I'll try to figure how to set it in a script.)

trumpy81 · Dec 28, 2023

pokeefe0001 said:
Is there a way to attach a name or identifier to the script

I answered your question pertaining to adding an identifier or name to a script, that is why I provided that link, it is talking about exactly that.

You know exactly what you want to do, so keep that in mind while you search for an answer.

pokeefe0001 · Dec 28, 2023

trumpy81 said:
I answered your question pertaining to adding an identifier or name to a script, that is why I provided that link, it is talking about exactly that.

You know exactly what you want to do, so keep that in mind while you search for an answer.

I guess I didn't clarify what kind of identifier I wanted, but I did say "so that the Settings can be applied to a specific script (or notification)"

I don't know exactly what I want to do because I have no idea what Windows uses to tie a specific notification to one of the notification Settings. Whatever that entity is, it is apparently ephemeral for PowerShell scripts. The notification setting for "Windows Power Shell" that I saw earlier has evaporated. On the other hand, notification settings for "Macrium Reflect", "Dropbox", "VeraCrypt", "File Explorer", etc., are permanent

trumpy81 · Dec 28, 2023

This may be of some help to your quest:

NotifyOnDemand - free and open source command line utility to generate Windows Notifications

Free and open source command line utility to generate Windows Notifications

rlatour.com

You could easily integrate that into your script/s.

pokeefe0001 · Dec 28, 2023

trumpy81 said:
This may be of some help to your quest:

NotifyOnDemand - free and open source command line utility to generate Windows Notifications

Free and open source command line utility to generate Windows Notifications

rlatour.com

You could easily integrate that into your script/s.

Looks interesting. I'll give it a try.

garlin · Dec 29, 2023

Except all notifications are sourced by NotifyOnDemand, which is the same effect of running a PS script and being identified from a single source.

pokeefe0001 · Dec 29, 2023

garlin said:
Except all notifications are sourced by NotifyOnDemand, instead of your PS example.

Well, so far that's a little better than having them all sourced by PS. (Especially since, so far, "them all" is just one script.) But having some way to set an arbitrary source would be handy.

garlin · Dec 29, 2023

I just finished some research, and don't pretend to be any expert, but to self-identify your notification source -- a real or fake AppUserModelId needs to be registered.

We can't use the simple NotifyIcon() method, because it won't allow us to pass any arbitrary AppUserModelId, instead it takes the profile of the parent PowerShell or ISE process.

1. Create one or more AppUserModelId Classes, each with a random GUID:

Code:

C:\Users\GARLIN>powershell (New-Guid).Guid
63410a2a-42d7-4019-b8cb-2fc2604eeb4c

My two new Classes are "PowerShell.Script1" & "PowerShell.Script2"
Random GUID's are arbitrarily chosen, you can re-use mine or create your own.

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppUserModelId\PowerShell.Script1]
@=""
"DisplayName"="PowerShell Script 1"
"CustomActivator"="{d3644ec3-0142-443b-b08b-357eb21917d4}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppUserModelId\PowerShell.Script2]
@=""
"DisplayName"="PowerShell Script 2"
"CustomActivator"="{2a0537b1-c027-4378-9b75-7c7e481d60c0}"

2. Adapt the Toast Notification method from PowerShell can I use balloons, toasts and notifications?

Code:

    [Windows.UI.Notifications.ToastNotificationManager, Windows.UI.Notifications, ContentType = WindowsRuntime] > $null

    # Toasts templates: https://msdn.microsoft.com/en-us/library/windows/apps/hh761494.aspx
    $template = [Windows.UI.Notifications.ToastNotificationManager]::GetTemplateContent([Windows.UI.Notifications.ToastTemplateType]::ToastText02)

    # Convert to .NET type for XML manipulation
    $toastXml = [xml] $template.GetXml()

    # Customize the toast message
    $toastXml.GetElementsByTagName("text")[0].AppendChild($toastXml.CreateTextNode("Script 1 test")) > $null
    $toastXml.GetElementsByTagName("text")[1].AppendChild($toastXml.CreateTextNode("Time is now " + [DateTime]::Now.ToShortTimeString() + ".")) > $null

    # Convert back to WinRT type
    $xml = New-Object Windows.Data.Xml.Dom.XmlDocument
    $xml.LoadXml($toastXml.OuterXml)

    $toast = [Windows.UI.Notifications.ToastNotification]::new($xml)

    # Unique Application id/tag and group
    $toast.Tag = "PowerShell.Script1"
    #$toast.Group = "PowerShell.Script1"

    # Create the toasts and show the toast. Make sure to include the AppId
    $notifier = [Windows.UI.Notifications.ToastNotificationManager]::CreateToastNotifier($toast.Tag)
    $notifier.Show($toast)

    #########

    # Convert to .NET type for XML manipulation
    $toastXml = [xml] $template.GetXml()

    # Customize the toast message
    $toastXml.GetElementsByTagName("text")[0].AppendChild($toastXml.CreateTextNode("Script 2 test")) > $null
    $toastXml.GetElementsByTagName("text")[1].AppendChild($toastXml.CreateTextNode("Time is now " + [DateTime]::Now.ToShortTimeString() + ".")) > $null

    # Convert back to WinRT type
    $xml = New-Object Windows.Data.Xml.Dom.XmlDocument
    $xml.LoadXml($toastXml.OuterXml)

    $toast = [Windows.UI.Notifications.ToastNotification]::new($xml)

    # Unique Application id/tag and group
    $toast.Tag = "PowerShell.Script2"
    #$toast.Group = "PowerShell.Script2"

    # Create the toasts and show the toast. Make sure to include the AppId
    $notifier = [Windows.UI.Notifications.ToastNotificationManager]::CreateToastNotifier($toast.Tag)
    $notifier.Show($toast)

3. When the two toasts are delivered, each is tagged by a different "App". There's no reason why you can't create more sources as you need, just as long as you can map the identifier Tag to a registered Class.

pokeefe0001 · Dec 29, 2023

Thank you very much! That's exactly what I needed.

It will take me a while to digest that since I know next to nothing about Windows notification (the difference between a banner and a toast, for instance), and I have to reacquaint myself with object-oriented programming whenever confronted with an object. I could just blindly copy what you have - changing names and text strings, of course - but I'd rather understand what I'm doing.

I'll dig into this in a couple days.

garlin · Dec 29, 2023

The script uses one of the Windows-provided XML templates for layout. There's a few more templates available.

What's really different is you're using a different API. There's like 4-5 distinct methods to create a notification event, but since your requirement is to use an unique source identifier, that removes most of the other API paths. Frankly, most of the available resources are unintelligible unless you're an UI developer.