With less than a week to live, Recall happened one of the most controversial Windows features we’ve seen in recent memory, and it’s not even available to users yet. Unveiled last Monday as the star feature of the new features to come from the Copilot+ PC spec, it aims to be a sort of detailed digital record of everything that’s happened within the team over the past months.

Not even a day had passed since its introduction, when the first critical voices of the function began to be heard, with statements so emphatic This is the ultimate spyware and privacy nightmare. And just three days after its announcement (I repeat the announcement, not the launch), we already learned about the first opening of the investigation by the regulator, due to the more than understandable concerns that Recall raises when we talk about user privacy.

Still almost a week after it all startedI’m not sure if Microsoft miscalculated the impact this could have such a feature, or if they were aware but decided to move forward in spite of it, but in either case we are faced with what appears to be a mistake that lingers in the memory. Of course, the best part is that Recall is very limited in scope, as it can only be used on PCs that meet the Copilot+ PC specification, the main characteristic of which is to have an NPU reaching 40 TOP…or not? ?

Officially yes, it is a condition sine qua nonbut we didn’t have to wait long to verify that this is actually an unrealistic limitation because, as we read in WindowsLatest, The creators of ViveTool, Albacore, managed to use Recall on a machine without an NPU. He did not confirm whether 100% of the functions are functional, but he says about the main ones, as surprising as it may seem.

But he failed to do so on the first try and used a computer with an x86-64 processor, an architecture for which Microsoft has not yet released the AI ​​models that Recall uses. However, after identifying this problem, he decided to repeat the experiment this time with an old PC but based on ARM, where you can use the new function. So it seems like we’re talking about an “artificial” limitation, but I still think it won’t hurt too much given the response the feature has.