“Cannot open this item” Error when clicking Desktop Alerts

Clicking a desktop alert or toast notification is intended to open the associated email or calendar invite directly. When an alert instead triggers the error dialog "Cannot open this item", or dismisses itself without bringing the message into view, the client has failed to resolve the item’s unique identifier. This error typically points to protocol handler mismatches, elevation integrity conflicts, or background inbox rules moving the item prior to user interaction.

Fast Fix

Check your file protocol associations. Go to Windows Settings > Apps > Default apps, select Outlook (New) (or your intended Outlook version), and set it as default for MAILTO, .eml, and .msg. If Outlook was launched with administrator privileges, restart it normally without elevation.

---

Diagnostic Snapshot

Property	Details
Error Message	“Cannot open this item” / Silent failure upon clicking desktop alert
Common Causes	Item moved by automated rules, UAC elevation mismatch, or corrupted protocol handlers
Impact Level	Moderate (inconvenient message navigation; underlying email remains intact)
Resolution Time	5 to 10 minutes

---

Why the Desktop Alert Link Breaks

When a new message arrives, the operating system generates a temporary notification containing a direct pointer (an EntryID or web URL hook) to the target record in your mailbox.

When you click that toast, the Windows shell calls the application’s registered protocol handler to open the item. The command fails with "Cannot open this item" under three primary conditions:

1. The Item Moved (Race Condition): If you have an active Inbox Rule configured to move incoming messages into a specific subfolder, the alert is triggered while the email hits the Inbox. If the rule processes and moves the message into a subfolder before you click the banner, the notification’s original pointer is invalidated.
2. Process Integrity Level Mismatch (UAC Elevation): If Outlook is running with elevated administrator rights (“Run as administrator”) while the Windows shell (explorer.exe) is running under standard user privileges, Windows security blocks the notification click from communicating across integrity levels.
3. Conflicting App Associations: Following a migration, Windows 11 may attempt to pass the notification request to classic Outlook while New Outlook owns the underlying data session, breaking the link.

Message Arrival
 │
 ├── 1. Toast Notification Generated (Points to Inbox EntryID)
 │
 ├── 2. Background Rule Executes ───> Moves message to "Subfolder"
 │
 └── 3. User clicks Toast Alert ───> Points to old Inbox location
                                      └── RESULT: "Cannot open this item"

---

Progressive Troubleshooting Steps

Step 1: Check for Moving Rules (The Most Common Cause)

If this error occurs only on specific types of emails (such as newsletters, automated alerts, or internal project updates), an automated rule is likely redirecting the message:

1. Look in your mailbox subfolders to see if the message that triggered the alert is already filed away.
2. If the message appears inside a subfolder rather than your Inbox, the notification failed because the original item pointer expired when the file was moved.
3. To resolve this:
   • Edit the rule to uncheck any option that marks the item as unread or moves it instantly without alerting.
   • Alternatively, configure the rule to route the notification properly. For issues with rules migrating incorrectly between clients, see:
     • How to Fix “Missing Rules” after Switching to New Outlook

Step 2: Remove Elevated Administrator Privileges

Running Outlook elevated causes modern toast notifications to lose their Inter-Process Communication (IPC) binding to the Windows shell:

1. Close Outlook completely.
2. Check your Start menu shortcut or taskbar pin:
   • Right-click the Outlook icon, right-click Outlook, and select Properties.
   • Go to the Compatibility tab.
   • Ensure that Run this program as an administrator is unchecked.
3. Relaunch Outlook normally.
4. Send a test email to your account from an external address and click the notification banner to verify it opens.

Step 3: Repair Default App Protocol Handlers

If Windows 11 is confused about which client handles notification hooks:

1. Press Win + I to open Settings.
2. Go to Apps > Default apps.
3. Scroll down and click Choose defaults by link type (or search for Outlook directly).
4. Verify that both MAILTO and MS-OUTLOOK are mapped to the specific client you actively use:
   • If using New Outlook, set them to Outlook (New).
   • If using Classic Outlook, set them to Outlook.
5. For deep-dive resolution on application association launch failures, refer to:
   • “New Outlook” failing to launch from mailto: links

Step 4: Clear the Windows Notification Action Center Cache

If toast links are broken across all notifications, the local Windows Action Center notification database may be corrupted:

1. Press Win + R, paste the following path, and press Enter: %localappdata%\Microsoft\Windows\ActionCenterCache
2. If files exist within this directory, select and delete them.
3. Restart your computer to allow the Windows Push Notification Platform to regenerate a clean toast database.

---

Diagnostic Escalation

If clicking a notification causes Outlook to crash entirely instead of displaying an error message, the underlying WebView2 runtime or application package may be failing:

• New Outlook Crashing on Startup (The WebView2 Runtime Fix)