Collecting Recall Data Lawfully on a Live System
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.
TL;DR. Settle authority first: a Recall store is a screen history, full of other people's messages, privileged advice and private life. Then, from an elevated prompt reached remotely, record the status (build, DISM feature state, the WindowsAI policy values, a listing of every CoreAIPlatform.00 folder), copy each store with robocopy /B keeping ukg.db with its -wal and -shm, and save SOFTWARE and every NTUSER.DAT. Do not open Recall, change a Recall setting or policy, reset, remove or pause it, or touch Windows Hello: several of those delete snapshots. On a released build the copy is encrypted, and only the user's own authenticated session can show its content. Drop the result on the tool; the collection guide on the home page summarises the steps.
Before you start: authority and scope
A Recall store holds whatever was on the user's screen, every few seconds, for weeks or months: their colleagues' and family's messages, video calls with live captions (Beaumont), banking and health pages, emails from lawyers. Messages deleted in the chat application, including disappearing messages, stay in the snapshots that showed them. That changes the legal questions.
- Authority that names it. A warrant, a court order or an internal mandate written for "the laptop's files" may not cover a screen history. Ask for wording that covers screen captures and the text extracted from them.
- A time window. Agree on the period that matters, and look only at that period.
- Privileged content. Agree a review protocol (a separate review team, keyword screening) before anyone reads the OCR text, as you would for a mailbox.
- Third parties. Data protection law applies to everyone who appears in the snapshots, not only to the device's user. Involve counsel and, where they exist, the data protection officer and employee representatives.
- Consent. On a released build, the content opens only through the user's Windows Hello. Whether you may ask the user to open it, and under what conditions, is a legal question. Never use a user's PIN or biometrics without their consent and a legal basis: that is access to their account, whatever the purpose.
This is general guidance, not legal advice.
Your own footprint
Recall saves snapshots of the session it runs in. If you work in the user's session, at the console or through a remote-control tool that shares their desktop, your windows, commands and any password you type can become snapshots in their store, mixed with the evidence. Work from a remote shell (PowerShell remoting, your EDR's live response, a Velociraptor client) and write down what you ran and when.
Actions that destroy or lock away data:
| Action | Effect, according to Microsoft |
|---|---|
Setting DisableAIDataAnalysis to 1 | Saved snapshots are deleted |
Setting AllowRecallEnablement to 0 | Recall removed and saved snapshots deleted, after a restart |
| Reset Recall, or removing the Recall feature | All snapshots deleted |
| Removing Windows Hello, resetting the PC | Snapshots cannot be restored |
| Turning off "Save snapshots" | The documentation does not say what happens to existing snapshots |
Do not apply "turn off Recall" guidance to a system under investigation before collection. Pausing Recall needs the user's Windows Hello to resume and changes what is recorded; leave it alone.
Record the status
In an elevated PowerShell prompt:
$case = 'E:\case\FIN-WKS-07'
New-Item -ItemType Directory -Force -Path "$case\recall", "$case\hives" | Out-Null
# 1. Build: which generation of Recall a store can be
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' |
Select-Object CurrentBuild, UBR, DisplayVersion | Out-File "$case\recall\build.txt"
# 2. Recall feature state (Enabled, Disabled, Disabled with Payload Removed)
Dism /Online /Get-FeatureInfo /FeatureName:Recall | Out-File "$case\recall\feature.txt"
# 3. Device policy
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsAI" /s *>&1 |
Out-File "$case\recall\policy-device.txt"
# 4. Footprint of every store: names, sizes, UTC times
Get-ChildItem 'C:\Users\*\AppData\Local\CoreAIPlatform.00' -Recurse -Force -ErrorAction SilentlyContinue |
Select-Object FullName, Length, CreationTimeUtc, LastWriteTimeUtc |
Export-Csv "$case\recall\footprint.csv" -NoTypeInformation
reg query HKCU\... in your elevated prompt reads your own hive, not the user's. User policy values come from each user's NTUSER.DAT, saved below. If the listing in step 4 fails on access, note it: the copy in backup mode below will still work. Do not change permissions on the original folder to read it; the 2024 TotalRecall script grants itself access with icacls, which alters the evidence.
Copy the stores
# 5. Each user's CoreAIPlatform.00 folder, with file and folder times
foreach ($p in Get-ChildItem 'C:\Users' -Directory -Force) {
$src = Join-Path $p.FullName 'AppData\Local\CoreAIPlatform.00'
if (Test-Path -LiteralPath $src) {
robocopy $src "$case\recall\$($p.Name)\CoreAIPlatform.00" /E /B /COPY:DAT /DCOPY:T /XJ /R:1 /W:1
}
}
- Keep the database and its side files together.
ukg.db-walcan hold the latest snapshots;ukg.db-shmhelps a reader check it. Copy all three in one pass, and do not open the originals with a SQLite client, which may checkpoint the WAL into the database. - If a file is locked, robocopy reports a sharing violation. Use a tool that reads NTFS directly (KAPE, Velociraptor) or a Volume Shadow Copy, and note which method gave which file.
- One folder per user. The profile folder the store came from is what attributes it.
Save the hives
The policy values are in SOFTWARE and in each NTUSER.DAT:
# 6. SOFTWARE, always loaded
reg save HKLM\SOFTWARE "$case\hives\SOFTWARE" /y
# 7. Loaded profiles: save each hive by SID
$profiles = Get-CimInstance Win32_UserProfile | Where-Object { -not $_.Special }
foreach ($p in $profiles | Where-Object Loaded) {
$name = Split-Path $p.LocalPath -Leaf
New-Item -ItemType Directory -Force -Path "$case\hives\$name" | Out-Null
reg save "HKU\$($p.SID)" "$case\hives\$name\NTUSER.DAT" /y
}
# 8. Profiles not loaded: copy the hive with its transaction logs
foreach ($p in $profiles | Where-Object { -not $_.Loaded }) {
$name = Split-Path $p.LocalPath -Leaf
robocopy $p.LocalPath "$case\hives\$name" NTUSER.DAT NTUSER.DAT.LOG1 NTUSER.DAT.LOG2 /B /COPY:DAT /A-:SH /R:1 /W:1
}
# 9. Hashes outside the case folder, then an archive
Get-ChildItem $case -Recurse -File -Force | Get-FileHash -Algorithm SHA256 |
Export-Csv "$case.sha256.csv" -NoTypeInformation
tar.exe -a -c -f "$case.zip" -C $case .
KAPE and Velociraptor
The KAPE target WindowsCopilotRecall, by Zach Stanford and Phill Moore, copies C:\Users\*\AppData\Local\CoreAIPlatform.00\UKP\ recursively. It was not part of KapeTriage or !SANS_Triage when this article was written, so name it:
kape.exe --tsource C: --tdest E:\case\FIN-WKS-07 --target WindowsCopilotRecall,RegistryHivesUser,RegistryHivesSystem
RegistryHivesSystem brings SOFTWARE; RegistryHivesUser brings every NTUSER.DAT with its logs. The target covers UKP\ only; the footprint listing above covers the rest of CoreAIPlatform.00.
In Velociraptor, Windows.Triage.Targets offers the same WindowsCopilotRecall target, built from the KAPE definitions. The exchange artifacts Windows.System.Recall.AllWindowEvents and Windows.System.Recall.WindowCaptureEvent query ukg.db on the endpoint; they need a readable 2024-era database and return nothing useful from an encrypted one. Collect the files either way.
When the store is encrypted
On a released build, everything above gives you encrypted files and a footprint, which is still evidence (see what released builds leave). Microsoft says administrators cannot view a user's snapshots. The content opens only in the user's own session, after Windows Hello. The routes to it are legal before they are technical:
- The user, with authority and consent, opens Recall and shows the relevant period while you record what is shown. Agree in advance what will be searched, and document it as you would any assisted examination.
- Export, in the European Economic Area. Where the
AllowRecallExportpolicy allows it, the user can export their snapshots with Windows Hello. The export is encrypted; Microsoft's documented sample decrypts it into.jpgand.jsonpairs with the user's 32-character export code. The tool on this site reads Recall stores, not exports.
Do not run tools that inject code into Recall's processes, such as the 2026 research tool TotalRecall Reloaded, on a system under investigation. They are attack demonstrations: they change the system, depend on the user unlocking Recall, and would be hard to defend as a forensic method.
From a disk image
Mount the Windows volume read-only and copy Users\*\AppData\Local\CoreAIPlatform.00\, Windows\System32\config\SOFTWARE* and Users\*\NTUSER.DAT*. Recall requires BitLocker or Device Encryption, so expect to need the recovery key first. Disk Image Parser can hand the store and the hives found in an image to the tool, in the browser.
Handling the copies
Treat a Recall store as you would a password vault: it often contains passwords and tokens that were on screen.
- Encrypt it at rest, restrict access to named people, and log who opened it.
- Hash on collection and work on copies.
- Review only the agreed time window; mask credentials and third-party personal data in reports.
- Do not upload it to online services. The tool on this site runs in the browser and sends nothing anywhere.
What to do with the result is in the FIN-WKS-07 walk-through.
FAQ
Can an administrator read a user's Recall snapshots?
Not on released builds. Microsoft says IT administrators cannot access or view snapshots, and the files an administrator copies stay encrypted. Only the user's own Windows Hello session unlocks them in Recall. Stores from the May and June 2024 pre-release builds are plain files, readable once copied.
Can my collection change the Recall store?
Yes. If Recall is saving snapshots in the session you work in, your own windows become snapshots in the user's history. Turning off saving snapshots or Recall itself by policy, resetting Recall or removing it deletes snapshots, and removing Windows Hello makes them unrecoverable. Work from a remote shell and change nothing.
Does KAPE collect the Recall store?
Yes, with the WindowsCopilotRecall target, which copies C:\Users*\AppData\Local\CoreAIPlatform.00\UKP\ recursively. It was not part of the KapeTriage or !SANS_Triage compound targets when this article was written, so name it explicitly. Velociraptor's Windows.Triage.Targets offers the same target.
Do I need the user's consent?
That depends on the jurisdiction, the employment relationship and the legal basis of the investigation. A Recall store is a record of what was on someone's screen, so get advice and written authority that covers it explicitly. This article is not legal advice.
Related articles
Collect Windows Recall data from a live system
Confirm authority, record Recall's status, copy each user's Recall store with its SQLite side files, save the SOFTWARE hive and each NTUSER.DAT, hash the result, then load it in the browser.
- Time
- 20 min
- Tools
- Written authority for the collection, An elevated PowerShell prompt, robocopy, reg.exe and DISM (built in), The Windows Recall tool (browser)
- Result
- A folder or zip with one CoreAIPlatform.00 folder per user, the SOFTWARE hive, one NTUSER.DAT per user, a status record and SHA-256 hashes.
Confirm authority and scope
Get written authority that covers screen history, including third-party and privileged content, and agree a time window and a review protocol before touching the system.
Record Recall's status
From an elevated prompt, record the build, the Recall feature state with DISM, the WindowsAI policy values, and a listing of every CoreAIPlatform.00 folder with sizes and UTC times.
Copy the stores
Copy each user's CoreAIPlatform.00 folder with robocopy in backup mode, keeping ukg.db, ukg.db-wal and ukg.db-shm together and keeping file times.
Save the hives
Save HKLM\SOFTWARE with reg save and each loaded user's hive through HKU\<SID>; copy NTUSER.DAT with its LOG1 and LOG2 files for profiles that are not loaded.
Hash, archive and load
Compute SHA-256 hashes, keep them outside the case folder, zip the folder, and drop it on the tool, which runs in the browser and uploads nothing.
Frequently asked questions
Can an administrator read a user's Recall snapshots?
Not on released builds. Microsoft says IT administrators cannot access or view snapshots, and the files an administrator copies stay encrypted. Only the user's own Windows Hello session unlocks them in Recall. Stores from the May and June 2024 pre-release builds are plain files, readable once copied.
Can my collection change the Recall store?
Yes. If Recall is saving snapshots in the session you work in, your own windows become snapshots in the user's history. Turning off saving snapshots or Recall itself by policy, resetting Recall or removing it deletes snapshots, and removing Windows Hello makes them unrecoverable. Work from a remote shell and change nothing.
Does KAPE collect the Recall store?
Yes, with the WindowsCopilotRecall target, which copies C:\Users\*\AppData\Local\CoreAIPlatform.00\UKP\ recursively. It was not part of the KapeTriage or !SANS_Triage compound targets when this article was written, so name it explicitly. Velociraptor's Windows.Triage.Targets offers the same target.
Do I need the user's consent?
That depends on the jurisdiction, the employment relationship and the legal basis of the investigation. A Recall store is a record of what was on someone's screen, so get advice and written authority that covers it explicitly. This article is not legal advice.