<SYSTEMDRIVE>:\Users\<USERNAME>\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db
<SYSTEMDRIVE>:\Users\<USERNAME>\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-wal
System-wide database and Write-Ahead Logging (WAL) files:
<SYSTEMDRIVE>:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db
<SYSTEMDRIVE>:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-wal
Overview
Introduced in Windows 10, the Windows Push Notification service allows applications to deliver / push notifications, in three different forms:
-
Badge
, tiny symbol that appears in the corner of an application’s taskbar / hidden icon.Examples: the number of unread messages on
Teams
,Slack
,Discord
or other instant messaging applications. -
Tile
, rectangular shape that is displayed in the screen and linked to an application. -
Toast
, rectangular shaped pop-up box that can appear for a limited time (5 seconds by default) at the bottom right of the screen or be sent directly to theWindows Action Center
.Examples: instant messaging applications (such as
Teams
) notifying the user of a new message.
More information on Windows Push Notifications
can be found in the
“A Digital Forensic View of Windows 10 Notifications”.
Information of interest
Each notification is associated with a dedicated entry in the Notification
table of the wpndatabase.db
database. There are system-wide notifications and
per-user notifications, stored in different databases (with one database
per-user).
Each notably entry contains the arrival and expiry time of the notification, as
well as a “payload” associated with the notification. For toast notification
,
the payload contains the content of the notification. In case of
toast notifications
from instant messaging applications, or social media /
instant messaging web application accessed through a web browser, the payload
may contain the message received.
The notifications are short-lived and deleted from the database after their
expiry time or following a user acknowledgement (closing of the pop-up or
clearing from the Windows Action Center). The wpndatabase.db
database thus
provided very limited historical data.
More information might be retrievable in the Write-Ahead Logging (WAL)
file
wpndatabase.db-wal
and / or carved from the database (using tools such as
bring2lite
or
fqlite
).
References
View on GitHub