907
Microsoft's 'Recall' feature can't be uninstalled after all
(mashable.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Sep 2024
907 points (99.2% liked)
Technology
59689 readers
2927 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Windows does have its own command-line package manager. I don't know if it can remove Recall, but last I checked it could remove Cortana. It would just get reinstalled soon after, but that could be prevented with some file-naming trickery. If you give a file the same name as the folder used to have and make it read-only, it couldn't remake the folder and wouldn't reinstall.
I wouldn't be surprised if you can still do that now.
Which one do you mean? Winget which is their newest attempt at creating a package manager that isn't an absolute piece of garbage, or their crappy CLI for managing MSIX/APPX modules? Because I remember using the latter to try and remove Cortana back when I first tried Windows 10. Fast forward, I removed all the garbage I didn't need, applied a Windows update, restarted my PC and it was all reinstalled. I wiped that SSD the same day and went back to Linux. This was the last time I used Windows on any of my personal devices.
I was talking about Appx. I haven't used Windows in a while, but that was how I got rid of Cortana. The key part was the read-only file named after the folder that couldn't be replaced.
I'd say you didn't actually remove the garbage. "Settings, apps, uninstall" doesn't really get rid of it, the deployment package is still hanging around.
You need to use powershell to de-deploy those packages.
It's a bit like the difference between "apt remove" and "apt purge"
Oh I did, I spent hours looking up different pwsh commands and package names to clean it all up