This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Whilst using Windows 10 Pro, I am receiving notifications in the notification centre when I have received a new email in Outlook. However, when I click the email in the notification centre it does not open the email.
Please can you help sort this issue. Followed all other forums etc. and these have not helped solve my issue.
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I am having this issue as well. Started about 2 days ago.
Windows 10 Enterprise, Microsoft Outlook for Microsoft 365 MSO (16.0.12827.20200) 32-bit.
Same problem here. Windows 10 Pro, Microsoft Outlook for Microsoft 365 MSO (16.0.12827.20200) 32-bit. Started recently (maybe in the last few weeks?).
Same problem for me. Clicking on the pop-up notification does not open the email and the 'delete' and 'flag' action buttons do not work. Clicking on the email from the notification center simply removes the notification. Running Microsoft 365 for Enterprise, Version 2005 (Build 12827.20336 Click-to-Run), which is the May 2020 update. Windows 10 Pro Version 1903.
Im also having this problem
Same problem here. Desktop alert, in lower right of my screen, that displays when a new message arrives, does not open the email when clicking on it. This just stopped working recently, I forget exactly when, but sometime in the last couple weeks/months. What is interesting is MSFT was active on this issue over a year ago with the original poster, but now with all the recent updates to this thread, nothing from MSFT.