Windows 11's Settings may be moving to the Microsoft Store

Windows 11's "Settings" might be moving—to the Microsoft Store. Have you ever done this: you know an option in Settings displays incorrectly, you want to report it, you wait half a month, and Microsoft replies, "We've noted it, it'll be handled in the next version." Then that version comes thirty days later, and it's still not fixed. The problem lies in the process itself. The Settings app's UI code is packaged and released together with the main system body, so fixing a display issue

💡 What You Will Learn

Windows 11's "Settings" might be moving—to the Microsoft Store. Have you ever done this: you know an option in Settings displays incorrectly, you want to report it, you wait half a month, and Microsof

Windows 11's "Settings" might be moving — to the Microsoft Store

Have you ever done something like this: you know a certain option in Settings is displaying incorrectly, you want to report it, you wait half a month, and Microsoft replies, "We've noted it, it'll be handled in the next version." Then that version comes thirty days later, and it's still not fixed.

The problem is the process itself. The Settings app's UI code is packaged and shipped together with the main system body. To fix a small display bug, you have to go through this entire pipeline: change the code, package and test, stuff it into a cumulative update, wait for Patch Tuesday, staged rollout, wait for you to install and reboot.

The whole trip takes three weeks to a month. This set of rules was established thirty years ago, when changing a single word in the Settings UI was genuinely worth convening a system update meeting.

Microsoft is now quietly trying a new path.

That "Settings" in the Store is a laboratory

A reporter from the overseas tech outlet Windows Latest dug up a test app in the Microsoft Store. Package name Microsoft.ProjectOdeon, version 1.0.9.0, publisher listed as Microsoft Corporation, tagged "Preview." The icon is the Settings app icon, and the interface almost verbatim copies the system's built-in Settings.

The reporter installed it on a Windows 11 Insider Preview virtual machine. After installing, they discovered one key thing: it doesn't replace the built-in Settings — the two can coexist.

And then came the part that makes you smile — on the same machine, the two sets of readings differ by over two hundred GB. Odeon says storage capacity is 125.9 GB, the built-in Settings says 381 GB; Odeon says the GPU is "Microsoft Basic Render Driver," the built-in Settings says "No dedicated video memory."

It can read real things — computer name, network status, pending updates are all correct. But the unfinished parts are also obvious: every toggle on the Recovery page has a line on top saying "Show values reported by Windows," and the service agreement links are grayed out and unclickable.

These details together say one thing: this isn't something meant to replace the Settings app — it's a laboratory.

What's really worth looking at is those nine workers

The interface isn't worth much — the pile of executables in the install directory is what's worth something.

The main program is called AccountExperiences.Settings.TestApp.exe — the test app doesn't even bother hiding its own identity. Beside it sit nine little tools all starting with the same name:

Once you list these names, the meaning is clear: the interface runs in a sandbox with restricted privileges, and only when it actually needs to touch the system does it call up the corresponding little tool to do the work. And renaming the PC, changing the time zone, uninstalling updates — for these, an ordinary Store app's permissions are nowhere near enough; it has to pop up an admin authorization prompt — the "Rename" button on the Settings page has "Requires administrator approval" written underneath it, which corresponds exactly to this mechanism.

Technically, this path already works. The interface and system operations are split into two layers, and elevation happens separately only when needed. This is precisely the core hurdle to moving Settings into a Store app.

Why Microsoft doesn't dare push it now

The technology works — the remaining concerns aren't technical.

In January of this year, the Microsoft Store had a server-side outage. The result was that Notepad, Paint, and Snipping Tool all refused to open, and even Windows Security Center wouldn't launch. Microsoft later acknowledged the problem and pushed a fix.

If Notepad crashes, worst case you wait two more minutes and switch to another editor.

If the Settings app crashes, you can't adjust brightness, change networks, clear cache, or install/uninstall things on your computer — and there's no fallback.

So what's deliberately preserved in this test is crucial: coexistence rather than replacement, carrying a Preview tag, requiring Developer Mode to install. Every layer is leaving a way out for a future official release.

The Store app update channel itself has long been a mature thing — Notepad, Paint, and Snipping Tool all ride on it, and a new version can be pushed in a few days. Microsoft knows better than anyone whether this mechanism works; it just doesn't dare let Settings into the water yet.

As for that line in the title about "being able to kill off Control Panel faster" — that needs a discount. Microsoft says it's moving Control Panel features into Settings, but it's been saying that for more than a year, and as of this August its own design lead's line was still "we're not at that stage yet." To manually install a printer today, you still have to open Control Panel.

The real signal this test sends isn't "Settings is moving" — it's "the update channel might be changing."

What the old interface gets stuck on longest is precisely the details

Microsoft has been doing the same thing all these years: renovating thirty years of legacy assets, piece by piece, into a modern interface. These jobs share a common pain point — the update cadence is locked to Windows' release cadence.

UI details — the least urgent kind of work — are precisely what gets stuck the longest.

Odeon proved one thing: this path is technically viable. It also exposed another: Microsoft is waiting for a safer moment, or a more reliable fallback, before it dares hand the front door over to the Store.

For ordinary users, there's nothing to do right now, and no replacement that requires Developer Mode to install is going to suddenly pop up in the Store.

But if you're in the habit of glancing at the changelog every week, this news is worth noting: that little UI blemish in Settings that's gone unfixed for so long might not have to wait until next month anymore.