Two downloads, one app
Windows 11 is modern. Windows 11 ships WinForms controls that were drawn when Windows 7 was modern. .NET 11 finally repaints them, rounded buttons, a real light mode, colours that come from the system instead of from a constant someone yped in 2009. The catch: .NET 11 is a runtime you have to install
So this release comes twice.
| Download | Needs | Use it when |
|---|---|---|
Bloatynosy-1.11.5-net48.zip
| nothing | You want to unzip and double-click on a machine you just met |
Bloatynosy-1.12.10-net11.0.zip
| .NET 11 Desktop Runtime | You want the new look and don't mind a one-time install |
Same features, same rules, same single file. The .NET 11 build is prettier, the .NET Framework build is the one you put on a USB stick. Pick your inconvenience
What the .NET 11 build looks like
- A light mode. Dark stays the default, this is still a tool for people who debloat Windows at midnight but Settings has a switch now. It takes effect after a restart
- Rounded buttons. The .NET 11 renderer draws them the way Windows 11 draws its own. No custom painting, no bitmaps, no theme engine
- Colours from the system. Surfaces, text and borders are system colours, so high contrast mode works because the system does the work, not because the app pretends to. The accent blue and the gold are still hand-picked, because Windows own dark blue reads at 2.6:1 and that is not good enough
Bloatynosy used to come with the tweaks it shipped with. This release opens the shelf to everyone else. Recipes are fetched from GitHub, previewed against your own PC, and applied only when you say so. Still WinForms. The framework survived another feature
Whats in this release
- Recipes from the community. The shelf is no longer whatever the installer happened to contain. Recipes live in the repo, anyone can submit one with a pull request, and the app fetches them at runtime. No internet, no empty page: the bundled copies step in. The preinstalled recipe now reaches TikTok, Instagram, Threads and Clipchamp as well
- Fork a recipe instead of arguing with it. Someone else's recipe is a starting point, not a verdict. Fork makes a full local copy: rename it, uncheck the entries you disagree with, save. It lands in the Recipes menu o Home, ready to preview, fork again or export as JSON for a pull request. The copy remembers where it came from, so credit survives the edit. Forking scans nothing and changes nothing in Windows, it is a copy, not a run
- A preview that sorts itself out. What will happen now stands above what will not, each block counting itself in a heading you can actually see. Skipped entries say why they were skipped: already applied, protected, not found, on your ignore list. Conflicts move to the top in amber instead of hiding as the thirteenth line
- A sharper interface that did not get heavier. Spacing, alignment, colour and states were gone over across the app, and the download did not grow by a single kilobyte. All of it is hand-drawn WinForms. In case you were about to ask where the Electron is: there never was any, and that is the point
Still portable. Still WinForms. Still nothing applied just because you opened the app