https://youtu.be/t30qIghy6gg
For months, we've endured the tortured warnings of the Recall Chicken Littles, but now that this feature is finally available, we can finally see for ourselves that there are, in fact, very real problems. No, not with security. If anything, Recall is locked down too well.
No, the problem with Recall is tied to the several small language models (SMLs) that it requires. Each of them is humongous. Recall won't work unless you have the latest version of each. And downloading and installing these SLMs is a chore, more manual process than seamless.
It here is, ironically or hypocritically--you decide--that I will admit that this criticism is perhaps as unfair as the nonsense we heard about Recall back in May and June. That is, my issue could maybe be obviated by the fact that I'm using Recall on a PC that is enrolled in the Windows Insider Dev channel, the only way to use Recall at the moment, and thus the experience I'm seeing may not represent the real-world experience that others will have once it is released in stable.
With that caveat in mind, here's what it's like to try and get Recall working.
About two weeks ago, Microsoft issued its first public preview of Recall as part of Windows 11 Dev Channel build 26120.2415. Having been told about this milestone earlier that week, I enrolled my Surface Laptop 7 into the Dev channel the night before that release, and then updated to the Recall-enabled build when the Microsoft announcement went live. (Unexpectedly, it appeared right on schedule.)
My initial write-up about this experience hints at the problem I'm still seeing. Onboarding Recall is awkward at best and convoluted at worst, and my initial attempt to run this app failed because I had to install "updates for Re call" via Windows Update before it would work. Recall didn't just install these updates, nor did it provide any way for me to do so myself. It just told me I needed to go to Windows Update.
Which I did. Checking for updates, I was given a single update, called Image Extraction, which downloaded slowly but installed very quickly. Nice, so I went back to Recall. Nope. You still need to install updates.
So I went back to Windows Update and clicked "Check for updates." Yep, there was another update, this one called Image Search. Same experience. Slow download, quick install. Whatever. Back to Recall. Nope. Come on.
So I went back to Windows Update. Clicked "Check for updates," again. And sure enough, there was a third update. This one was called Semantic Analysis. Fine. Same thing: Slow to download, quick to install. Surely, that was everything. Or not. I clicked "Check for updates," again, suspicious. This time it was clear. That was everything.
So I went back to Recall. And this time, it came up. It was done updating and I could actually use this reviled tool and see for myself what all the fuss was about.
Spoiler alert: I still don't know what all the fuss was about. I wi...
The post .
SOCIAL SHARE CARD GENERATOR