this post was submitted on 11 Oct 2024
204 points (96.8% liked)

Technology

58599 readers
4071 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
204
Removing Windows Recall breaks File Explorer in latest 24H2 update - NotebookCheck.net News (www.notebookcheck.net)
submitted 11 hours ago* (last edited 11 hours ago) by [email protected] to c/[email protected]
36 comments fedilink hide all child comments
 

I wish I was a billion dollar company who gets away with stuff like this. Just generally break people's systems, add spyware, lie to users, treat them like shit.

All while making even more money and my stocks keep on going up, because AI, Ai, Ai...

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 4 points 5 hours ago (1 children)

I was under the impression you could still remove the feature without issue.

https://github.com/ChrisTitusTech/winutil/issues/2697#issuecomment-2403792309

[โ€“] [email protected] 5 points 4 hours ago

That's covered in the article you're commenting on.

Another user on GitHub also pointed out that Microsoft's own DISM can be used to disable the Recall service without the File Explorer consequences, although Titus points out that this behaviour seems inconsistent, as in his testing, the File Explorer still changed its appearance after a restart. Inconsistency aside, it's unlikely that any non-technical Windows user will even know what DISM is, never mind how to use it, and this reliance on a command-line utility to remove a controversial feature is indicative of MIcrosoft's goals.