Windows 11 Feature Flags Still Leave ViVeTool in Charge

Microsoft’s Feature flags page is live in Windows 11 Experimental builds, and it still refuses to expose the hidden IDs ViVeTool was built to flip. The Settings screen arrived with the April 10, 2026 Insider overhaul as the official answer to years of command-line workarounds, then spent the summer listing only features Microsoft had already described in program notes.

That is a real improvement for testers who just want the thing in the blog post. It is also a narrower switchboard than the unofficial tool it was supposed to retire, which is why the GitHub zip is still on desktops in September 2026.

Microsoft’s Flags Page Only Lists What It Already Announced

The page lives at Settings, Windows Update, Windows Insider Program, Feature flags, and it is documented for the Experimental channel. Each row is a named experiment with a short description and a control that can sit on No Override, Disabled, or Enabled. Apply the change, restart, and the build behaves as if that flag had been part of the flight.

Microsoft’s own rule is the catch people skip. The company said it would start with visible new features announced in WIP, and that bug fixes and system-level work may never show up there. Windows how-to specialist Mauro Huculak, who keeps a running catalog of the page, puts it more bluntly: the interface exposes advertised or officially testable experiences, and a lot of under-development code stays off it.

On his September 19, 2026 rundown of Experimental quality update 26340.9502, the live list was short and polite. These are the switches testers could actually see.

FLAGS ON EXPERIMENTAL BUILD 26340.9502

• Camera Roll Backup: New Settings Home and Accounts entry points for backing up phone photos and videos to OneDrive.
• Cross Device Resume: Opens a phone webpage on the PC in the default browser or installs the matching mobile web app.
• Drag and Drop bundle: Fixes drop-target alignment, drag previews, and AutoDest crashes.
• Emoji 17.0: Adds the new set, including distorted face, fight cloud, and hairy creature, in the Win +. panel.
• Start menu customization: Extra layout, recommendation, and visibility controls for Start.
• Improved Context Menu: Faster right-click menu with more room to tailor what appears.
• Indexer File Explorer search: Uses the indexer when searching This PC.
• Magnifier contrast theme: High-contrast controls inside Magnifier that leave photo and video colors alone.
• Modernized AutoPlay: Updated dialog for drives, cameras, and other media devices.
• Refined Windows Search: Cleaner home, source labels for app, file, setting, or web, and more consistent previews.
• Short query file search: File results for two-character queries in File Explorer.

Huculak also logged 18 flags that had already left the page because those features were baked in, including alternate taskbar positions, a smaller taskbar, longer update pauses, and the new Insider settings experience itself. Once a flag graduates, you cannot turn that work back off from Settings. The official catalog shrinks as code ships, which is the opposite of a power-user lab that keeps every dormant ID in reach.

The Insider Overhaul That Ended the Beta Lottery

The flags page is one piece of a larger repair job. For years Insiders installed a build they had just read about and then sat in a holdout group while Controlled Feature Rollout, or CFR, drip-fed the actual feature. Microsoft called that gap the single biggest frustration it heard, and on April 10, 2026 it cut the channel map down to Experimental and Beta, with Release Preview kept as an advanced option.

THE APRIL 2026 INSIDER SHIFT

1. March 20, 2026: Windows lead Pavan Davuluri publishes a quality pledge that includes a simpler, more transparent Insider Program.
2. April 3, 2026: A Feature flags Settings page is spotted hidden in build 26300.8155, still off by default.
3. April 10, 2026: Microsoft announces Experimental in place of Dev and Canary, plus ending gradual feature rollouts in Beta.
4. April 15, 2026: Enthusiasts treat the still-hidden page as the long-requested chrome://flags equivalent for Windows.
5. August 21, 2026: Experimental build 26340.9233 ships a fix after the flags list goes empty even though flags are present.

Beta is now the boring, useful channel. Microsoft Learn says feature rollout there does not use CFR, so an announced Beta feature is on the device after the update, with only small in-feature variants still in play. Experimental is where new work shows up first, and many of those features still roll through CFR, starting with a subset of Insiders. If a feature was announced and it is missing, Learn points testers to Feature flags on Experimental builds rather than to a third-party binary.

Advanced options let Insiders pick a Windows core such as 25H2/26H2 or 26H1, and Experimental also carries a Future Platforms track that is not tied to a retail version. Moving between Experimental, Beta, and Release Preview on the same core can use an in-place upgrade. Future Platforms still needs a clean install to leave. None of that replaces a tool that can address an ID Microsoft never put on a Settings row.

ViVeTool Still Flips the IDs Microsoft Will Not Show

ViVeTool exists because Windows already stores experiments as numbered flags with states, and Microsoft never shipped a supported UI for them. Lucas publishes the project on GitHub as thebookisclosed, and the repo describes a C# library and console app that talks to the A/B feature experiment mechanism in Windows 10 and later. The binary does not inject new code. It changes the state of features that are already sitting in the build.

The latest packaged build is the ViVeTool v0.3.4 release, posted March 10, 2025, with a thank-you for 2 million downloads, Intel/AMD and Snapdragon Arm64 zips, and credits to Rafael Rivera and PhantomOfEarth for symbol scanning. The repo shows 7.8k stars and 375 forks. It needs Windows 10 build 18963 or newer. Typical use is an elevated terminal, vivetool /enable /id: followed by one or more numbers, then a restart. Disable and query commands reverse or inspect the same IDs. A feature can sit at Default (0), Disabled (1), or Enabled (2).

We will start by enabling Feature flags for visible new features announced in WIP. This means less visible changes announced in WIP, like bug fixes and system improvements, may not be present in Feature flags.

Windows Insider Blog, April 10, 2026

That sentence is why the GitHub project did not become a museum piece. PhantomOfEarth, the same account that hunts IDs and that first spotted the Settings page, still feeds the numeric pipeline the official catalog refuses to show. On August 18, 2026, Experimental build 26340.9212 carried a customizable File Explorer context menu that stayed hidden until someone flipped it with ViVeTool. On September 6, 2026, a walkthrough for KB5120998 still sent 24H2 PCs on build 26100.9278 and 25H2 PCs on build 26200.9278 through IDs such as 61161244 for a feature bundle, 59213768 for taskbar position, and 62353331 plus 62762248 for redesigned Search.

What the Two Switchboards Control

The Settings page is a labeled, restart-backed toggle list for announced Experimental features, including those still on a CFR ramp. ViVeTool is an unsupported client for the same feature store, aimed at any ID a given build contains, on Insider rings and on ordinary 24H2 and 25H2 PCs. One is a product. The other is a poke at the plumbing.

OFFICIAL FLAGS VERSUS VIVETOOL

Beta users who just wanted the changelog to match the desktop got most of what they asked for without opening either tool. Experimental users still hit a two-layer filter: CFR can hide an announced feature, and Feature flags can omit anything Microsoft does not want on a Settings row. Search updates in July 2026 were a clean example of the first layer working as designed. Testers on Experimental 26H2 were told to open Feature flags and turn the Search work on, which is exactly the job Microsoft assigned the page. The second layer is the one that keeps ViVeTool employed.

A Hidden Page That Later Went Blank

The first joke wrote itself. The Feature flags page shipped as a hidden feature, and on Beta build 26220.8148 the ID that turned it on was 60911173. Insiders who wanted Microsoft’s ViveTool replacement used ViVeTool to reach it. Marcus Ash, who leads design and research for Windows and Devices, saw the leak and wrote that testers were fast, and that more on WIP settings was coming the following week. The April 10 blog was that follow-up.

The second failure was less funny. In August 2026 the Experimental flags list rendered empty even though flags were available, which is a bad look for a page whose only job is to show the switches. Microsoft called it out in the Experimental notes for build 26340.9233, released August 21, 2026, as a fix for an issue that caused the Flags list to appear empty. The same flight went to Beta as 26220.9223 and to Experimental 26H1 as 28120.2760. The official Insider account posted the builds and the flags fix the same afternoon.

Hope your weekend is maximized! New WIP builds out today + fix for Experimental Feature flags: https://t.co/hQwhD3j7Lq
Beta: https://t.co/vYItwIH7M9
Experimental: https://t.co/ax5C4PwvBG
Experimental (26H1): https://t.co/Sc6fkdI26l pic.twitter.com/EfKCObdTR0

— Windows Insider Program (@windowsinsider) August 21, 2026

Replies under that post spent more time on AutoPlay chrome and the Future Platforms cadence than on celebrating a ViveTool funeral. The flags page had become plumbing, and plumbing that can go blank is plumbing people keep a backup for. A terminal command against a known ID does not depend on a Settings list populating.

Stable PCs Keep Using the Unofficial Tool

The Insider overhaul solved a program problem. It did not solve the quieter habit of flipping unfinished Windows on machines that are not in the program at all. Cumulative updates still land code in a disabled state, then turn it on later for some PCs. That is how a 24H2 or 25H2 box ends up with a new Start menu, a movable taskbar, or a Search refresh sitting inert until someone types an ID. Feature flags do not ship in that Settings path for ordinary retail devices. ViVeTool does, because the APIs are in the OS.

VIVETOOL IN SEPTEMBER 2026

• Downloads: The v0.3.4 notes thank users for 2 million downloads.
• Repo: 7.8k GitHub stars and 375 forks on thebookisclosed/ViVe.
• Floor: Windows 10 build 18963 or newer, covering current 24H2 and 25H2 PCs.
• Still in guides: KB5120998 IDs for taskbar position, Search, and a September 2026 feature bundle.

Huculak’s Experimental list still carries a leftover warning that some hidden work needs ViVeTool because not every experiment appears on the Feature flags page. That sentence is the whole story in one line. Microsoft built the GUI Insiders asked for, put descriptions on the rows, and tied adoption to a channel it finally defined in public. It also reserved the right to choose which flags exist as rows. The unofficial tool remains the way to address the rest, including the page itself when the page was still dark, and including retail builds that will never grow that Settings section.

People who want announced Experimental features should use Feature flags and send feedback on what is missing. People who want an ID Microsoft has not named should keep treating ViVeTool as unsupported, keep a restore point, and expect the flag to vanish or break. The Settings page made the first group less dependent on a zip file. It did not empty the second group’s download folder.

Frequently Asked Questions

Where is the Feature flags page in Windows 11?

On Experimental Insider PCs it is Settings, then Windows Update, then Windows Insider Program, then Feature flags, and some builds hide that last jump under Advanced Options after you confirm the Windows version. Microsoft Learn documents the page for the Experimental channel only, and it is meant to override CFR on features the company has already announced, not to browse every dormant ID in the build.

Does the Feature flags page appear on the Beta channel?

Microsoft did not build Feature flags as a Beta setting because Beta no longer uses Controlled Feature Rollout for whole features, so an announced Beta item is supposed to be on after you install the update. Small in-feature test variants can still differ from PC to PC, but the feature itself should be present, which is why Beta notes do not point testers at a flags list.

What can ViVeTool still do that Feature flags cannot?

ViVeTool can set Enabled, Disabled, or Default on a numeric feature ID that exists in the running build even when Microsoft never added that ID to the Settings catalog, and it runs on everyday 24H2 and 25H2 PCs as well as Insider rings. Feature flags only list experiments Microsoft chose to name, and those rows disappear after the work is integrated, so you cannot use the page to turn a shipped feature back off.

What is the oldest Windows version ViVeTool supports?

The GitHub project requires Windows 10 build 18963 or newer, which is the generation that first exposed the feature-control APIs ViVe talks to. Current packs still ship as a zip you extract and run from an administrator terminal, with separate Intel/AMD and Snapdragon Arm64 binaries in v0.3.4, and Microsoft does not support the tool even though it uses those built-in APIs.