Winslopr
Windows Slop Remover
Install / Use
/learn @builtbybel/WinsloprREADME
Note: "winslop" might refer to Windows 11 in some corners of the internet.
Winslopr is the tool designed to clean it up.
Winslopr
Windows slop remover
"We need to get beyond the arguments of slop vs sophistication…"
— Satya Nadella
"Slop" = stuff that ships by default, wastes resources, and takes control away, while doing basically nothing for you.
This started as a joke.
Then Microsoft said "slop vs sophistication" out loud and it stopped being one.
📋 What annoys you most about Windows 11?
59 community-sourced annoyances. Filterable. With fixes.
See what Winslopr handles and what needs extra tools.
winslopr
Windows
└── slop
├── telemetry
├── assistants
├── ads
├── suggestions
└── background junk
↓
removed by winslop
↓
thanks
Satya
remove the slop. Nothing fancy. Just tools.
FAQ
<sub>Click to expand. No assistant required.</sub>
<details> <summary><strong>Is Winslop anti-Windows?</strong></summary>No.
Windows itself is fine.
The unnecessary stuff layered on top of it isn’t.
Winslop targets slop, not Windows.
</details> <details> <summary><strong>Is there a help file / quick start guide?</strong></summary>Yes.
There's a small, lightweight entry guide to get you going:
- Quick Start / Help: https://github.com/builtbybel/Winslop/blob/main/docs/Help.md
Also no.
Winslop doesn’t care whether something is AI, scripted, cloud-based or hand-written.
If it’s forced, opaque, or unnecessary, its slop.
If it’s optional, transparent and useful, it’s fine.
</details> <details> <summary><strong>Does Winslop use AI?</strong></summary>No.
There is no model, no prompt, no inference step.
Everything is deterministic and based on explicit user choices.
No.
Winslop does not upload logs, telemetry, system data or usage statistics.
All actions happen locally on your machine.
Any system tool can if misused.
That’s why Winslop:
- shows exactly what it will change
- never runs anything automatically
- allows changes to be reviewed and reverted
You stay in control.
</details> <details> <summary><strong>Why not just use Copilot / Settings / PowerShell?</strong></summary>You can.
Winslop exists for people who prefer:
- fewer layers
- less abstraction
- no opinions
- no assistants
Just tools.
</details> <details> <summary><strong>Is this related to CrapFixer?</strong></summary>Yes.
Winslop is a very small, focused fork of CrapFixer.
The goal was to remove complexity, reduce scope and make things easier to maintain.
Smaller codebase.
Clearer intent.
Less slop.
Because Microsoft said “slop vs sophistication” out loud.
And because Windows isn't bad.
The slop is.
Winslop is anti-slop by design.
That’s why the UI is intentionally small, plain and functional.
No glossy visuals.
No animations.
No AI-generated fluff.
Slop comes in many forms:
- AI slop > mass-produced, soulless output
- Feature slop > unnecessary features that make UX worse
- UX / Design slop > bloated, unclear interfaces
- Corporate slop > buzzwords, filler and dark patterns
Winslop does the opposite: It removes more than it adds.
</details> <details> <summary><strong>Confession: I like Windows, but...</strong></summary>I just hate what Windows 11 keeps trying to become.
So I built the “stop doing that” button again.
Consider this stress relief with a UI.
Not really.
Its a constructed name
Winslopr is a made-up tool name, somewhere between cleaner, remover, and something that just sounds like it belongs in a Windows utility folder.
"Sloper" isnt a real word in this context.
But Winslopr still reads like one: the thing that removes the slop
So no, the word didn’t exist. Now it does
</details> <details> <summary><strong>What is Winslop written in?</strong></summary>C# with WinUI 3. Started as a fork of CrapFixer, rebuilt from scratch to be smaller and more focused.
</details>