| |

How to Enable Windows 11 May 2026 Update Features Early Using ViveTool (KB5079473)

 

 

 

Windows 11 April 22, 2026 · 5 min read

Unlocking Windows 11 May 2026 Features Early with ViveTool

Microsoft’s gradual rollout model means most users won’t see the May 2026 changes until weeks after release. Here’s how to force-enable them today using a single command-line tool.

Microsoft is preparing to ship the Windows 11 May 2026 Security Update (KB5079473, build 26200.8313) on May 12, 2026, targeting both the 25H2 and 24H2 release trains. While the patch is already accessible via the Release Preview Channel, the company’s staged deployment strategy means the feature payload will be gated for most devices — sometimes for weeks after the initial rollout date.

For engineers, power users, and developers who want deterministic access to platform changes before they arrive automatically, the open-source utility ViveTool exposes Microsoft’s internal A/B feature flag system. With a single command, you can flip the entire May 2026 feature set on — or roll it back if something misbehaves.

TL;DR: Install KB5079473, run vivetool /enable /id:58989070 in an elevated Command Prompt, and reboot. Full instructions below.

What’s shipping in May 2026

This update is heavier than a typical Patch Tuesday. Beyond the standard security fixes, Microsoft is landing several user-visible and system-level changes:

Xbox Mode for PC

A dedicated gaming overlay and resource allocation mode previously restricted to console hardware.

File Explorer: Preview Anyway

Removes the “this file may be dangerous” friction gate when previewing content downloaded from the web.

Haptic Feedback API

New haptic effects system with support for precision touchpads and compatible peripheral devices.

Drop Tray

A persistent staging area in the shell for transferring content between apps without clipboard gymnastics.

Taskbar AI Agent

Exposes an AI agent entry point directly from the Taskbar, expanding on the existing Copilot integration.

Debloat Policy & Driver Updates

New MDM/GPO policies for suppressing pre-installed apps, plus a revised driver signing enforcement model.

Understanding the flag system

Windows ships features in a compiled-but-disabled state. The deployment infrastructure — internally referred to as “experimentation” or “flights” — controls which feature IDs are activated per device based on criteria like region, hardware profile, and telemetry tier. ViveTool communicates with the same FeatureManagement API surface that the OS uses internally, allowing local overrides that persist across reboots.

The ID 58989070 is an umbrella flag that enables the cluster of features associated with build 26200.8313. Individual sub-features may have their own IDs — the community repository at @PhantomOfEarth on X tracks these as they’re discovered via binary diffing of preview builds.

Note: Feature IDs are ephemeral. Once Microsoft fully ships a feature, its associated ID is retired from the flag registry and the ViveTool command becomes a no-op. IDs also change between preview builds. The ID documented here targets build 26200.8313 specifically.

Prerequisites

Before running ViveTool, your device needs to be on the correct build. You have two paths:

Option A — Stable Channel (after May 12): Open Settings → Windows Update and install KB5079473 when it appears. Optionally enable “Get the latest updates as soon as they’re available” to accelerate delivery.

Option B — Release Preview Channel (now): Enroll your device in the Windows Insider Release Preview ring via Settings → Windows Update → Windows Insider Program. This gives access to the update immediately without waiting for the production rollout gate.

Step-by-step: enabling May 2026 features

  1. Navigate to the ViveTool GitHub releases page at github.com/thebookisclosed/ViVe/releases and download the latest ViveTool-vx.x.x.zip.

  2. Extract the archive to a stable path — avoid the Downloads folder or any path with spaces. Something like C:\Tools\ViveTool\ works well.

  3. Open Command Prompt as Administrator (search for cmd, right-click → Run as administrator). PowerShell works equally well.

  4. Navigate to the extraction directory:

cmd
 
 
 
# Replace with your actual extraction path
cd C:\Tools\ViveTool\ViveTool-v0.3.3
  1. Run the enable command with the May 2026 feature flag ID:

cmd
 
 
 
vivetool /enable /id:58989070

# Expected output:
# Successfully set feature configuration(s)
# Feature ID: 58989070 | Enabled: True
  1. Restart your machine. The flag writes to the registry immediately, but the feature host processes need a fresh boot to pick up the new configuration.

Rolling back

If a feature causes instability — or you simply want to revert to the default Microsoft-managed state — ViveTool provides two rollback paths:

cmd
 
 
 
# Disable the specific May 2026 flag:
vivetool /disable /id:58989070

# Or reset ALL ViveTool customizations to Microsoft defaults:
vivetool /fullreset

The /fullreset command is the safer nuclear option — it clears every flag you’ve manually set and returns feature management entirely to the OS telemetry pipeline. Useful if you’ve accumulated overrides across multiple update cycles and want a clean slate.


Frequently asked questions

Will all May 2026 features be enabled by running this command?
Not necessarily. Some features are region-gated at the server level and cannot be enabled locally via ViveTool. Others require specific hardware (e.g., NPU for AI features) or are controlled by additional sub-flags not exposed by the umbrella ID.
Is this safe to run on a production machine?
ViveTool only writes to Windows feature flag registry keys — it doesn’t modify system binaries or driver state. That said, pre-release features are inherently less stable than shipped ones. Running this on a secondary device or a VM first is a reasonable precaution.
Do these flags survive Windows Updates?
Manual ViveTool flags persist across cumulative updates until you run /fullreset or until Microsoft’s own deployment infrastructure pushes a conflicting configuration. Once a feature is fully shipped, Microsoft’s flags take precedence and the manual override becomes irrelevant.
Where can I find IDs for individual sub-features?
The community maintains a running list via @PhantomOfEarth on X and in the ViveTool GitHub discussions. The Pureinfotech ViveTool codes page also aggregates known IDs by update cycle.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *