Windows 11 lets you see notifications in the Action Center, but there is no way to search them. They disappear the moment you dismiss them, and even the ones still visible can only be scrolled — not filtered, not searched by keyword, not grouped. If you need to find what that Outlook alert said yesterday, you're out of luck. Notification Logger fixes this with a full searchable notification history.

Why Windows Doesn't Let You Search Notifications

The Windows Action Center is designed as a transient tray — it shows recent notifications and clears them once dismissed. Microsoft never built a persistent, searchable log because the expected workflow is: see notification → act on it → dismiss it. For anyone who needs to look back at notifications — support engineers, developers, busy professionals — this design is a significant gap.

Common situations where search would help:

Email previews you dismissed too fast

You saw a notification about an important email, swiped it away before reading the subject line, and now can't find the message in a crowded inbox.

Security and system alerts

Windows Defender, backup software, or a VPN posted a warning while you were away. You need to find when it appeared and what it said.

Build or deployment alerts

Your CI/CD pipeline sends desktop notifications for failed builds. You need to find all "failed" alerts from a specific project today.

Missed meeting reminders

You're on a call and a calendar reminder fires. Later you need to know what time the meeting was and whether there was a link in the notification.

How Notification Logger's Search Works

Notification Logger captures every incoming notification and stores it in a local database. The main window provides a real-time search bar that filters across all saved fields: app name, notification title, and notification body. Results narrow instantly as you type.

Keyword search

Type any word or phrase into the search bar. Notification Logger filters the grid to show only notifications whose title or body contains that text. The match is case-insensitive by default.

Practical examples:

Search term What it finds
invoice Any notification mentioning an invoice — from email, accounting software, etc.
failed Build failures, backup errors, login failures across all apps
meeting Calendar reminders and video call alerts containing the word "meeting"
security Windows Defender and antivirus alerts
order Shopping and delivery notifications from e-commerce apps or email
disk Low-disk-space warnings and storage alerts

Filter by app

Use the App filter to limit results to a single application. This is useful when you know which app sent the notification but don't remember the exact text — for example, showing only Slack or Outlook notifications.

Filter by date range

The date picker lets you narrow results to a specific day, week, or custom date range. Combined with keyword search, this pinpoints a notification quickly: "security alerts from Windows Defender in the last 7 days".

Regex search

For power users, enable Regular Expressions in Settings. This unlocks the full expressive power of regex in the search bar. Examples:

Regex pattern Matches
fail(ed|ure) Notifications containing "failed" or "failure"
\b(error|warning)\b Exact word "error" or "warning", not "errorless"
order #\d+ Order confirmation notifications with a numeric order ID
(?i)urgent The word "urgent" in any letter case
build \d+ (pass|fail) CI build result notifications with a build number
Enable regex in Settings: Open the gear icon → toggle Regular expressions On. The search bar then accepts full .NET regex syntax. Toggle it back off when doing plain keyword searches.

Using Favorites to Pin Keyword-Matched Notifications

Once you find a notification that matters, star it as a Favorite. Favorited notifications are:

  • Excluded from automatic deletion (even if data retention is set to 14 days)
  • Instantly accessible via the Favorites filter in the toolbar
  • Kept indefinitely, regardless of your retention settings

This makes Favorites the right place to keep one-off critical alerts — a security warning, a license key, a shipping notification — that you don't want to lose to the retention window.

Grouping Results by App

After filtering by keyword, click the Group button to collapse all results by app name. This shows you at a glance which applications are responsible for the matching notifications. Useful when investigating: "which app keeps sending error notifications?"

Practical Search Workflows

Finding a specific email alert

  1. Type the sender's name or subject keywords into the search bar
  2. Set the app filter to Outlook or your email client
  3. Narrow the date range to when you expected the email
  4. Copy the notification text via double-click (with "Copy cell text" enabled in Settings)

Auditing security events

  1. Search for threat, virus, blocked, or quarantine
  2. Filter to Windows Security or your antivirus app
  3. Use a date range covering the period in question
  4. Export results as CSV for a formal security review

Reviewing failed build notifications

  1. Enable regex in Settings
  2. Search for build .*(fail|error)
  3. Group by app to see which pipeline produced the most failures

Frequently Asked Questions

Can I search notifications from before I installed the app?
No. Notification Logger can only search notifications that arrived after installation and after permissions were granted. Windows does not expose historical notifications to third-party apps.
How far back can I search?
As far back as your data retention setting allows. The default is 14 days, but you can change this in Settings → "Clean notifications older than _ days". Set it to a large number (e.g., 365) to keep a year of history. Favorited notifications are kept forever regardless of this setting.
Does it search inside notification images or attachments?
Notification Logger searches text fields only: app name, notification title, and notification body. Windows notification images and action button labels are not indexed.
Is the regex syntax the same as Python or JavaScript?
Notification Logger uses .NET regex syntax, which is very similar to both. Common patterns work identically. The main differences are in some named group and lookahead syntax, but for keyword searches and basic patterns the three are interchangeable.
Can I save a search to run it again later?
There is no saved-search feature. For frequently needed searches, note your keyword and date range. The search bar remembers the last entry for the current session.

Start building a searchable notification history on Windows 10 / 11