Windows 11 Dev Build Teases Removing Quick Settings Tiles in Energy Saver

  • Thread Author
Microsoft appears to be quietly testing a restoration of a much‑requested customization option in Windows 11: the ability to remove unwanted quick‑action tiles from the Quick Settings panel. The change was first observed in the Dev‑channel preview build 26300.7965 and has been attributed to work discovered in the Energy Saver quick‑setting module, with screenshots and commentary shared publicly by Windows UI sleuths.

Background: why Quick Settings matter — and why users asked for more control​

Quick Settings is the tray panel that gives fast access to connectivity and device toggles — Wi‑Fi, Bluetooth, Airplane mode, audio controls, battery/energy options and accessibility shortcuts. For power users and casual users alike, Quick Settings is a primary control surface for everyday system actions, replacing the older Action Center model in previous Windows versions.
Microsoft has iterated on Quick Settings since Windows 11’s debut. In particular, the Energy Saver toggle (which replaced or extended the older Battery Saver paradigm) is now a first‑class element in Quick Settings on recent Windows builds. The Energy Saver feature itself and its integration into Quick Settings have been formalized in Microsoft’s documentation and design guidelines.
Customization of Quick Settings has been inconsistent over several releases. At times Microsoft provided a simple edit mode where users could add, remove and rearrange tiles; at other times the UI shifted toward a scrollable list where removal controls were not as obvious or readily available. That inconsistency generated repeated user feedback asking for a reliable, on‑panel way to remove tiles rather than merely reorder them.

What was discovered in build 26300.7965​

On March 6, 2026 Microsoft released Windows 11 Insider Preview Build 26300.7965 to the Dev Channel, an official update that includes a number of experimental and in‑flight changes intended for internal validation and feedback. The presence of a change does not guarantee it will ship to the broader user base; feature flags and hidden UI paths are commonly used during development.
Independent Windows UI researchers and X (formerly Twitter) users monitoring the build found a hidden update inside the Energy Saver quick‑setting subpage indicating backend support for removing quick actions directly from the Quick Settings panel. The reports and screenshots show a context menu pattern (right‑click or press‑and‑hold) and an unpin/remove affordance associated with individual quick actions — behavior that would let users prune tiles they never use. Importantly, the discovery was of a backend capability and the removal control is not yet fully enabled or functional for typical Insiders in the Dev build.
Key, verifiable points from the discovery:
  • The build in which the change was found is Dev channel build 26300.7965, which Microsoft published as an Insider preview.
  • The new UX element appears to be located in the Energy Saver subpage within Quick Settings, and it shows an unpin/remove affordance for quick actions. The functionality is present in the code but not activated for general use in the current preview.

Why the Energy Saver toggle is important to this discovery​

The Energy Saver module itself is a relatively recent consolidation of battery and power controls in Windows 11. Microsoft’s documentation notes that the Energy Saver experience replaces or extends the older Battery Saver functionality in newer Windows 11 branches, and the control is intended to make power management more discoverable in Quick Settings and in Settings > System > Power & battery. Because Microsoft has already grouped multiple power‑related controls under Energy Saver, the module is a natural place to prototype adjacent UI behavior — including contextual menus and per‑tile controls.
The finding in build 26300.7965 is therefore twofold: Microsoft is experimenting with deeper organization inside the Energy Saver subpage (for example, grouping theme toggles, power modes and eco brightness), and it appears to be reintroducing an edit/unpin mechanism on the Quick Settings surface itself. That combination — a richer subpage plus direct tile management — is what has excited many users and observers.

How this differs from earlier Quick Settings behavior​

Historically, Quick Settings offered an edit mode where users could add and remove tiles via an Edit or pencil icon. Over subsequent iterations the panel sometimes shifted to a design that prioritized showing more toggles in a scrollable list; in those designs the direct remove affordance could be harder to reach or absent, prompting complaints that users could only reorder but not remove certain items. The discovery in the Dev build suggests Microsoft intends to bring back a straightforward removal mechanism that is accessible directly from the panel — a behavior more akin to the original, more customizable Quick Settings experience.
This is not the first time Microsoft has allowed hidden or gated Quick Settings behaviors to be visible in preview builds: previous features such as a new Volume Mixer, shared audio controls, and even color‑coded battery indicators have been discovered by UI sleuths in early builds and later shipped in altered forms, or subjected to further tweaks before roll‑out. The pattern indicates Microsoft uses the Dev channel to exercise multiple UI permutations before committing to a final design for public releases.

What this change means for users — practical benefits​

If Microsoft completes this work and ships a remove‑tiles affordance to general Windows 11 users, the practical upsides include:
  • Cleaner Quick Settings: Users can remove seldom‑used or OEM‑installed toggles and keep the panel focused on personally relevant actions.
  • Faster access to essentials: With fewer tiles occupying visual space, the most important toggles will be easier to find and actuate.
  • Reduced cognitive load: Less clutter can mean fewer mistakes and quicker decision making when working on the desktop or when using touch on tablets and convertibles.
  • Improved accessibility: Allowing users to curate the panel may help those who rely on screen readers or who prefer larger targets by removing distractions.
These are real usability wins for personal systems and for users who want a minimal, tailored control surface.

What businesses and IT administrators should watch for​

The reintroduction of per‑tile removal has implications beyond consumer convenience:
  • Group Policy and management controls: Enterprises often lock down system UI elements to conform with corporate policy. Microsoft’s enterprise management features can disable or reconfigure parts of the user interface. Administrators should verify whether new Quick Settings edit functions are controllable via Group Policy, Intune, or other configuration channels before rolling preview builds to end users. Microsoft has introduced policies for managing energy settings in the past; this control plane will likely extend to new Quick Settings options.
  • Support and training: If organizations permit personalization of Quick Settings, help desks may see new support questions (for example, users accidentally removing a necessary tile and needing assistance to add it back). IT departments should prepare updated guidance for user help resources.
  • Security posture: While tile removal itself is low risk, administrators should consider whether sensitive toggles (for example, remote access, diagnostic telemetry controls, or device management switches) should be exposed to end users for removal. Locking essential management tiles prevents accidental configuration changes on managed endpoints.

Risks and limitations: what this early discovery does not prove​

While the screenshots and preview reports are promising, there are clear limits and risks to assume the feature will ship unchanged:
  • The functionality observed in build 26300.7965 is hidden behind feature flags and is not enabled for general use in the Dev build — meaning Microsoft could change, delay, or scrap the feature based on testing and feedback. Early code presence is a good indicator of intent, not a guarantee of release.
  • The scope of tile removal is not yet documented. It’s unclear whether Microsoft intends to allow removal of all tiles, or only for certain classes of quick actions. Some tiles may be tied to underlying system services where removal could create confusion (for example, connectivity indicators that are necessary for troubleshooting). Until Microsoft provides official release notes or documentation, the exact tile‑level policy remains speculative.
  • Accessibility and discoverability must be handled carefully. If removal is controlled by a context menu or press‑and‑hold gesture, some users may have difficulty discovering the control; Microsoft will need to ensure the behavior is accessible to keyboard, assistive technologies, and touch users.
Because of those unknowns, any reporting that the feature will definitely behave a certain way for all users should be treated cautiously. Multiple outlets have reported the hidden change and attributed the discovery to the X user PhantomOfEarth, but the original social post and screenshots are being amplified by secondary reporting — the canonical product behavior is still controlled by Microsoft’s final shipping decisions.

How Microsoft typically rolls out UI experiments — a quick primer​

Understanding Microsoft’s release model helps set expectations for when and how this change might reach stable Windows 11 users:
  • Dev Channel: Early experiments land here first. Build numbers in this channel (such as 26300.7965) represent active development and are not guaranteed to ship outside Insiders. These builds often carry feature flags and experimental toggles.
  • Beta / Release Preview: Features that survive Dev testing and are refined may migrate to Beta and then Release Preview. Microsoft uses these channels to broaden testing across more hardware configurations.
  • Public Feature Update / Cumulative Update: After validation, Microsoft can include the feature in a cumulative update, a servicing release, or a scheduled feature update. The company may also perform a staged rollout server side or use phased feature enablement.
Because the capability observed is hidden, it will likely follow the same path: internal testing, iterative changes, then gradual exposure to Insiders and, if all goes well, a broader rollout.

Reaction from the community: why this matters beyond a small UI tweak​

The Quick Settings panel sits at the intersection of usability, discoverability and personalization. A simple removal affordance resonates with many because it’s one of the few lightweight ways users can make Windows feel like their machine without installing third‑party tools.
Community reactions to early sightings have been broadly positive: enthusiasts welcome the return of direct removal controls, and many have pointed to the persistent clutter problem on OEM systems and on devices where power users want only a handful of frequently used toggles. Several respected Windows observers who track hidden builds have flagged the change and shared screenshots, increasing confidence that Microsoft is at least seriously testing the capability.
At the same time, power users have reminded observers that previous hidden discoveries did not always ship, and even when they did, features were sometimes reworked. That pragmatic view has tempered exuberance with a recommendation to wait for official Microsoft documentation.

Recommendations for users and Insiders​

If you’re interested in this capability and you participate in the Windows Insider Program, here are sensible steps and considerations:
  • If you want to monitor progress, keep your Insider channel set to Dev (or Beta where the feature appears next) and watch official Windows Insider release notes for feature flag changes. The official Dev build announcement for 26300.7965 is the authoritative confirmation that Microsoft shipped that preview build for testing.
  • Don’t expect hidden code presence to mean immediate availability. Treat screenshots and early posts as previews, not final product behavior. Plan to update support documentation only after Microsoft publishes public guidance.
  • If you depend on consistent UI for accessibility or enterprise workflows, delay adoption of early Dev builds on production devices until the feature permanently ships with management controls documented. Enterprises should test internal policies to ensure the new behavior can be governed where necessary.
  • If you’re an enthusiast who enjoys testing hidden features, follow trusted community reporters and use official feedback channels (Feedback Hub) to submit experiences and bugs rather than relying only on third‑party tools or registry hacks.

What Microsoft could do next (and what we’ll be watching for)​

To make the feature truly useful and stable, Microsoft should consider the following during the development process:
  • Clear discoverability: add explicit edit affordances (an Edit pencil, or a persistent three‑dot menu) alongside context menus so users of all abilities can remove and restore tiles without guesswork.
  • Restore/Reset options: a one‑click reset to factory Quick Settings would prevent users from accidentally locking themselves out of convenient toggles.
  • Management controls for IT: provide Group Policy/Intune settings that enable or disable user ability to remove specific system or management tiles.
  • Accessibility parity: ensure the remove/unpin action is keyboard reachable, labeled for screen readers, and exposed via UI Automation.
  • Telemetry opt‑in: if Microsoft leverages telemetry to understand which tiles users remove most often, make that data collection transparent and optional.
We will watch official Windows Insider release notes and Microsoft documentation for signals that these considerations are being addressed as the feature moves through preview channels.

Final analysis: small UI change, meaningful UX implications​

Reintroducing a remove option for Quick Settings tiles would be a modest technical change with outsized usability benefits. It aligns with longstanding user feedback asking for a configurable control surface that adapts to each person’s workflow. The presence of backend support in Dev build 26300.7965 is a strong sign that Microsoft is listening and experimenting with practical UX improvements.
However, readers should maintain realistic expectations. The observed capability is currently hidden and under test; the feature’s final behavior, scope, and rollout timeline are still under Microsoft’s control and subject to change. Until Microsoft markets or documents the functionality in a shipping release, the correct posture is cautious optimism: promising discovery, useful potential, but not yet a completed product.
Windows 11 users who value a streamlined Quick Settings experience should monitor the Insider channels, consider participating in previews on non‑critical devices, and prepare to provide feedback once Microsoft exposes the feature publicly. If the feature ships as observed, basic personalization will return to a control surface many of us use dozens of times per day — a subtle improvement that could make Windows feel that much more personal and efficient.
Source: thewincentral.com Windows 11 May Bring Back Option to Remove Quick Settings Toggles
 
Click to expand...
Microsoft’s Dev‑channel preview build has quietly rekindled a small but persistent user demand: the ability to remove unwanted items from Windows 11’s Quick Settings panel. What arrived in Build 26300.7965 (KB5079385) is not yet a finished feature, but the hidden UI elements and code paths uncovered by UI sleuths point to a return of a customization control many users thought was lost when Windows 11 modernized the Control Center. This matters because Quick Settings are how millions of users interact with brightness, Wi‑Fi, sound, and battery features multiple times a day — and the design decisions here speak to Microsoft’s shifting balance between simplicity and granular control.

Background​

Since Windows 10, Microsoft offered users the ability to add, remove, and reorder quick action tiles in the notification/control center. Early versions of Windows 11, and particularly the rollout of 24H2, shifted to a more simplified, scrollable Quick Settings layout. That change centralized many toggles and made the full set of actions visible by default; you could rearrange controls, but you could not remove them entirely. The result was faster discoverability for Microsoft’s chosen features, but also frustration among users who wanted a leaner system tray tailored to their workflows.
On March 6, 2026, Microsoft published the Windows Insider announcement for Build 26300.7965 (KB5079385) to the Dev Channel. While the official notes emphasize fixes and broader features, public reporting and community sleuthing revealed hidden UI components in that build that point to two related experiments:
  • a mechanism to remove specific quick actions from the Quick Settings surface, and
  • a redesigned Energy Saver submenu inside Quick Settings that groups power‑related controls (including a Dark/Light mode toggle, Eco Brightness, Power Mode, and Screen Contrast controls) under a single expandable tile.
Multiple independent Windows‑focused outlets and several insiders who experiment with Dev‑channel builds confirmed these findings soon after the build’s release. Their testing indicates the new UI is partly functional on battery‑equipped devices but that the remove/unpin functionality itself is not yet complete, suggesting Microsoft is iterating on both the UX and underlying logic before a wider rollout.

What exactly surfaced in Build 26300.7965?​

Hidden UI artifacts and the Energy Saver submenu​

In the Dev build, Quick Settings shows an Energy Saver tile with a small chevron — a clear indication that Microsoft intends for that item to expand into a submenu rather than be a single on/off toggle. Inside that submenu, testers found shortcuts for:
  • Dark Mode (a quick switch between Dark and Light themes),
  • Eco Brightness (a variant of adaptive brightness tuned for energy savings),
  • Power Mode (switching between power profiles), and
  • Screen Contrast (controls intended to tune display contrast to save power on some panels).
This is a deliberate reorganization. Microsoft has been consolidating power and display optimizations under the Energy Saver concept since 24H2, and putting those controls behind an expandable submenu inside Quick Settings reduces clutter while exposing richer, battery‑focused choices when needed.

The reappearance of an edit/unpin mechanism​

More intriguing is the presence of code strings and hidden UI affordances that suggest an edit mode — one which would allow users to remove individual quick actions from the visible Quick Settings list. Where Windows 11 had previously gone with an always‑exposed, scrollable list, these artifacts imply Microsoft is testing a hybrid: quick access remains, but power users could hide toggles they never use. Early screenshots and community builds show visual cues for edit mode (icons dimming, remove glyphs), though the interactive behaviors to commit changes are not fully implemented in this build.

Other Quick Settings improvements in preview​

Alongside these discoveries, Microsoft continues to roll out and iterate on closely related Quick Settings features that started appearing across Insider channels earlier:
  • Shared Audio and per‑device volume sliders — a Quick Settings control to share audio streams to multiple Bluetooth LE Audio receivers with independent listener volumes;
  • A taskbar indicator for shared audio so users can see when output is being shared;
  • Ongoing fixes to Quick Settings reliability and synchronization between hardware state and UI.
These features have been previewed progressively across multiple Insider builds and channels; the Dev build in question appears to be the latest testing ground for their integration with other Quick Settings reorganizations.

Why this matters: Practical user impact​

Quick Settings live at the intersection of convenience, discoverability, and clutter. Restoring the option to remove toggles affects multiple user groups in tangible ways.
  • For power users, the ability to cull unused toggles reduces visual noise and lets them keep only the controls they touch frequently. That improves speed of access and reduces misclicks.
  • For desktop users, removing battery‑focused tiles like Energy Saver or Eco Brightness (often irrelevant on a plugged desktop) will prevent an unnecessary overflow of mobile‑oriented controls.
  • For laptop users, consolidating multiple battery‑saving actions under Energy Saver — while still allowing removal of unrelated tiles — creates a cleaner, more contextual control surface.
  • For help desks and IT administrators, changes to Quick Settings can simplify support scripts but also introduce variability for end users who rely on visual cues during troubleshooting.
If Microsoft ships a robust edit/unpin UX, Quick Settings will regain a well‑liked customization affordance that Windows 11’s earlier simplification removed. But the path forward contains tradeoffs and risks (see Risks & unknowns below).

Critical analysis — strengths, design logic, and likely engineering constraints​

Strengths and sensible design choices​

  • Contextual grouping reduces cognitive load. Placing Dark Mode, Eco Brightness, Power Mode, and Screen Contrast under Energy Saver is a sensible mental model. All four relate to power/visual tradeoffs; grouping them reduces the number of first‑level tiles while keeping deep control within two clicks. This balances discoverability and simplicity.
  • Bringing back removal restores agency. Many users complained after 24H2 that they were forced to live with toggles they never used. Restoring an edit mode respects the long‑held Windows tradition of user choice and customization.
  • Consistency with modern modular design. The expandable submenu pattern aligns with modern mobile‑inspired control centers and offers a consistent approach for quick access vs. deeper configuration.
  • Integration with existing Energy Saver semantics. Microsoft rebranded and extended Battery Saver into Energy Saver in earlier releases; exposing those controls in Quick Settings is consistent with ongoing energy management efforts on Windows.

Engineering and UX constraints likely guiding Microsoft​

  • State persistence and synchronization. Quick Settings reflect both user preferences and hardware state (e.g., Bluetooth on/off). An edit/unpin mode must persist per user and sync across devices in sensible ways, or risk confusing users when a toggle reappears after updates or on another machine.
  • Policy boundaries for enterprise-managed devices. Enterprises may use group policies or MDM controls to enforce certain settings. The edit/unpin mechanism must honor those policies or provide clear admin controls so IT can ensure required toggles remain visible to users.
  • Accessibility and discoverability tradeoffs. Removing controls makes the UI cleaner for some, but hides options other users might expect to find. Microsoft needs to ensure the edit interface is discoverable to users who want to customize, and that assistive technologies can access both the edit affordances and the removed items if necessary.
  • Testing permutations across hardware classes. Quick Settings must behave consistently across laptops, desktops, tablets, and Copilot+ OEM devices. The Energy Saver submenu’s features like Eco Brightness or Screen Contrast are more relevant to devices with power management and certain display hardware; Microsoft must guard against showing irrelevant options on unsupported machines.

Risks, limitations, and unanswered questions​

No preview feature is a promise, and several important unknowns remain.
  • Will edit actions persist across major updates? Historically, Windows updates sometimes reset UI customizations. If Microsoft does not store Quick Settings layouts robustly (and sync them across the user’s Microsoft account), users could lose their curated layout after feature updates.
  • Enterprise management friction. If an admin requires visibility of specific toggles (for security or compliance), could end users still hide them? Conversely, will admins be able to pin enforced items? There’s an operational requirement here that Microsoft must address.
  • Discoverability vs. hidden features. Hiding Dark/Light mode behind Energy Saver is logical for battery focus, but Dark Mode is a general accessibility and personalization setting. Users expect to find theme switching in the personalization surface and perhaps not buried behind battery controls. This introduces a potential discoverability problem for users who want to switch themes independent of power considerations.
  • Incomplete implementation and potential rollbacks. The removal controls in the Dev build are incomplete. Microsoft may iterate and change the exact model or even abandon it. Insiders should therefore treat current behavior as experimental.
  • Device eligibility and feature gating. Several Quick Settings features (notably Shared Audio and per‑device volume) are gated by hardware compatibility (Bluetooth LE Audio support) and, in some cases, Copilot+ hardware requirements or OEM driver support. The editing features may also be staged so not all Insiders will see them immediately.
  • Security and privacy surface. Any new UI control that surfaces device or audio routing could potentially be misused if not thoughtfully permissioned. For example, the Shared Audio indicator is a helpful privacy cue, but users need clarity about what sharing entails and which user contexts trigger it.

What this means for different audiences​

Home users and enthusiasts​

If you interact with Quick Settings multiple times per day, a return of removal controls is welcome. Expect a small learning curve as Microsoft experiments with the Energy Saver grouping. Power users will appreciate the ability to sculpt a minimal tray, but you should:
  • Test changes inside the Dev or Beta Insider channels only if you are comfortable with instability;
  • Keep in mind some options may be hidden until Microsoft finishes back‑end logic;
  • Back up settings or document your preferred Quick Settings layout if you rely on it heavily.

IT administrators and enterprise teams​

This change has policy and support implications. Administrators should:
  • Watch for new MDM and GPO options that govern Quick Settings visibility and editability;
  • Prepare documentation and support steps in case some users hide controls that help with troubleshooting (Wi‑Fi, Bluetooth toggles, etc.);
  • Test the feature in a controlled pilot before broad deployment to surface unexpected behavior on corporate hardware and drivers.

OEMs and driver teams​

OEM partners must ensure driver and firmware support for features like Eco Brightness and Shared Audio. OEMs should:
  • Validate display and brightness APIs that Energy Saver’s subfeatures rely on;
  • Update Bluetooth stack/LE Audio support to fully leverage per‑device sliders and Shared Audio;
  • Communicate with Microsoft and enterprise customers about compatibility windows.

Accessibility community​

Any UI reorganization must be accessible. Microsoft needs to:
  • Ensure edit/unpin interactions are reachable via keyboard and screen readers;
  • Provide clear announcements when items are removed or restored;
  • Release updated guidance and UI templates for assistive tech vendors.

How Microsoft should get this right​

If Microsoft intends to ship Quick Settings editability beyond Insider experiments, a few practical recommendations would make rollout cleaner and reduce friction:
  • Make edit mode discoverable but unobtrusive. A small “Edit” icon or contextual menu entry with a short tutorial the first time a user opens Quick Settings would help users learn how to customize.
  • Respect policies and provide admin controls. Offer clear MDM/GPO settings to enforce required tiles, and provide companies the ability to pin essential items.
  • Persist and sync user layouts. Save Quick Settings layouts to the user’s account so a curated setup follows them between devices. Provide an import/export option for power users.
  • Surface relevance metadata. Only show Energy Saver’s subcontrols on devices where they’re meaningful; hide them on desktop systems or clearly mark them as unavailable.
  • Offer a fallback discovery path. If Microsoft buries common items (like Dark Mode) under Energy Saver, also provide a dedicated Personalization Quick Setting or a setting link that surfaces theme controls where users expect them.
  • Document accessibility semantics. Publish ARIA/automation guidance for assistive tech partners and testers so edit/unpin actions work across the accessibility ecosystem.
  • Beta the experience with telemetry and opt‑outs. Use Insider telemetry to understand how often users remove items, which tiles are frequently hidden, and whether hiding causes support confusion. Offer a simple opt‑out for telemetry related to UI customization.

How to test or follow progress (for Insiders and power users)​

If you’re curious and comfortable with pre‑release software, you can observe how the feature evolves through the Insider Program. Important practical notes:
  • Join the Windows Insider Program and set your device to the Dev or Beta channel as appropriate. Dev is for early testing; Beta is more stable but might have delayed features. Microsoft’s announcement for Build 26300.7965 specifies Dev distribution on March 6, 2026.
  • Update to the relevant preview build (for example, Build 26300.7965 under KB5079385 in the Dev Channel) and check Quick Settings. Look for the Energy Saver tile chevron and any edit affordances.
  • Test on a battery‑equipped laptop to see Energy Saver subcontrols; desktops may not display the full submenu.
  • Report bugs through the Feedback Hub if you notice missing behavior (for example, if the UI shows remove icons but they don’t commit changes).
  • Remember: Dev builds are experimental. Back up important data and avoid installing them on production machines.

Bigger picture: What this signals about Microsoft’s UX trajectory​

This preview behavior is part of a broader pattern that has emerged over the last year: Microsoft iterates quickly on Windows 11’s interface by trialing mobile‑inspired control center patterns and then responding to user feedback with measured reintroductions of power features.
  • The company is balancing the push for a cleaner, more uniform UI with the longstanding Windows expectation of user control. Restoring editability would be a concession to users who value customization over simplified default experiences.
  • Microsoft appears to be consolidating related functionality (power, display, audio) into contextual submenus to reduce first‑level surface area while preserving deep controls. This aligns with modern UI design but raises discoverability and accessibility tradeoffs that the company must manage.
  • Hardware gating remains critical. Several features (Shared Audio, Eco Brightness, etc.) require hardware/driver support, meaning the experience will vary by OEM and by device class.

Final assessment and takeaways​

The hidden Quick Settings edit hints in Build 26300.7965 are welcome news for users who lost the ability to remove quick actions when Windows 11 simplified the Control Center. Consolidating power controls inside an Energy Saver submenu while reintroducing an edit/unpin flow is a pragmatic compromise: it keeps Quick Settings lean for casual users while restoring control for those who want it.
However, this is still an experiment. The feature is incomplete in the Dev build and may change substantially before any broad release. Key concerns — persistence across updates, enterprise policy controls, accessibility, and hardware gating — must be addressed to avoid frustrating users or breaking administrative expectations.
For now, the prudent approach for users is to watch the Insider channels, test on non‑production hardware if interested, and prepare for a future Windows 11 update that aims to offer more nuanced personalization of the system tray. If Microsoft follows through with robust edit controls, clear admin options, and thoughtful accessibility support, Quick Settings will regain the balance between simplicity and the personalization Windows users have long valued.
Source: Trusted Reviews You’ll soon be able to remove unwanted options from Windows 11’s quick menu
 
You must log in or register to reply here.