What Windows Recall Stores, and Where, by Version
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.
TL;DR. Recall keeps one store per user in %LOCALAPPDATA%\CoreAIPlatform.00\UKP\{GUID}\: ukg.db (window events, titles, apps, URLs, OCR text), an ImageStore folder (the snapshot images) and two vector indexes. The folder has not moved since 2024; what changed is who can read it. In the pre-release builds of May and June 2024, the files were plain SQLite and JPEG. In the reworked feature, previewed with Windows Insiders from November 2024 and rolled out to Copilot+ PCs from April 2025, saving snapshots is opt-in per user, viewing needs Windows Hello, and the snapshots and database are encrypted with keys protected by a VBS enclave. On any case, the first three questions are the build, whether the user has a store, and whether it is readable. The tool on this site reads readable stores and, for the others, reports what the files and policy keys show, without decrypting anything.
This site is independent of Microsoft.
Three generations
| Period | Builds | How Recall was turned on | Store content |
|---|---|---|---|
| May to June 2024, pre-release | Windows 11 24H2 preview builds; CyberCX used an ARM64 Azure VM with KB5037850 | By researchers, with tools such as AmperageKit. It never reached customers in this form | Plain SQLite database and JPEG files |
| November 2024 to April 2025, Windows Insider | 26120.2415 (Snapdragon, 22 November 2024), 26120.2510 (AMD and Intel, December 2024), Release Preview 26100.3902 (April 2025) | Opt-in by the user, with Windows Hello | Encrypted, according to Microsoft's architecture; Kevin Beaumont found the database encrypted in the Release Preview |
| From 25 April 2025 | 26100.3915 (KB5055627) and later, rolled out gradually to Copilot+ PCs | Opt-in per user; removed by default on managed commercial devices | Encrypted |
Microsoft's documentation still calls the feature "Recall (preview)".
The short history explains the split. Microsoft announced Recall with the first Copilot+ PCs on 20 May 2024, for 18 June. Kevin Beaumont (31 May) and CyberCX (5 June) ran it on unsupported hardware, and Alexander Hagenah published TotalRecall in early June: the store was a plain database and an image folder in the user's profile, which a program running on the machine could copy and search. On 7 June, Microsoft announced opt-in during setup, Windows Hello enrollment, "just in time" decryption and an encrypted search index. On 13 June it moved Recall to the Windows Insider program. On 27 September 2024 it published the security architecture of the reworked feature.
The store
C:\Users\<user>\AppData\Local\CoreAIPlatform.00\UKP\{GUID}\
ukg.db
ukg.db-wal, ukg.db-shm (when present)
ImageStore\
SemanticTextStore.sidb
SemanticImageStore.sidb
The GUID differs between stores: the Velociraptor artifacts and TotalRecall's example output show different values. Search with a wildcard. Each user who turns Recall on has a store in their own profile, and Microsoft says Recall does not share snapshots between users of the same device.
| Item | What 2024 research found | Released builds |
|---|---|---|
ukg.db | The main SQLite database: window events, window titles, applications, URLs, OCR text (CyberCX). Kaspersky counted 20 tables in the 2024 beta | Same file name and folder, encrypted (Beaumont, April 2025). Hagenah describes SQLite's encryption extension with AES-256-GCM (TotalRecall Reloaded) |
-wal, -shm | SQLite side files. Copy them with the database whenever they exist: a WAL can hold the latest committed changes | Encrypted with the database, as far as anyone has published |
ImageStore\ | One JPEG per snapshot, with no file extension, named after the snapshot's image token. The JPEG carries a copy of the snapshot's metadata in its EXIF MakerNote tag (CyberCX) | Microsoft says snapshots are always encrypted, each with its own key. How released builds lay snapshots out on disk is not publicly documented |
SemanticTextStore.sidb, SemanticImageStore.sidb | DiskANN vector indexes for search, in SQLite (CyberCX) | Listed by Hagenah from strings in the enclave binary. Microsoft says "any associated information in the vector database" is always encrypted |
The details of the database are in the ukg.db schema and timestamps.
What a snapshot holds
Microsoft's 2024 text said snapshots were taken every five seconds while the screen content changed; the current documentation says "periodically" and "every few seconds", under the same condition. Each snapshot gives an image and database rows for the window in focus: its title, the application's name and path, the URL for supported browsers, the OCR text of the screen, and the window's position. The database also records window events that have no image: a window created, changed (for example its title) or closed.
The released feature adds analysis on top. From the names in Recall's binaries, Hagenah lists topics, named entities (people, organisations, addresses), screen regions, time spent per application and per website, the user's own Recall searches, and an identifier that links a snapshot to the Windows activity history. He says himself that what each field holds is inferred from its name and not all verified. None of it can be read from the files offline.
What Recall does not capture
A gap in a Recall store is normal. According to Microsoft's Manage Recall page and the research:
- Private browsing in supported browsers (Edge, Firefox, Opera, Chrome, other Chromium browsers from version 124). In the 2024 preview, CyberCX found that an InPrivate window was cut out of the snapshot entirely, showing what was under it, while its title changes were still recorded as window events.
- DRM-protected content, and any window whose application excludes itself from screen capture (
SetWindowDisplayAffinitywithWDA_EXCLUDEFROMCAPTURE). - Filtered applications and websites: the user's own filter lists and the administrator's deny lists. Microsoft warns that parts of a filtered site can still appear: embedded content, the browser's history, a tab that is not in the foreground.
- Sensitive information. The filter is on by default and is meant to stop snapshots that show passwords, ID numbers or card numbers. Beaumont found it unreliable: Recall saved and indexed a card number and its CVV that he typed in a web form.
- Some remote desktop clients: Remote Desktop Connection (
mstsc.exe),VMConnect.exe, the Azure Virtual Desktop MSI client and RemoteApp windows are filtered by default. Other clients are saved unless they protect their window from capture. Beaumont found Azure Virtual Desktop apps, Windows App and AnyDesk sessions in his snapshots. - Games while Game Mode is on, audio, and continuous video.
- Periods when Recall was not saving: paused by the user ("Pause until tomorrow" resumes at midnight), less than 25 GB free on the disk, saving turned off, or the user not signed in. Hagenah lists twelve conditions checked before each capture, from names in the binaries, including idle user, battery saver and BitLocker off.
How long snapshots are kept
- Space. When nobody sets a limit, Windows allocates 25 GB on a 256 GB device, 75 GB on 512 GB and 150 GB from 1 TB. An administrator can set 10, 25, 50, 75, 100 or 150 GB (Enterprise and Education only). When the limit is reached, the oldest snapshots go first.
- Age. The administrator can set 30, 60, 90 or 180 days. Microsoft's two pages disagree on the default: Manage Recall says that without the policy, snapshots stay until the space limit is reached; the policy reference says the maximum is 90 days unless the user chooses otherwise. Hagenah's test machine reported 90 days.
- Deletion by the user. One snapshot, every snapshot of an app or website, or everything with Reset Recall, which also resets Recall's settings. Removing the Recall feature deletes the snapshots.
- Deletion by policy. Turning off saving snapshots by policy, or making Recall unavailable, deletes the snapshots already saved. See Recall policies and settings as evidence.
- Windows Hello. Microsoft warns that snapshots cannot be restored if Windows Hello is removed, or after a reset or a move to a new PC.
Deleted messages are a different matter: a message deleted in a chat application stays in the snapshots that showed it. Beaumont found disappearing Signal and WhatsApp messages and deleted Teams messages in his Recall history.
Could Recall have run at all?
Before looking for a store, check that the machine and the user could have one. Microsoft's requirements:
- A Copilot+ PC that meets the Secured-core standard, with a 40 TOPS NPU, 16 GB of RAM, 8 logical processors and 256 GB of storage. Enabling Recall needs 50 GB free.
- BitLocker or Device Encryption enabled. The Insider builds also needed Secure Boot.
- The user enrolled in Windows Hello Enhanced Sign-in Security with at least one biometric sign-in (face or fingerprint).
- On a managed commercial device (Enterprise or Education, or a device joined to a domain, enrolled in management or using a volume licence), the administrator must allow Recall by policy; the user still has to opt in. On an unmanaged Copilot+ PC, Recall is available and each user decides.
A Windows 11 laptop without an NPU has no Recall store, whatever its build. A Copilot+ PC in a company that never allowed Recall should not have one either.
Where to go next
| What you have | Read |
|---|---|
| A store that opens as SQLite | The ukg.db schema and timestamps |
| A disk image of a released build | Recall on a disk image: what released builds leave |
| Hives and a question about policy | Recall policies and settings as evidence |
| A running machine | Collecting Recall data lawfully on a live system |
| An intrusion | Recall in an intrusion: a target and a source |
FAQ
Where does Windows Recall store its data?
In each user's profile, under %LOCALAPPDATA%\CoreAIPlatform.00\UKP{GUID}: the ukg.db database, an ImageStore folder for the snapshot images, and two vector indexes, SemanticTextStore.sidb and SemanticImageStore.sidb. Researchers found the store in the same folder in the 2024 preview and in the released feature. What changed is that the released feature encrypts it.
Can I open ukg.db in a SQLite browser?
Only a store from the pre-release builds that researchers enabled in May and June 2024, before Microsoft reworked the feature. Released builds encrypt the database, and no public method decrypts it offline.
Is Recall on by default?
No. In the released feature, each user must opt in to saving snapshots and confirm with Windows Hello, and on managed commercial devices Recall is removed unless an administrator allows it by policy. The version shown in May 2024 was designed to be on by default; Microsoft changed that on 7 June 2024.
Does every Windows 11 PC have Recall?
No. Recall runs only on Copilot+ PCs that meet the Secured-core standard, with a 40 TOPS NPU, 16 GB of RAM, 8 logical processors and 256 GB of storage, with BitLocker or Device Encryption on, and with the user enrolled in Windows Hello Enhanced Sign-in Security with a biometric sign-in.
Related articles
Frequently asked questions
Where does Windows Recall store its data?
In each user's profile, under %LOCALAPPDATA%\CoreAIPlatform.00\UKP\{GUID}\: the ukg.db database, an ImageStore folder for the snapshot images, and two vector indexes, SemanticTextStore.sidb and SemanticImageStore.sidb. Researchers found the store in the same folder in the 2024 preview and in the released feature. What changed is that the released feature encrypts it.
Can I open ukg.db in a SQLite browser?
Only a store from the pre-release builds that researchers enabled in May and June 2024, before Microsoft reworked the feature. Released builds encrypt the database, and no public method decrypts it offline.
Is Recall on by default?
No. In the released feature, each user must opt in to saving snapshots and confirm with Windows Hello, and on managed commercial devices Recall is removed unless an administrator allows it by policy. The version shown in May 2024 was designed to be on by default; Microsoft changed that on 7 June 2024.
Does every Windows 11 PC have Recall?
No. Recall runs only on Copilot+ PCs that meet the Secured-core standard, with a 40 TOPS NPU, 16 GB of RAM, 8 logical processors and 256 GB of storage, with BitLocker or Device Encryption on, and with the user enrolled in Windows Hello Enhanced Sign-in Security with a biometric sign-in.