Microsoft’s small-but-significant Windows 11 updates — versions
24H2 and
25H2 — added a raft of quality-of-life, accessibility, and AI-enhanced features in 2025, but many of those features are
staged and not visible on every PC by default; the community-favorite tool
ViVeTool can flip the local feature flags that make the functionality appear immediately on properly updated machines.
Background / Overview
Windows 11’s 24H2 and 25H2 releases are delivered mainly through Microsoft’s servicing pipeline as binary updates plus an enablement package that “flips the switch” for staged features. That means most of the code for 25H2 was already shipped via monthly cumulative updates; the enablement package and subsequent servicing updates simply change feature flags so features become visible. This model reduces download size and install time for up-to-date 24H2 systems and explains why two identical devices can show different feature sets at the same time. Microsoft’s own September 29, 2025 non-security update (KB5065789) documents many of these feature deployments — including new AI actions in File Explorer, the redesigned Advanced Settings page, repositionable on-screen hardware indicators, Passkeys improvements, and the “Click to Do” experience — and confirms that rollout is staged and gradual. Why that matters: if your PC is fully updated to the required servicing builds and you still do not see a given feature, it’s often because Microsoft is gating that feature by hardware capability, licensing (Copilot/Copilot+), tenant/region, or server-side experiments — not because the binaries are missing. For many of the visual and client-side features, the binaries are present locally and only the local feature flag is held off; that’s the gap ViVeTool can address.
What the YTECHB article says — succinct summary
- The YTECHB article explains that Windows 11 24H2 and 25H2 include many new features but not all are enabled by default, and suggests using the third‑party utility ViVeTool to force-enable those features locally.
- It gives a short step-by-step for obtaining ViVeTool (download the ZIP, extract, run Command Prompt as Administrator, CD into the ViVeTool folder) and then running the one-line toggle:
vivetool /enable /id:57048226. After a restart, many 24H2/25H2 features should appear. The article warns that some features remain hardware- or license-gated (for example, Copilot+ NPU-only features).
- The YTECHB post lists visible 25H2 highlights (notification‑center clock, a new Edit app, AI Actions in File Explorer, repositionable on-screen indicators, taskbar “End Task” shortcuts, Passkeys integration) and recaps the 24H2 features (Paint AI tools, Energy Saver, sudo support) while noting Copilot+ exclusive capabilities (Recall, enhanced video-call effects, AI upscaling for games, Click to Do).
This article expands that examination: it verifies key technical claims against Microsoft documentation and independent reporting, shows safe step-by-step instructions, explains what ViVeTool can and cannot do, and analyzes the privacy, stability, and enterprise risks of toggling staged features.
What ViVeTool does, and why it works
ViVeTool is an open-source command-line utility widely used by Windows enthusiasts to manipulate Windows’ local feature management state (feature flags / experiment gates). It writes the expected feature-state entries so the OS treats a feature as enabled locally when its binary is already present. ViVeTool is not a Microsoft product; it is community-maintained and is distributed from its GitHub repository. Key mechanics:
- Microsoft ships many feature binaries via monthly LCUs (cumulative updates) and enablement packages; the visible experience is controlled by feature flags and server-side gating.
- ViVeTool operates on local feature configuration, so it can unlock features whose binaries are already present on disk but are locally disabled.
- ViVeTool cannot (and does not) bypass server-side hardware checks, licensing, or cloud entitlements. If a feature requires a Copilot+ NPU or a Microsoft 365/Copilot license, ViVeTool cannot conjure the missing hardware or subscription.
Verify first: required updates and build checks
Before attempting any local flag changes, confirm these prerequisites — they’re essential:
- Confirm you have the servicing updates that delivered the 24H2/25H2 binaries. Microsoft’s September 29, 2025 non-security update (KB5065789) is the canonical reference for many of the 24H2/25H2 toggles and improvements; the KB lists affected builds (for example builds in the 26100.xxxx / 26200.xxxx series). Check Settings → Windows Update or run winver to verify your build.
- If your device is still on an older servicing baseline, ViVeTool will have no effect (the flags refer to absent binaries). Apply all pending cumulative/servicing stack updates first.
- Backup before you change anything. Create a system restore point, an image, or at minimum a tested file backup and, if applicable, your BitLocker recovery key. Community guides and enterprise advisories uniformly recommend backups because toggling in-development flags has non-zero risk.
Step-by-step: how to safely enable the new 24H2/25H2 features (verified workflow)
- Confirm Windows build:
- Press Win + R, type
winver, Enter. Record the OS build number shown.
- Confirm you have the September/October 2025 servicing updates (for example the KB5065789 preview and related monthly updates). Microsoft documents these in the KB notes.
- Download ViVeTool only from trusted sources:
- Use the official GitHub releases page for ViVeTool or the project’s confirmed download pages. Pick the release that matches your CPU architecture (x64 vs ARM64). The GitHub release history shows current releases and assets.
- Extract ViVeTool:
- Unzip into a folder you control (for example
C:\Vive), note the full path.
- Open an elevated console:
- Press Win + R → type
cmd → press Ctrl + Shift + Enter to open Command Prompt as Administrator (or open Windows Terminal as Admin).
- Change to the ViVeTool folder:
- Example:
cd /d C:\Vive
- Run the single-line enable command (the one commonly circulated and tested across community guides):
vivetool /enable /id:57048226- Wait for the command to complete; ViVeTool will report the change.
- Restart the PC:
- Reboot and sign back in. Some features may require a sign-out/sign-in or a short period for the UI to surface changes.
- To revert if needed:
vivetool /disable /id:57048226 then restart, or run vivetool /fullreset to remove custom toggles. Always reboot after changing feature flags.
Why this sequence? Community testing and independent step-by-step guides confirm the requirement to be on the correct servicing build and to reboot after flipping flags; the KB and independent reporting align with this sequence.
Exactly what that ViVeTool toggle exposes (what you can expect)
The group toggle commonly referenced with ID
57048226 is a broad “priority” or group switch that exposes a large set of incremental features introduced across 24H2 and 25H2. Typical visible items after flipping that toggle (where allowed by device/region/licensing) include:
- Notification Center improvements: show the full time/clock on the Notification Center (including on secondary monitors).
- File Explorer “AI Actions” context menu: right‑click image files to see Visual Search, Blur background (Photos), Erase objects (Photos), Remove background (Paint), and Summarize for Microsoft 365 files stored in OneDrive/SharePoint (requires appropriate licensing).
- New “Edit” app (a lightweight text editor/command-line style app).
- Reposition on‑screen hardware indicators for brightness/volume/airplane mode (Bottom Center, Top Left, Top Center).
- Taskbar “End Task” option by right‑clicking an open app (toggle in Settings → System → Advanced).
- Passkeys integration and Passkey management under Settings → Accounts → Passkeys.
- Settings app improvements (a redesigned Advanced page replacing “For Developers”, Git integration hints, and better time/language controls).
Important caveat: some high-privilege or AI-on-device experiences (for example
Recall, Studio effects that require on-device neural processing, AI upscaling in games, and low-latency Click to Do behavior) remain
hardware- and license-gated and will not become fully functional just because you flip the local flag. ViVeTool cannot emulate a missing NPU or Microsoft Copilot entitlement.
Cross-checks and verifications (what was checked and where)
- The KB entry for the September 29, 2025 update (KB5065789) lists many of the same features discussed above and explicitly calls out staged rollout, Click to Do improvements, Passkeys plugin support, repositionable indicators, and Notification Center visibility on secondary monitors — confirming Microsoft’s official position.
- Independent outlets including Windows Central and The Verge summarize the enablement-package model and highlight that 25H2 is primarily an activation/visibility update for binaries delivered via servicing — aligning with the YTECHB description of features being present but not always enabled.
- Community documentation and multiple Windows enthusiast reports validate the ViVeTool command and the ID
57048226 as a common group toggle to surface many staged features — but community sources also warn that correct servicing builds are a prerequisite and that server-side gating still applies.
Where claims are provisional: discussions about exact NPU performance thresholds (commonly cited as ~40+ TOPS) and exactly which Copilot+ features require which NPU capabilities are described in community reporting and Microsoft messaging in general terms; the precise hardware certification thresholds should be treated as provisionally reported unless you consult specific Microsoft hardware certification documentation for Copilot+ PCs. Mark those claims as
provisional.
Risks, privacy, and enterprise considerations
Enabling staged features with ViVeTool is not the same as joining an Insider ring, but it carries trade-offs:
- Stability risk: experimental or server‑staged features may still be receiving A/B testing or backend rollout changes. While many feature flag flips are harmless, there is a non-zero chance of UI quirks or regressions. Always backup first.
- Security and support: ViVeTool is third‑party. Download from the official GitHub releases to avoid tampered binaries. Enterprises should avoid unauthorized local toggles on managed endpoints because it can create support inconsistencies and complicate management.
- Privacy concerns: features like Recall (which stores encrypted local snapshots of screen content for searchability) are opt‑in and Microsoft describes local encryption and Windows Hello gating; however, organizations must evaluate governance, data residency, and compliance implications before enabling such features broadly. ViVeTool cannot alter server-side retention or telemetry policies.
- Licensing: Copilot-powered summarization and some File Explorer AI actions rely on Microsoft 365/Copilot entitlements for full functionality. ViVeTool can reveal the UI, but it can’t grant subscriptions. Expect degraded or cloud‑only behavior if entitlements are missing.
Enterprise deployment guidance:
- Pilot, validate drivers (GPU/PNP/NPU), and test critical workflows on representative hardware.
- Keep the servicing stack and SSUs current to reduce servicing failure risk.
- Document any local toggles and ensure they are fully reversible (ViVeTool’s
/disable and /fullreset are the reversions).
Practical tips, troubleshooting, and safe rollback
- If
vivetool /enable /id:57048226 appears to do nothing: check winver and confirm required KBs are installed; the toggle only affects features whose binaries are present.
- If contextual AI actions show UI but display “requires license” or “not available on this device”: that indicates server/hardware licensing gating — stop; toggling further won’t restore missing entitlements.
- To list current ViVeTool toggles and status, use ViVeTool’s
/query or vivetool /query functionality (see the GitHub release notes and README). Use /fullreset to clear any manual overrides if you encounter unexpected behavior after changes.
Final verdict — should you enable everything?
There is no single right answer: for hobbyists and testers who want to see the latest UI polish and client-side AI tooling immediately on a personal machine, using ViVeTool after verifying builds and backing up is a practical, commonly used approach. For managed environments, IT pros should treat ViVeTool as a troubleshooting/testing tool, not a production deployment mechanism. The benefits are immediate access and faster hands-on testing; the risks are potential instability, host-level policy drift, and privacy/licensing mismatches.
What to weigh:
- If you rely on the PC for daily productivity and cannot tolerate even small UI regressions, wait for Microsoft’s staged rollout.
- If you are experimenting, validating app compatibility, or writing how‑tos, use ViVeTool in a controlled test image or VM and keep documented steps to revert changes.
Closing summary
Windows 11 versions
24H2 and
25H2 bring a focused set of UX, accessibility, and AI refinements that Microsoft is rolling out in stages. The community tool
ViVeTool can safely surface many of those staged features on fully patched machines by toggling local feature flags — the commonly used command is
vivetool /enable /id:57048226 — but this only works when the required servicing binaries are present and cannot bypass hardware or licensing gating. Always verify build numbers and KBs first, download ViVeTool from the official GitHub releases, back up your system, and understand the privacy and enterprise implications before flipping flags.
If you follow the verified sequence in this article you will minimize risk: confirm your build, grab ViVeTool from GitHub, run the single toggle as an administrator, reboot, and observe. When in doubt, pilot on a non‑critical machine and keep a documented rollback plan.
Source: YTECHB
How to Enable All Features in Windows 11 25H2 and 24H2