Bloatynosy is a debloating tool for Windows 10 and 11, open-source under the MIT licence, a single portable file that does not sit in the background and does not change a single setting the moment you open it. The archive is a few hundred KB, the interface is written by hand, and it starts without a wait.

It does not change the system, it lays the switches out

A fresh Windows install always carries a few things you did not ask for and cannot easily find: a short-video app, a collaboration tool nobody uses, a service holding memory from the moment you log in. Bloatynosy is restrained about it. It does not decide for you. It lists those items and the settings behind them, you do the ticking, and you trigger the run.

The author puts it plainly in the project notes: open the app, see what Windows is doing, then decide what stays. That sentence explains why it does not look like the usual cleaner. There is no giant all-in-one button and no progress bar counting repaired items, only grouped entries, the current state of each, and a confirmation you have to press.

1.11 changes where the recipe comes from

Earlier versions baked the debloat list into the package, so the range of what you could touch was whatever shipped. Version 1.11 moves that catalogue into the code repository, where anyone can add a rule through a pull request, and the application pulls it while running. Losing the network does not leave a blank page: the copy carried inside the package takes over.

What grew along with it is the preinstalled-app group. Beyond the system components that have been listed for a long time, short-video and photo-social clients are now on the removable list too. Being listed is not the same as being worth deleting. Some components still hold other programs together, and the software that breaks afterwards is usually a third-party one.

The tool only lays the options out. Judging the consequences is still the user's job, and a restore point taken right after a clean install is more reliable than any promise of a safe delete.

The preview sorts itself by priority

The other change in 1.11 is on the preview page. Changes that will happen sit at the top, changes that will not sit below, and every block carries its count in the heading so nobody has to count rows. A skipped entry says why: already applied, protected by the system, no matching item found, or placed on your own ignore list. Conflicts move to the top in amber instead of hiding on row thirteen waiting to be discovered.

The interface details were reworked as well, spacing, alignment, colours and control states all went through a pass, and the package did not grow by a single byte. The whole program is hand-written WinForms with no embedded browser engine, which is how it keeps a few hundred KB and a start that feels immediate. The author mentions in the release notes that there has never been an Electron layer here, and that is rather the point.

The ignore list and profiles stay on the machine

Some entries you know at a glance should not be touched. Right-click and choose to ignore, and the entry drops into an ignore group at the bottom; the same menu brings it back. Items in that group cannot be ticked, even if a profile asks for them, and cannot be applied, while the scan itself still looks at everything, so the number on the home screen does not drift.

The ignore list lives in a local settings file and records group names and package identifiers rather than the text shown in the interface, so switching language does not wipe it. It also does not travel with a profile: hand someone your configuration and you do not hand over what you have blocked. What a profile does is carry decisions from one machine to the next, useful after a reinstall or when setting up office machines in a batch.

One option is optional: let an AI explain what a given change means. It is off by default, has to be switched on in the settings with your own API key, and works with several common providers and compatible endpoints. Even then it sends only the name and technical details of that single entry, never the scan results.

Three things to know before using it

It needs Windows 10 or 11 and relies on the .NET Framework 4.8 that ships with the system, which recent installations usually have. The program runs with the current user's rights, and if the system refuses a global setting the report names the item that failed to write instead of failing silently; start it as administrator only when something really needs it.

One more point is easy to miss: Bloatynosy is portable, and its data travels with the folder. Change the directory, change the machine, and the whole folder has to come along or the profile and the ignore list stay behind. As for whether deleting something breaks anything, there is no general answer, since two people on the same machine depend on different pieces. A restore point before you start is usually cheaper than patching up afterwards.

Version 1.11 is no leap in features. It changes how the recipe is maintained and how readable the preview is. For a tool of a few hundred KB, that restraint, handing the judgement back to the person using it, is exactly why it earns a place in the toolbox.