Skip to content

Recall Policies and Settings as Evidence

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.

Published on 9 min read

TL;DR. Recall's policies live under Policies\Microsoft\Windows\WindowsAI, in the SOFTWARE hive for the device and in each NTUSER.DAT for that user. AllowRecallEnablement (device only) decides whether the Recall component exists at all; DisableAIDataAnalysis decides whether snapshots may be saved, and setting it to 1 deletes the ones already saved. Storage, age, app and website filters, export and DLP have their own values, mostly on Enterprise and Education only. Read them as what was allowed, not what happened: the user's opt-in has no documented registry value, and the store in the profile is the evidence of use. Microsoft's own pages disagree on two defaults, so quote the value you found and the documented meaning, with the page date. The tool on this site reads these values from SOFTWARE and NTUSER.DAT and reports them next to the store's footprint.

Where the values live

HiveKeyApplies to
SOFTWAREPolicies\Microsoft\Windows\WindowsAI (live: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsAI)The device, all users
NTUSER.DATSoftware\Policies\Microsoft\Windows\WindowsAI (live: HKCU\... for the signed-in user)That user

The Group Policy settings are under Windows Components > Windows AI, from WindowsCopilot.admx. The same policies can be delivered by MDM through the WindowsAI Policy CSP. On a device managed that way, the effective policy state can also be kept elsewhere in SOFTWARE (the PolicyManager key); if the Policies keys are empty on a managed device, look there before concluding that no policy applied.

The values

From the WindowsAI Policy CSP and Manage Recall. "From 26100.3915" means Windows 11 24H2 with KB5055627 (April 2025) and later.

ValueScopeDataMeaningEditions, builds
AllowRecallEnablementDevice0, 10: Recall not available; the component is disabled, its files removed and saved snapshots deleted, after a restart. 1: availablePro, Enterprise, Education; from 26100.3915
DisableAIDataAnalysisDevice and user0, 11: snapshots are not saved, and existing ones are deleted when the policy takes effect. 0: users may choose to save snapshotsPro, Enterprise, Education; from 26100.3915
SetMaximumStorageSpaceForRecallSnapshotsDevice and userMB: 0 (Windows decides), 10240, 25600, 51200, 76800, 102400, 153600Space cap; the oldest snapshots are deleted firstEnterprise, Education; from 26100.3915
SetMaximumStorageDurationForRecallSnapshotsDevice and userDays: 0 (Windows decides), 30, 60, 90, 180Maximum age of a snapshot. With both limits set, the first one reached appliesEnterprise, Education; from 26100.3915
SetDenyAppListForRecallDevice and userText, ;-separated AUMIDs or executable namesApplications never captured. Takes effect after a restartEnterprise, Education; from 26100.3915
SetDenyUriListForRecallDevice and userText, ;-separated URIsWebsites never captured in supported browsers; a site also covers its subdomains and paths. Takes effect after a restartEnterprise, Education; from 26100.3915
AllowRecallExportDevice0, 11: users in the European Economic Area may export their snapshotsEnterprise, Education; Insider builds per the CSP page

Two more policies matter less as evidence. Set Data Loss Prevention Provider (CSP SetDataLossPreventionProvider, from 26100.6725) names a DLP provider, such as Microsoft Purview, that tells Recall which windows to remove from a snapshot; the CSP page does not give its registry value. DisableRecallDataProviders (user, Insider builds) controls extra details from App Actions providers, such as meeting attendees. DisableClickToDo does not affect Click to Do inside Recall.

Microsoft documents no TurnOffSavingSnapshots value: "Turn off saving snapshots for use with Recall" is the friendly name of DisableAIDataAnalysis. Some third-party hardening scripts write a TurnOffSavingSnapshots value anyway (for example fkie-cad's windowsScripts); what Windows does with it is undocumented, so it shows that such a script ran, not that saving was turned off.

What each value proves

AllowRecallEnablement = 0

An administrator decided that Recall should not exist on the device. When it took effect, Recall's files were removed and any saved snapshots were deleted. Consequences:

  • A missing store on this device says nothing about whether a user had Recall before the policy arrived.
  • A store with writes after the policy's arrival is a contradiction to explain: the policy was not applied, was applied later than you think, or was changed.

DisableAIDataAnalysis = 1

No snapshots should be saved while it is in force, for the device (SOFTWARE) or for that user (NTUSER.DAT); saved snapshots are deleted when it takes effect. The same two consequences apply.

DisableAIDataAnalysis = 0, or no value

Users were allowed to save snapshots. That is permission, not use. Microsoft says administrators cannot start saving snapshots for a user; the user opts in. Note also that Microsoft's text about an absent value describes managed devices: "If the policy isn't configured, snapshots won't be saved". On an unmanaged Copilot+ PC there is usually no policy at all, and each user decides.

Storage and age limits

They bound how far back the store can reach. With a 30-day limit, no snapshot older than 30 days should exist; with a 10 GB cap, a busy user's history may cover only weeks. A store that starts at a certain date is not evidence of deletion if the limits explain it.

Deny lists

They explain gaps. If ms-teams.exe is on the list, no snapshot of Teams is expected, and a missing chat proves nothing. Microsoft notes that parts of a filtered website can still appear: embedded content, the browser's history, a tab in the background.

AllowRecallExport = 1

Users could export their snapshots. An export is encrypted, sits outside the store, and survives Reset Recall. Microsoft's decryption sample turns it into .jpg and .json pairs with the user's 32-character export code, which Recall shows once during setup. If export was allowed and the case needs the content, ask whether the user exported, and where.

What no value shows

  • The user's opt-in. No documented value. The evidence is the store: see what released builds leave on a disk image.
  • The user's own settings: the storage and age they chose, their app and website filters, pauses. Microsoft documents none of them in the registry. BDO reported a CaptureExclusion value holding exclusions in Base64, without publishing its location (BDO); treat it as a lead to search for in your own hives, not as a documented artifact.
  • Whether the Recall feature is installed. On a live system, Dism /Online /Get-FeatureInfo /FeatureName:Recall or Get-WindowsOptionalFeature -Online -FeatureName Recall gives the state: enabled, disabled, or disabled with the payload removed. No public source documents where an offline image keeps this state for Recall.

When the documentation disagrees

Microsoft's pages are not consistent, and they have changed since 2024:

  • Default age. Manage Recall says that without SetMaximumStorageDurationForRecallSnapshots, snapshots stay until the space limit is reached. The CSP page says the maximum is then 90 days, unless the user picks another value. Hagenah's test machine reported 90 days.
  • AllowRecallEnablement default. The CSP page lists a default value of 1, "Recall is available", and also says that when the policy is not configured, users have the Recall component in a disabled state. Manage Recall says Recall is removed by default on managed devices.
  • Biometrics. Microsoft's privacy page says a biometric sign-in must be enabled to use Recall. Kevin Beaumont found that after setup, the Windows Hello PIN alone opens Recall and can turn it back on. Microsoft's architecture post does describe the PIN as a fallback after setup.
  • 2024. Beaumont noted in May 2024 that the Group Policy for the preview had been renamed and that Microsoft's documentation did not match. Values found on a machine from that period may not follow today's tables.

In a report, give the value found, the documented meaning, the page and its date.

Times and tampering

The key's last write time is when the key last changed, but Group Policy processing can rewrite policy keys, so it may be a policy refresh rather than the moment someone changed a value. Compare with the Group Policy operational log and with your knowledge of the GPO.

Policies are also a target. SigmaHQ has rules for reg.exe deleting DisableAIDataAnalysis or setting it to 0, as an attacker might to re-allow Recall for collection. Remember the second step: saving snapshots still needs the user's opt-in with Windows Hello. A relaxed policy followed by a store whose first writes come after it, in an intrusion window, is worth a careful look. More in Recall in an intrusion.

FAQ

Which registry value shows that Recall was turned on?

None that Microsoft documents. Saving snapshots is an opt-in each user makes in Recall or in Settings, with Windows Hello. The policy values under Policies\Microsoft\Windows\WindowsAI show what an administrator allowed or forbade. Whether the user actually turned Recall on shows in the store in their profile.

What does DisableAIDataAnalysis = 1 mean?

Snapshots are not saved for Recall, and snapshots saved before are deleted when the policy takes effect. In SOFTWARE it applies to the whole device; in a user's NTUSER.DAT it applies to that user. Its Group Policy name is Turn off saving snapshots for use with Recall.

Is there a TurnOffSavingSnapshots value?

Not in Microsoft's documentation. Turn off saving snapshots for use with Recall is the friendly name of the DisableAIDataAnalysis policy, and that is the registry value name to look for. Some third-party hardening scripts also write a TurnOffSavingSnapshots value; Microsoft does not document what Windows does with it, so read it as a sign that someone ran such a script, not as a setting that took effect.

Can an administrator turn Recall on for a user?

No, according to Microsoft. An administrator can make Recall available and allow users to save snapshots; each user must still opt in. A relaxed policy is therefore permission, not proof of use.

Frequently asked questions

Which registry value shows that Recall was turned on?

None that Microsoft documents. Saving snapshots is an opt-in each user makes in Recall or in Settings, with Windows Hello. The policy values under Policies\Microsoft\Windows\WindowsAI show what an administrator allowed or forbade. Whether the user actually turned Recall on shows in the store in their profile.

What does DisableAIDataAnalysis = 1 mean?

Snapshots are not saved for Recall, and snapshots saved before are deleted when the policy takes effect. In SOFTWARE it applies to the whole device; in a user's NTUSER.DAT it applies to that user. Its Group Policy name is Turn off saving snapshots for use with Recall.

Is there a TurnOffSavingSnapshots value?

Not in Microsoft's documentation. Turn off saving snapshots for use with Recall is the friendly name of the DisableAIDataAnalysis policy, and that is the registry value name to look for. Some third-party hardening scripts also write a TurnOffSavingSnapshots value; Microsoft does not document what Windows does with it, so read it as a sign that someone ran such a script, not as a setting that took effect.

Can an administrator turn Recall on for a user?

No, according to Microsoft. An administrator can make Recall available and allow users to save snapshots; each user must still opt in. A relaxed policy is therefore permission, not proof of use.

Related articles

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.
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.
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.