In a surprising strategic reversal, Microsoft has announced the Windows 11 K2 update , internaly dubbed the "Un-Enshittification" release. After years of use...
What "un-enshittification" actually means for an operating system
"Enshittification" describes the slow decline of a product once it has a captive audience: features that once served the user start serving the vendor instead. In an operating system, that shows up as advertisements in the Start menu, prompts to sign into cloud services you never asked for, default apps that resist being changed, and settings that quietly reset after updates. The Windows 11 K2 update, internally dubbed the "Un-Enshittification" release, is framed as Microsoft walking that trend backward rather than adding more on top of it.
The important shift here is one of direction. Most major updates are additive—new panels, new suggestions, new integrations. A release defined by removal and restraint is unusual, because it treats the absence of friction as a feature. That reframes the operating system as a tool the user drives, rather than a surface the vendor monetizes.
The kinds of changes to look for
Without over-promising specifics, a reversal like this tends to target the parts of the system that most visibly work against the person using it. If you are evaluating what the update changed, these are the areas worth checking first:
- Promotional content and app suggestions embedded in the Start menu, lock screen, or search.
- Setup and update flows that push account sign-in, bundled services, or re-enabled telemetry.
- Default application handling—whether your chosen browser, PDF viewer, or media player actually sticks.
- Settings that previously reverted on their own, and controls that were buried several menus deep.
The value of a release like this is measured less by any single removed banner and more by whether your preferences hold over time. A genuinely un-enshittified system is one where a choice you make once stays made.
The tradeoffs Microsoft is accepting
Stripping out promotional surfaces and default nudges has a real cost to the vendor, which is why this kind of move is notable. Those surfaces exist because they drive sign-ups, service usage, and data collection. Rolling them back means giving up measurable engagement in exchange for goodwill and reduced user frustration—a bet that trust is worth more over the long run than the incremental clicks those prompts generated.
There is also a discoverability argument on the other side. Some of what gets labeled clutter—suggested apps, cloud backup prompts, first-run tours—was originally justified as helping newcomers find features. A restraint-focused release implicitly decides that experienced users being annoyed is a bigger problem than newcomers missing a suggestion, and that people can find features when they actually want them.
How to approach the update as a user
Treat the release as a reset point rather than a finished product. After installing, walk through your privacy, notification, and default-app settings and confirm they reflect what you want, since an update is exactly the moment stray defaults tend to creep back. Note which annoyances are genuinely gone versus merely toggled off, because a setting you can flip is weaker than a surface that no longer exists.
If the direction holds across future releases, the more meaningful signal isn't this one update—it's whether restraint becomes the baseline. Judge it by what stays absent months from now, not by the announcement.