Native toast notifications not displaying on Windows 10

Hi @shawngray17280

I can see the Edge notifications in Action Center like below. I think the issue in your computer is related with Edge not showing in Get notifications from these senders. You need to turn on Edge option in it so that you can get notifications.

There're some possible fixes for you, you can have a try:

• Go to edge://flags/#enable-system-notifications in Edge and set Enable system notifications to Enabled.
• Update Edge to the latest version which is v105.
• Check if this policy DefaultNotificationsSetting is set in the computers and make sure it's not set BlockNotifications.
• If the above still can't fix the issue, you can refer to the Repair Microsoft Edge part in this doc to repair Edge.
• You can also do a SFC scan as the issue may be caused by a corrupted/missing system file. Please follow this article on how to run a SFC scan in Windows 10.

  ---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Regards,
Yu Zhou

Hi Shawngray17280-9791,

It’s because A new Windows requirement for toast notifications is introduced in Windows 10, version 1607, and it is enforced starting with Windows 10, version 1709. The Windows requirement specifies that an application's shortcut on the Start menu must contain an AppUserModelID tag. However, the Outlook shortcut that's created by the OCT doesn't contain the AppUserModelID tag, so toast notifications aren't displayed.

For desktop applications that send toast notifications, you must include the AppUserModelID tag of your application's shortcut on the Start screen each time that you call the CreateToastNotifier method. If you don't do this, your toast notifications won't be displayed. For details, see Quickstart: Sending a toast notification from the desktop :- https://learn.microsoft.com/previous-versions/windows/desktop/legacy/hh802768(v=vs.85)

To work around fix this issue, follow these steps:

Perform a Windows installer (MSI) installation of Outlook without using the OCT. Then, the Outlook shortcut that contains the AppUserModelID tag will be created in the following location:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs

Copy the new Outlook shortcut, and deploy it on the computers that have the issue.

To know more about Toast content refer to this documentation :- https://learn.microsoft.com/windows/apps/design/shell/tiles-and-notifications/adaptive-interactive-toasts

----------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept it as an answer--

Update: We have managed to resolve the issue (for now) after possibly two-dozen hours wasted with investigating it.

In summary, the issue for us was that Edge's AppUserModelId (AUMID) was not registered in the registry, which is something that is a requirement for toast notifications to be shown. This is well-documented, but is generally only relevant for third-party app development, rather than an official Microsoft product that is built-in to the OS.

Unfortunately, there seems to be literally no debugging/error information available that points towards the lack of registration being the cause of the notification disappearing into a black hole. This is rather frustrating, as it seems like something that'd be very easy for the Windows Notification Service to report on via the event log, rather than simply indicating that the notification is being processed successfully. If I'm simply looking in the wrong place for this, please let me know!

I do not know why the Edge AUMID wasn't registered on our devices, however I have a feeling that it's due to the fact that we have a Group Policy Preference that deletes the standard Edge shortcut that is provided by the system and replaces it with one that has some custom command arguments. I'm assuming that because the Edge shortcut is deleted half-way through the build process (we use SCCM), the registry is not correctly populated with an AUMID entry for it.

However, I am not certain of this, as we have another device (unmanaged) that does not have the AUMID registry entry, yet Edge notifications work correctly. This is an older build though that originally had the legacy Edge Trident release and was upgraded to Edge Chromium, so this may make things different to a completely fresh build?

To fix the issue, create the following two registry entries:

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppUserModelId\Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe!App" /v "DisplayName" /d "Microsoft Edge" /t "REG_EXPAND_SZ"  

reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppUserModelId\Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe!App" /v "CustomActivator" /d "{628ACE20-B77A-456F-A88D-547DB6CEEDD5}" /t "REG_SZ"  

The CustomActivator value contains the COM class ID (CLSID) for the Edge notification helper (628ACE20-B77A-456F-A88D-547DB6CEEDD5), which is what handles notification clicks, etc. There is surprisingly little reference to this CLSID online, however it does appear to have remained static for at least 2 years, all the way back to Edge versions in the 80's (we're on 105 at the time of writing).