Windows Recall has emerged as one of Microsoft’s most debated features, introduced with the expansive Windows 11, version 24H2 update. This feature, exclusive to Copilot+ PCs, accompanies other innovative AI tools such as Click To Do and Image Generation. However, the reception has been far from warm, with users expressing significant concerns regarding privacy and security. In response, Microsoft has made several attempts to “recall” the feature, refining its functionality in light of user feedback.
At its core, Windows Recall operates by capturing snapshots of the user’s screen at regular intervals, employing on-device AI to analyze and categorize the content. Following its preview release for Copilot+ PCs last month, the feature has since expanded to include Intel and AMD Copilot+ systems. To address the mounting security apprehensions, Microsoft has introduced a setting aimed at filtering out sensitive information from these snapshots. This setting is designed to prevent the feature from capturing data from applications or websites that handle sensitive information, such as credit card numbers and social security details.
More critical security concerns abound for Windows Recall
Despite these precautions, a recent report by Tom’s Hardware’s Avram Plitch raises questions about the effectiveness of the filtering mechanism. In his testing, Windows Recall managed to capture sensitive financial information, including a credit card number, while he was using Windows Notepad. Even with the filtering setting enabled, the feature recorded sensitive details, including explicit labels such as “Capital One Visa” next to the captured numbers.
While Plitch acknowledged that the credentials used in his test were fabricated, he replicated similar outcomes with actual credit card information. He escalated his testing by creating an HTML page featuring a web form soliciting credit card details, including the type, number, expiration date, and security code (CVC). His intention was to see if the clear labeling would prompt Windows Recall to block or prevent the capture of sensitive information. However, the feature still took a snapshot of the page containing his financial details.
Interestingly, Plitch found that Windows Recall did not capture sensitive fields when he visited payment pages for Oimoroni and Adafruit. This inconsistency suggests that while the feature may successfully filter out information from recognized commercial sites, it may falter in other contexts, as demonstrated in his specific scenario.
It is crucial to note that Windows Recall is currently in beta and accessible only through Microsoft’s Windows 11 preview program. As such, users can expect some bugs and issues, and Microsoft is actively seeking feedback to enhance the product before its official launch. Our Senior Editor, Zac Bowden, has been testing Windows Recall since its preview release and reported that he could not replicate the issue of capturing financial information, even when typing it into Notepad. This discrepancy indicates that the problem may be tied to the current beta status of the feature, and Microsoft is hopeful that these issues will be resolved prior to a wider rollout.
When approached for comment regarding Plitch’s findings, Microsoft directed inquiries to a blog post that outlines how Windows Recall is designed to filter and censor sensitive financial information. The company acknowledged the potential for scenarios where the feature may not accurately filter out sensitive data during the preview phase, stating, “We’ll continue to improve this functionality, and if you find sensitive information that should be filtered out, for your context, language, or geography, please let us know through Feedback Hub.”
