Winslopr is a lightweight Windows utility designed to help users remove preinstalled apps, disable certain AI-related features, and adjust system settings aimed at reducing background services and telemetry.
It provides a simple interface to select which components or features to modify, allowing users to streamline their Windows installation and customize the operating system to better suit their preferences.
Is Winslopr anti-Windows?
No. Windows itself is fine. The unnecessary stuff layered on top of it isn't. Winslopr targets slop, not Windows.
Is there a help file / quick start guide?
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
Can Winslopr break my system?
Any system tool can if misused. That's why Winslopr shows exactly what it will change, never runs anything automatically and allows changes to be reviewed and reverted.
What is Winslopr written in?
Initially in C, then it was forked from CrapFixer and ended up in C# and continues. No glossy modern UI stack. No WinUI. No Mica. No overdesigned "modern Windows app" look. No "look how fancy we are" . Just tools.
Features
- Removes Windows bloatware (preinstalled apps like Xbox, Clipchamp, etc.)
- Disables AI features like Copilot or Recall
- Reduces telemetry and ads inside Windows
- Lets you select exactly what to remove instead of running aggressive scripts
- Portable tool - you just download and run it (no installation)
What's New
Winslopr was my first real experiment with WinUI 3. Since then I've grown a lot more confident with the framework, and that shows in how FluentTweaker is built.
So I've decided to retire Winslopr and move forward with FluentTweaker as its successor, a cleaner, more capable app built as part of the Fluent ecosystem alongside FluentCleaner.
Over the years I've released a number of Windows 10/11 optimizers and debloaters as C# WinForms / .NET apps. The best ideas and features from those tools are gradually making their way into FluentTweaker. Now that I've grown comfortable with WinUI 3, it feels like the right home for all of it, one modern, native app instead of a scattered collection of old projects.
The timing feels right too. Microsoft appears to be moving away from web app slop and refocusing on WinUI and native app development, which gives me a lot more confidence that I'm building on the right foundation and a lot less worry about waking up one morning to find the framework abandoned
Maintaining two apps that do the same thing doesn't make sense. FluentTweaker does everything Winslopr did and much more and it fits cleanly into the same workflow if you already use FluentCleaner.
