this post was submitted on 03 Sep 2024
907 points (99.2% liked)

Technology

59427 readers
4651 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
 

Who is surprised?

you are viewing a single comment's thread
view the rest of the comments
[–] Andromxda@lemmy.dbzer0.com 6 points 2 months ago (2 children)

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.

[–] scutiger@lemmy.world 8 points 2 months ago

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.

[–] r_deckard@lemmy.world -1 points 2 months ago (1 children)

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"

[–] Andromxda@lemmy.dbzer0.com 1 points 2 months ago

You need to use powershell to de-deploy those packages.

Oh I did, I spent hours looking up different pwsh commands and package names to clean it all up