Windows Recall in Release Preview: Security Fixes, Requirements, and Ongoing Privacy Concerns

Microsoft’s Windows Recall feature, now in the Release Preview Channel for Windows Insiders, is a bold attempt to redefine how users interact with their PCs. By taking periodic screenshots of your screen, analyzing them with AI, and storing them in a searchable database, Recall promises to help you retrace your digital steps effortlessly. Think of it as a photographic memory for your computer—search for a document, webpage, or even a fleeting moment from weeks ago using natural language. But while the feature is intriguing, its rocky history and lingering privacy concerns make it a polarizing addition to Windows 11. In this article, we’ll dive into Recall’s current state, its troubled beginnings, the security measures Microsoft has implemented, and the implications for users as it nears a broader release.

A Rocky Start: Recall’s Security Nightmare

When Microsoft unveiled Recall in May 2024, it was pitched as a flagship feature for Copilot+ PCs, designed to leverage powerful neural processing units (NPUs) for on-device AI processing. The idea was simple: Recall would capture snapshots of your screen every few seconds, use optical character recognition (OCR) to extract text, and store everything in a local database for easy retrieval. However, the initial implementation was a security disaster, sparking widespread criticism from researchers, privacy advocates, and users.

The original version of Recall had several glaring flaws:

• Plaintext Storage: All snapshots and extracted data were stored unencrypted on the hard drive, making it trivially easy for anyone with access to the PC—whether a malicious user or malware—to view sensitive information like passwords, banking details, or confidential documents.
• No Content Moderation: Recall captured everything without filtering sensitive data. Passwords, credit card numbers, and even private messages in apps like Signal were recorded unless users manually excluded specific apps or websites.
• Opt-Out by Default: The feature was enabled automatically on Copilot+ PCs, meaning users had to actively disable it to avoid data collection. This was particularly risky for shared PCs, where one user’s activity could be exposed to others.
• Bypassing Hardware Requirements: Security researchers, using tools like AmperageKit, enabled Recall on unsupported hardware, exposing its vulnerabilities even further. This revealed that Microsoft had rushed the feature without proper testing through the Windows Insider Program, bypassing its usual rigorous preview process.

The backlash was swift. Security experts labeled Recall a “potential security nightmare,” with ethical hacker Alexander Hagenah demonstrating how his TotalRecall tool could extract sensitive data from the database. Privacy advocates warned of abuse in scenarios like intimate partner violence, where an abuser could access a victim’s activity. The feature’s ability to capture disappearing messages from secure apps like Signal raised additional red flags.

Microsoft’s timing couldn’t have been worse. The company had just pledged to prioritize security over all else, following high-profile breaches and CEO Satya Nadella’s directive to “do security” above other priorities. Yet, Recall’s initial rollout seemed to ignore these commitments, eroding user trust further. By June 2024, Microsoft delayed Recall’s launch, pulled it from the Release Preview Channel, and promised a complete overhaul.

The Current State: Recall in Release Preview

Fast forward to April 2025, and Recall is back in the Windows Insider Release Preview Channel (Build 26100.3902), signaling that Microsoft is nearing a public rollout. The feature is now limited to Copilot+ PCs—those with NPUs capable of at least 40 trillion operations per second (TOPS), 16GB of RAM, and 256GB of storage. It’s been tested extensively in less-stable Insider channels like Dev and Beta since late 2024, and the Release Preview phase is the final step before broader availability.

Microsoft has addressed many of the original criticisms, implementing significant security and privacy enhancements:

• Opt-In by Default: Recall now requires users to explicitly enable snapshot saving during setup, reducing the risk of unintended data collection.
• Encrypted Data: All snapshots and the search index database are encrypted using Device Encryption or BitLocker, with keys stored in the system’s Trusted Platform Module (TPM). Data is decrypted “just in time” using Windows Hello authentication (face, fingerprint, or PIN), ensuring only authorized users can access it.
• Virtualization-Based Security (VBS): Recall operates within a VBS enclave, isolating its data from the rest of the system to protect against malware or unauthorized access. Secure Boot and Hypervisor-Protected Code Integrity (HVCI) are mandatory, though these settings may impact gaming performance on some systems.
• Sensitive Data Filtering: Automated filters now attempt to block sensitive information like passwords and credit card numbers from being stored. Users can also manually exclude specific apps, websites, or private browsing sessions in supported browsers like Edge, Firefox, and Chrome.
• User Control: Recall can be paused, resumed, or completely uninstalled via the “optional features” settings. Users can set storage limits, and older snapshots are automatically deleted when the limit is reached.
• Malware Protections: Rate-limiting and anti-hammering measures help prevent malware from rapidly accessing Recall’s database.

Microsoft has also subjected Recall to rigorous testing, including months of design reviews and penetration testing by its Offensive Research and Security Engineering Team, as well as an independent third-party security vendor. These changes make the current version of Recall significantly more secure than its predecessor.

System Requirements for Recall

To use Recall, your PC must meet strict hardware and software requirements, ensuring it can handle the AI-driven processing and security features. Below is a detailed chart of the prerequisites:

Note: Arm64EC (emulation-compatible) systems are not currently supported, and Recall requires enrollment in the Windows Insider Program.

Security and Privacy Implications: What’s Fixed and What’s Not

While Microsoft has addressed many of Recall’s initial flaws, the feature’s core concept—capturing and storing everything you do on your PC—still raises significant concerns. Let’s break down the security and privacy implications in depth.

What’s Been Fixed

The shift to opt-in activation is a major win for user control, ensuring that only those who want Recall will have it running. Encryption via BitLocker or Device Encryption, combined with VBS enclaves, makes it much harder for unauthorized users or malware to access Recall’s data. The requirement for Windows Hello authentication adds another layer of protection, as does the ability to uninstall the feature entirely. Automated filtering of sensitive data, while not perfect, reduces the risk of storing passwords or financial details.

Microsoft’s decision to put Recall through the full Windows Insider testing pipeline has also paid off. Months of scrutiny in experimental channels have allowed the company to iron out bugs and vulnerabilities, unlike the rushed initial rollout. The addition of malware protections like rate-limiting shows that Microsoft is taking the threat of targeted attacks seriously.

Lingering Concerns

Despite these improvements, Recall’s comprehensive data collection remains a double-edged sword. Even with encryption and filtering, the feature creates a treasure trove of personal data that could be exploited by sophisticated attackers. Well-funded threat actors, such as state-sponsored groups from China, Russia, or North Korea, may develop methods to bypass VBS enclaves or exploit zero-day vulnerabilities to access Recall’s database. Organized crime groups could create malware that activates Recall on disabled systems, turning it into a surveillance tool.

Privacy concerns are equally pressing. Recall’s snapshots can capture sensitive material from other users if they share a PC or send content to someone with Recall enabled. For example, if User A sends a confidential document to User B, and User B has Recall active, that document could be stored in User B’s Recall database without User A’s consent. This is particularly worrying in workplace settings or for users in abusive relationships, where Recall could expose private communications or activities.

The feature’s reliance on local storage also raises legal risks. Recall’s database could be subject to subpoenas by law enforcement or civil litigants, potentially exposing months of user activity. Additionally, while Microsoft claims Recall doesn’t share data with third parties, the mere existence of such a detailed archive on a user’s PC feels invasive to many. As one privacy advocate noted, “This feature makes it that even a well-intentioned person might wrongly assume it is secure enough.”

Finally, Recall’s content filtering is imperfect. While it attempts to block sensitive data, there’s no guarantee it will catch everything, especially in complex scenarios like handwritten notes or custom applications. Users must remain vigilant and manually exclude apps or websites to mitigate risks.

The Trust Problem

Beyond technical concerns, Recall faces a deeper issue: Microsoft’s eroded trust with users. Years of pushing ads, unwanted apps, and aggressive account sign-in prompts in Windows 11 have left many skeptical of the company’s intentions. Recall’s original botched launch only reinforced this distrust, and even with fixes, the feature demands an “extraordinary level of trust that Microsoft hasn’t earned.” Opening the Recall app and seeing a timeline of your work emails, personal photos, or private messages can feel inherently creepy, no matter how secure the system is.

Microsoft’s challenge now is to change public perception. Negative coverage of Recall’s initial flaws has far outpaced stories about its fixes, and many users still view it as the same flawed feature from 2024. Overcoming this will require transparent communication and a flawless rollout.

What’s Next for Recall

As Recall moves closer to general availability, likely later in 2025, Microsoft is banking on its security overhaul and opt-in model to win over users. The feature’s integration with Click to Do, an AI-powered tool that suggests actions based on screen content, adds further utility for Copilot+ PC owners. However, its success will hinge on Microsoft’s ability to address remaining privacy concerns and rebuild trust.

For now, Recall is a feature with immense potential but significant risks. If you’re a Windows Insider with a Copilot+ PC, you can test it in the Release Preview Channel to see if its benefits outweigh its drawbacks. But for most users, the decision to enable Recall will come down to one question: Do you trust Microsoft to keep your digital life secure?

Conclusion

Windows Recall in its current form is a far cry from the security disaster of 2024. Microsoft has made strides in encrypting data, adding user controls, and subjecting the feature to rigorous testing. Yet, its comprehensive data collection and potential for abuse mean it’s not without risks. As Recall nears a public release, users must weigh its productivity benefits against the privacy and security implications. For those considering enabling it, ensure your PC meets the requirements, understand the settings, and stay informed about any new developments. The future of Recall depends on Microsoft’s ability to deliver a secure, trustworthy experience—and that’s a tall order.