Microsoft reboots Windows Recall with proof-of-presence encryption

Three months after a massive privacy backlash forced Microsoft to shelf its controversial Windows Recall feature, the tool is back with an entirely rebuilt security architecture.

Recall uses AI to snapshot a user's screen every five seconds, creating a searchable visual timeline of everything done on the PC. Security researchers quickly demonstrated that early builds stored those snapshots and extracted texts in plain text or easily accessible databases, turning the feature into a potential goldmine for infostealers.

Now, Microsoft says it has rebuilt the feature from the ground up.

Proof-of-presence and secure enclaves

In an interview with SecurityWeek, Microsoft VP David Weston said the company has never built anything this significant on the client side. The biggest change under the hood is proof-of-presence encryption.

Snapshots and their underlying vector databases are now encrypted with keys protected by the hardware TPM chip and strictly tied to Windows Hello Enhanced Sign-in Security. Simply put, malware cannot grab the keys in the background; you have to physically sit in front of the machine and authenticate via facial recognition or fingerprint.

Microsoft also isolated the entire processing pipeline inside Virtualization-Based Security (VBS) enclaves outside the main OS. The architecture uses a just-in-time authorization model: access is granted temporarily, and data is wiped from memory as soon as the session times out. Sensitive snapshots are shielded so thoroughly that even a user with full administrator rights cannot access the raw data.

Opt-in by default, with complete removal

Recall will no longer run automatically. It is now strictly an opt-in toggle during setup, and users have the option to uninstall the feature entirely from Windows.

To prevent recording sensitive details, Microsoft pulled in data loss prevention (DLP) tech from its enterprise product, Microsoft Purview. The system actively scans snapshots in the background to filter out passwords, credit card numbers, and national IDs.

Private browsing sessions are automatically ignored, users can blacklist specific apps or sites, and a system tray icon clearly indicates whenever snapshots are being saved, allowing users to pause capture or purge past time windows on the fly.

Why it matters

Microsoft learned a painful but necessary lesson: local AI is not automatically private AI. Storing unencrypted continuous screenshots locally was an indefensible security oversight, and this overhaul sets a crucial new security baseline for the Copilot+ PC era.

We think wrapping the entire pipeline in hardware TPM keys, VBS secure enclaves, and biometric proof-of-presence is a genuinely clever architectural shift. Denying access even to local administrators closes the exact attack vectors researchers demonstrated earlier this year.

For users who actually want an omnipresent AI memory, Recall now looks safe enough to test without handing total control to potential malware. However, the friction is real: constant biometric prompts will test user patience, and running DLP scans alongside background encryption will inevitably tax local system resources. Microsoft may have fixed the engineering flaws, but rebuilding user trust will take far longer.