← All guides AI Release RU Subscribe to @ai_release1

How to Enable Hidden Windows 11 Features Early with ViVeTool

Updated: 12.11.2026 · AI Release · @ai_release1

TL;DR

Time: 20–30 minutes, including one reboot and a restore-point check.
Difficulty: Intermediate.
Requires: Windows 11, an administrator PowerShell window, a ViVeTool release for your CPU architecture, a feature ID from the release notes or a trusted tracker for your exact build, and a System Restore checkpoint.

The /enable command is the easy part. The checks most guides omit are: whether your build already contains the feature code, whether the feature ID matches that build, and whether you can roll back cleanly. A feature flag is a hidden on/off switch in Windows code; ViVeTool changes the switch, but it cannot add code that is not already present.

Requirements and setup

Windows 11 with a known build number. Feature flags are build-specific; do not assume an ID from another build will work.
Administrator rights. ViVeTool changes system configuration and normally needs an elevated prompt.
ViVeTool extracted to a local folder, for example C:\Users\<you>\Downloads\ViVeTool\ViVeTool.exe.
The target feature ID. The source material for this guide does not provide feature IDs, so use <feature-id> as a placeholder and replace it with an ID from the release notes or a trusted tracker for your exact build.
System Protection enabled, or permission to create a restore point.
Enough free space for the archive, extracted files, and a restore point. Check with Get-PSDrive C.

Create a checkpoint before changing anything:

Enable-ComputerRestore -Drive "C:\"
Checkpoint-Computer -Description "Before ViVeTool" -RestorePointType MODIFY_SETTINGS
Get-ComputerRestorePoint | Select-Object -Last 1

Example: the last command should return a recent entry with Description : Before ViVeTool. If System Protection is disabled by policy, the checkpoint command fails; stop and fix that first.

If the feature depends on a Windows update that has not arrived, install the update first. The manual catalog procedure is covered in Step-by-Step: How to Install a Windows 11 Security Update Manually via Microsoft Update Catalog.

Step 1. Record the build, architecture, and rollback baseline

What to do: open an administrator PowerShell window and save the OS build, architecture, and your feature-ID worksheet before running ViVeTool.

Why: feature IDs are tied to specific Windows builds. If the ID does not exist in your build, /enable may report success while nothing changes. The baseline also tells you what to restore if the feature causes instability.

How to check: confirm that the output contains WindowsProductName, OsBuildNumber, and OsArchitecture, and that the baseline file exists on your Desktop.

$baseline = "$env:USERPROFILE\Desktop\vive-baseline.txt"
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber, OsArchitecture | Tee-Object -FilePath $baseline
[System.Runtime.InteropServices.RuntimeInformation]::OSArchitecture | Tee-Object -FilePath $baseline -Append

Expected output has this shape:

WindowsProductName : Windows 11 ...
WindowsVersion     : <version>
OsBuildNumber      : <build-number>
OsArchitecture     : <architecture>

Example: if OsArchitecture returns X64, use the x64 ViVeTool build; if it returns Arm64, use the ARM64 build. Do not mix them.

Record the experiment in a small worksheet:

Item	Example value	Why it matters
Feature ID	`<feature-id>`	Must match the build
Build before	`<build-number>`	Rollback reference
ViVeTool SHA256	`<sha256>`	Integrity check
Result after reboot	`Enabled` or `No change`	Keep-or-rollback decision

Checklist before continuing:

[ ] Build number saved to vive-baseline.txt
[ ] CPU architecture confirmed
[ ] Feature ID recorded with its source
[ ] Restore point visible in Get-ComputerRestorePoint
[ ] No other feature IDs are being changed in the same test

Step 2. Stage ViVeTool and enable one feature flag

What to do: extract ViVeTool, verify the executable hash, query the feature ID, and enable that single ID from an elevated PowerShell window.

Why: one ID at a time keeps the result attributable. If you enable several IDs and the UI breaks, you cannot tell which flag caused it. Querying first also proves the ID exists in your build before you change state.

How to check: Get-FileHash must match the hash published with your ViVeTool release, \/query must show the feature ID, and \/enable should print a success message such as Successfully set feature configuration(s).

$work = "$env:USERPROFILE\Downloads\ViVeTool"
New-Item -ItemType Directory -Path $work -Force
Expand-Archive -LiteralPath "$env:USERPROFILE\Downloads\ViVeTool.zip" -DestinationPath $work -Force
Set-Location $work
Get-ChildItem
Get-FileHash .\ViVeTool.exe -Algorithm SHA256

Example: Get-ChildItem shows ViVeTool.exe; Get-FileHash returns a SHA256 value. Compare it with the value on the release page. If it differs, delete the folder and download again.

Open an elevated window:

Start-Process powershell -Verb RunAs

In the elevated window, query before enabling:

Set-Location "$env:USERPROFILE\Downloads\ViVeTool"
.\ViVeTool.exe /query /id:<feature-id>
.\ViVeTool.exe /query > "$env:USERPROFILE\Desktop\vive-before.txt"
.\ViVeTool.exe /enable /id:<feature-id>

Example: replace <feature-id> with a value such as the ID listed for your build in the release notes. Do not copy an ID from an unrelated build. If /query /id:<feature-id> returns no matching feature, stop; the ID is wrong for this build.

Reboot so the flag is loaded at startup:

Restart-Computer

Step 3. Reboot, verify state, and check visible behavior

What to do: after reboot, query the same feature ID again and then check the Windows UI or app behavior that the flag is supposed to change.

Why: ViVeTool state and visible behavior are two different checks. A flag can show Enabled while the UI remains unchanged because another dependency, a server-side experiment, or an app update is missing. That is the “where this does NOT work” case most guides skip.

How to check: the query should show the feature ID with an enabled state; the target UI should show the new control or behavior after a short wait and, when relevant, a sign-out or second reboot.

Set-Location "$env:USERPROFILE\Downloads\ViVeTool"
.\ViVeTool.exe /query /id:<feature-id> | Select-String -Pattern "Enabled|State|Feature"

Example: a successful query returns a line containing the feature ID and an enabled state. Then open the relevant Settings page or app. If the control is absent, do not enable more IDs blindly; use the decision table below.

Query result	Visible result	Action
State shows enabled	Feature appears	Keep it; record the build and ID
State shows enabled	Feature absent	Check dependencies, app version, and server-side gating; then disable
No matching feature	Not applicable	Wrong build or wrong ID; stop and re-check the source

If the feature does not appear and you do not need it, roll back immediately:

.\ViVeTool.exe /disable /id:<feature-id>
Restart-Computer

Example: after /disable, the same /query /id:<feature-id> should show the feature as disabled or no longer active. If it does not, restore the checkpoint from Step 1.

Troubleshooting

Problem. PowerShell cannot find ViVeTool

Error: The term 'ViVeTool.exe' is not recognized as the name of a cmdlet, function, script file, or operable program.
Cause: PowerShell does not run executables from the current folder unless you prefix them with .\, or you are in the wrong directory.
Solution: change to the extracted folder and run the explicit path:

Set-Location "$env:USERPROFILE\Downloads\ViVeTool"
.\ViVeTool.exe /query

Problem. The enable command fails with access denied

Error: Access is denied
Cause: the PowerShell window is not elevated, so ViVeTool cannot write the feature configuration.
Solution: open an administrator window and verify elevation before retrying:

([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)

The command must return True. If it returns False, close the window and start PowerShell with Run as administrator.

Problem. SmartScreen blocks the downloaded executable

Error: Windows protected your PC and Microsoft Defender SmartScreen prevented an unrecognized app from starting.
Cause: the downloaded archive has Mark-of-the-Web, so Windows treats the extracted executable as untrusted.
Solution: verify the SHA256 hash first. If it matches the release page, unblock the file and retry; do not disable SmartScreen globally:

Unblock-File -Path .\ViVeTool.exe
Get-FileHash .\ViVeTool.exe -Algorithm SHA256

Summary and next steps

Enable one feature ID at a time, record the build and hash, and keep the matching /disable command ready for rollback. If you are cleaning up a test machine after the experiment, apply the same staged approach to ads, telemetry, and AI features with How to disable ads, telemetry and AI features in Windows 11.

FAQ

Does ViVeTool add features that are not installed?

No. It changes flags that already exist in the Windows build. If the code is absent, the flag cannot make the feature appear.

Can I use any feature ID I find online?

No. Feature IDs are build-specific and can change. Use only IDs tied to your exact build from release notes or a trusted tracker; this source does not provide feature IDs.

Why did /enable succeed but the UI is unchanged?

The flag may depend on another flag, an app update, specific hardware, or a server-side experiment controlled by Microsoft. Disable the ID and verify the dependency list before retrying.

How do I undo the change?

Run .\ViVeTool.exe /disable /id:<feature-id> and reboot. If the system is unstable, restore the checkpoint created in Step 1.

🤖 AI summary

AI Release Knowledge Layer
Machine-readable description · Version 1.0

Status: practical guide. Some statements come from vendors; verify in your environment.

1. Summary

Time: 20–30 minutes, including one reboot and a restore-point check. Difficulty: Intermediate.

Inside: direct answers, key facts, entities, context, reliability, unknowns and sources.

Machine data: Citation Map JSON · JSON-LD · Semantic Embeddings — separate stage.

Full Knowledge Layer: sections 2–8

2. Direct answers

What is required?: Windows 11 with a known build number. Feature flags are build-specific; do not assume an ID from another build will work.; Administrator rights. ViVeTool changes system configuration and normally needs an elevated prompt.; ViVeTool extracted to a local folder, for example… → details (AR-GUIDE-POSHAGOVOE-003)
How to do it?: Step 1. Record the build, architecture, and rollback baseline → Step 2. Stage ViVeTool and enable one feature flag → Step 3. Reboot, verify state, and check visible behavior → details (AR-GUIDE-POSHAGOVOE-004)
Which topics does it cover?: vivevtool как пользоваться, включить скрытые функции windows 11, vivevtool скачать windows 11, экспериментальные функции windows 11 включить, vivevtool feature id → details (AR-GUIDE-POSHAGOVOE-002)
What are the key points?: Time: 20–30 minutes, including one reboot and a restore-point check. Difficulty: Intermediate. → details (AR-GUIDE-POSHAGOVOE-007)

3. Key facts

Time: 20–30 minutes, including one reboot and a restore-point check. — evidence; status: заявление источника.
Difficulty: Intermediate. — evidence; status: заявление источника.
Requires: Windows 11, an administrator PowerShell window, a ViVeTool release for your CPU architecture, a feature ID from the release notes or a trusted tracker for your exact build, and a System Restore checkpoint. — evidence; status: заявление источника.
Windows 11 with a known build number. Feature flags are build-specific; do not assume an ID from another build will work. — evidence; status: заявление источника.
Administrator rights. ViVeTool changes system configuration and normally needs an elevated prompt. — evidence; status: заявление источника.
ViVeTool extracted to a local folder, for example C:\Users\<you>\Downloads\ViVeTool\ViVeTool.exe. — evidence; status: заявление источника.

4. Entities

Entity	Type	Role
vivevtool как пользоваться	тема/инструмент	упоминается в заголовке, TL;DR или разделах гайда
включить скрытые функции windows 11	продукт/модель	упоминается в заголовке, TL;DR или разделах гайда
vivevtool скачать windows 11	продукт/модель	упоминается в заголовке, TL;DR или разделах гайда
экспериментальные функции windows 11 включить	продукт/модель	упоминается в заголовке, TL;DR или разделах гайда
vivevtool feature id	тема/инструмент	упоминается в заголовке, TL;DR или разделах гайда
Windows	платформа/технология	упоминается в заголовке, TL;DR или разделах гайда

5. Context

Guide — describes → How to Enable Hidden Windows 11 Features Early with ViVeTool (AR-GUIDE-POSHAGOVOE-001).
Guide — includes step → Step 1. Record the build, architecture, and rollback baseline (AR-GUIDE-POSHAGOVOE-001).

6. Reliability

Confirmed

No independent confirmation is provided; source claims and editorial conclusions are separated below.

Source claims

Product features, versions, prices and limits come from vendors and the guide.
Commands and steps are recommendations, not guaranteed results.

AI Release analysis

Structure, comparison and selection criteria are editorial.
The guide does not replace an independent audit or legal advice.

7. Unknowns

Current versions, prices and limits.
Independent benchmarks and quality checks.
Terms of use and data policy.

8. Sources

Source	Type	Role
No external links	—	—

Cite as: AI Release. Пошаговое руководство: как включить скрытые функции Windows 11 заранее с помощью ViVeTool. ai-release.org.