Skip to content

Blog

Articles on Windows Recall for investigators: where the store lives, what each version keeps readable, the policy keys, and how to read snapshots carefully.

Check Recall's status, copy the CoreAIPlatform.00 store with its WAL, save the policy hives, and settle authority, privilege and third-party content first.
On a disk image of a released build, Recall content is encrypted. What you can still establish: which user had Recall, when it was saving, and deletions.
What attackers can take from a Recall store (infostealers, TotalRecall, TotalRecall Reloaded), what it gives responders, and the limits of a snapshot.
A worked example on a synthetic Recall store: alice's morning, the invoice email, the .pdf.exe opened at 09:12:07, what Recall shows and what it cannot show.
The WindowsAI policy values for Recall in SOFTWARE and NTUSER.DAT, what each proves about whether snapshots could be saved, and what no value shows.
Recall's ukg.db as public research documents it: WindowCapture events, apps, URLs, OCR text, image tokens, epoch-millisecond times, and what is still unknown.
Windows Recall from the 2024 preview to the released opt-in feature: the CoreAIPlatform.00 store, ukg.db, ImageStore, and what each version lets you read.