THE Ars Technica piece explains that the updated “TotalRecall Reloaded” tool can inject a DLL into AIXHost[.]exe and wait for a Recall authentication via Windows Hello, allowing it to intercept screenshots, OCR’d text, and other metadata after authentication. It notes that the problem lies not in Recall’s security around the database but in the sharing of data with the AIXHost[.]exe process, which apparently lacks the same protections.
Hagenah describes the vault as solid but warns that “The delivery truck is not,” highlighting the trust boundary involved. Microsoft said Hagenah’s discovery isn’t a bug and that the access patterns align with intended protections, with the company classifying it as not a vulnerability on 3 April 2026 after reporting the issue on 6 March 2026.
The story recalls that Recall data is locally encrypted and only viewable with Windows Hello, and that the reconstituted Recall became a better privacy feature, though the risk remains because anyone with access to the PC and a Windows Hello fallback PIN can reach the database. The article also notes a handful of tasks that can be performed without Windows Hello authentication, including grabbing the latest Recall screenshot or deleting the Recall database. According to the article, Recall remains a security and privacy risk despite improvements and the feature being turned off by default.