ViVeTool GUI is a modern, user-friendly graphical interface for managing hidden Windows features in Insider Preview builds. It provides an intuitive way to enable, disable, and search for features without requiring command-line expertise.
Key Highlights:
- π― Simple button-based feature management
- π Powerful search and filtering capabilities
- π Modern UI with light/dark/system theme support (WPF)
- βοΈ Advanced feature scanning and discovery tools
- π Community-maintained feature lists
- Windows Version: Windows 10 Build 18963 (Version 2004) or newer
- WPF Version (.NET 9): Recommended for latest features and Windows 11 Fluent design
- WinForms Version (.NET Framework 4.8): Legacy support for older systems
- Download the latest release from GitHub Releases
- Run the executable (no installation required)
- Select your Windows build
- Start managing features
- Select your Windows build from the dropdown
- Wait for the feature list to load
- Expand feature groups by clicking the arrow
- Select the feature you want to modify
- Click "Perform Action" and choose your desired action
- Click "Manually change a Feature"
- Enter a Feature ID
- Click "Perform Action" and select your action
- Enable/Disable Features - Easily toggle hidden Windows features on and off
- Search & Filter - Quickly find features by name, ID, or description
- Feature Organization - Group features by:
- Always Enabled
- Always Disabled
- Enabled by Default
- Disabled by Default
- Modifiable
- Smart Sorting - Sort by feature name, ID, or current state
- Clipboard Integration - Right-click to copy feature names and IDs
- Multi-Build Support - Load feature lists for different Windows builds
- Theme Customization - Dark, light, and system mode support
- Feature Scanner - Scan your Windows build to discover hidden features
- FAQ.md - Frequently asked questions and answers (50+ topics)
- TROUBLESHOOTING.md - Step-by-step problem solving guide
- KNOWN_ISSUES.md - Known limitations and workarounds
- CHANGELOG.md - Version history and release notes
- DEVELOPMENT.md - Development setup, architecture, and contribution guidelines
- CODE_ANALYSIS.md - NEW Comprehensive WPF vs Legacy analysis with roadmap
- WPF_ISSUES_QUICK_FIX.md - NEW Quick action items with ready-to-use code examples
- building.md - Build instructions and compilation guide
Modern Features:
- β Windows 11 Fluent Design - Native Windows 11 UI with accent color integration
- β ThemeMode API - System theme detection and integration
- β Modern .NET Runtime - Better performance and security updates
- β Enhanced Accessibility - Improved keyboard navigation and screen reader support
- β Smart Feature Feed Caching - ETag-based caching with offline fallback
- β Feature Scanner Integration - Built-in discovery tools for new features
- β GitHub Actions Publishing - Direct feature list publishing for maintainers
Not Implemented:
- β Store/A/B Testing repair tools (planned for next release)
- β Multi-language localization (planned for next release)
Recommended For:
- Windows 11 users
- Users wanting the latest UI/UX improvements
- Advanced feature scanning needs
- Active Insider program participants
Capabilities:
- β Core feature enable/disable functionality
- β Search and filtering
- β Feature grouping and sorting
- β Basic theme support (Windows default)
- β Multi-build feature list loading
- β Multi-language localization support
- β Store/A/B Testing repair tools
- β LastKnownGood Store fixing capabilities
Recommended For:
- Windows 10 users
- Users needing store repair functionality
- Users requiring multi-language support
- Legacy system compatibility
| Feature | WPF Version | Legacy WinForms |
|---|---|---|
| UI Framework | Windows 11 Fluent | Classic WinForms |
| Theme Support | Light/Dark/System | Windows Default |
| Multi-Language Support | β | β |
| Store Repair Tools | β | β |
| A/B Testing Fix | β | β |
| Feature Scanner | β Advanced | |
| Smart Caching | β ETag-based | |
| GitHub Publishing | β Native | β |
| Keyboard Accessibility | β Enhanced | |
| Performance | β Modern .NET 9 | |
| Windows 10 Support | β Works | β Optimized |
| Windows 11 Support | β Optimized | β Works |
Use WPF if you:
- Are on Windows 11
- Want the latest UI/UX improvements
- Don't need store repair functionality
- Want GitHub feature publishing
Use Legacy (WinForms) if you:
- Are on Windows 10
- Need store repair functionality
- Require multi-language support
- Prefer the classic interface
- Need backward compatibility
If you're currently using the Legacy WinForms version, see MIGRATION_NOTES.md for detailed migration instructions to the new WPF version.
ViVeTool GUI uses a GitHub-hosted feature feed to provide current feature lists for supported Windows builds.
- latest.json - Metadata about available builds and latest build numbers
- features/{build}/features.csv or features.json - Per-build feature lists
The application automatically fetches feature lists from the feed with:
- Smart Caching - Minimizes bandwidth usage
- Offline Fallback - Uses cached data when network is unavailable
- Legacy Support - Falls back to mach2 format for older builds
For Power Users & Maintainers:
- Launch the Feature Scanner from the main application
- Run a complete scan of your Windows build
- Click "Publish via GitHub Actions" in the publish panel
- Provide your build number, select format (CSV/JSON), and authenticate
- Your feature list is automatically committed to the repository
Note: Publishing requires maintainer permissions. Contact repository maintainers if you encounter 403 errors.
Compared to the command-line ViVeTool, ViVeTool GUI offers:
| Feature | CLI ViVeTool | ViVeTool GUI |
|---|---|---|
| User-Friendly UI | β | β |
| Feature Search | β Full-featured | |
| One-Click Actions | β | β |
| Modern Theme Support | β | β (WPF) |
| Feature Scanning | β Advanced |
ViVeTool-GUI/
βββ ViVeTool-GUI.Wpf/ # Modern WPF application (recommended)
βββ ViVeTool-GUI.FeatureScanner/ # Feature discovery and scanning tools
βββ Albacore.ViVe/ # ViVe API wrapper and core functionality
βββ vivetool-gui/ # Legacy WinForms version
βββ lib/ # External dependencies
βββ images/ # UI screenshots and icons
βββ MIGRATION_NOTES.md # WPF migration guide
βββ building.md # Build instructions
For detailed build instructions, see building.md.
Quick Start:
git clone https://github.com/mta1124-1629472/ViVeTool-GUI.git
cd ViVeTool-GUI
dotnet build -c Release- Ensure you're connected to the internet (first-time setup)
- Check that your Windows build number is supported
- Try clearing the local cache and restarting
- See TROUBLESHOOTING.md for detailed help
- Run ViVeTool GUI as Administrator
- Ensure your user account has sufficient privileges
- Check Windows Defender or antivirus software isn't blocking the app
- See TROUBLESHOOTING.md for more solutions
Check FAQ.md, TROUBLESHOOTING.md, or KNOWN_ISSUES.md for comprehensive guidance.
No oneβincluding the ViVeTool GUI creators, the ViVeTool developers, or the mach2 creatorsβis responsible for any damage or unintended side effects resulting from feature modifications. Always create a system restore point before making changes.
Built With:
- ViVeTool - Core feature management API
- mach2 - Feature scanning and legacy data
- icons8.com - UI icons
Special Thanks:
- PeterStrick - Original ViVe GUI creator
- The Book Is Closed - ViVeTool & ViVe authors
- Rivera - mach2 developer
ViVeTool GUI is open source. See LICENSE for details.
- Discord Server: Join our community
- Issue Tracker: GitHub Issues
- Discussions: GitHub Discussions
- Code Quality: SonarCloud Analysis
Contributions are welcome! Whether it's:
- π Bug reports and fixes
- β¨ Feature suggestions and implementation
- π Documentation improvements
See our guidelines in DEVELOPMENT.md and building.md for more information.
Want to help with WPF improvements? Start with CODE_ANALYSIS.md and WPF_ISSUES_QUICK_FIX.md for priority issues and ready-to-use code.
Made with β€οΈ for Windows power users and Insider testers