Mebolt.Release status
DOCUMENTATION

Understand first.
Tune second.

A practical guide to the current development scope, prerequisites and the twelve Mebolt workspaces.

Getting started—when the release is ready.

Mebolt is not yet available as a verified public installer. These instructions describe the intended review-first workflow; they are not an invitation to run unsigned development binaries.

  1. Use the official release page to check availability, requirements, signature and checksum.
  2. Read the release notes and back up important data independently.
  3. Launch the app and inspect the system without applying changes.
  4. Create and verify the mandatory safety baseline.
  5. Review one supported action, understand its trade-off and measure the result.
  6. Revert a change when it does not improve your actual workload.

Requirements and optional integrations.

The current target is x64 Windows 10/11 with the x64 .NET 8 Windows Desktop Runtime. Privileged operations need administrator access. Feature availability depends on the operating-system build, policies, hardware and driver support.

PresentMon capture needs an external compatible executable with explicit hash pinning. Sensor and ETW integrations are optional. Missing sensors, drivers or unsupported APIs must be reported as unavailable, not substituted with invented readings.

No Chromium runtime, Electron shell or browser engine is part of the native Windows UI architecture. Resource usage must still be measured under representative real workloads; no fixed RAM or CPU guarantee is published.

Measure changes that matter.

  1. Use the same game scene, settings, resolution and background workload.
  2. Warm up the workload consistently; do not compare a cold shader cache with a warm one.
  3. Record a baseline, change one factor and repeat the same capture duration.
  4. Compare frame-time consistency and low-percentile performance, not just average FPS.
  5. Repeat runs. Consider heat, battery life, stability and normal run-to-run variation.
  6. Keep a change only when the evidence supports it for your workload.

Telemetry capture itself has overhead. Diagnostic sessions are not proof that background resource-budget targets are met during normal gaming. The charts on the homepage are explicitly illustrative, not benchmark evidence.

The 12 workspaces.

The descriptions below explain the implementation scope and important limitations. They do not certify that every feature is supported on every PC.

01

Command Center

Bring live system information and the safety baseline into one place before reviewing any optimization.

  • CPU, memory and kernel timer visibility
  • Mandatory verified baseline before supported mutations
  • Reviewed optimization profiles with explicit outcomes
Before you use it. Temperature and driver-level metrics depend on supported sensors. Missing data is shown as unavailable, never estimated.
02

Game Sentinel

Detect game processes, organize per-game settings and investigate bottlenecks without turning every suggestion into an automatic system change.

  • Event-driven process detection and game profiles
  • Optional PresentMon capture with a hash-pinned external tool
  • Advisory bottleneck classification and benchmark comparison
Before you use it. PresentMon is not bundled. Frame-time capture requires a separately obtained, verified compatible executable. Auto-pilot recommendations are advisory.
03

CPU & Scheduling

Inspect processor topology and review process rules for workloads that benefit from deliberate scheduling.

  • Logical processor and core topology inspection
  • Per-process priority, affinity and power-throttling controls
  • Persistent rule and background balancing workflows
Before you use it. Hybrid cores, processor groups and cache topology vary by hardware. Affinity changes can reduce performance; benchmark each workload.
04

Power & Performance

Review Windows power plans and supported processor power settings with a clear view of the trade-offs.

  • Active power scheme inspection and backup
  • Custom plan and supported hidden-setting controls
  • Battery-aware and thermal-sensitive profile decisions
Before you use it. Aggressive idle and power settings can increase heat, fan noise and battery use. The automatic Extreme Overclock preset is blocked.
05

Memory & Storage

Inspect memory and storage state before deciding whether a maintenance action is appropriate.

  • Memory list and working-set inspection workflows
  • Threshold-based standby-list management controls
  • TRIM and BypassIO / DirectStorage diagnostics
Before you use it. Clearing useful caches can make the next load slower. Storage operations are capability-gated and are not a universal FPS improvement.
06

Interrupts & Input

Inspect PCI device interrupt settings, affinity policy and supported input-related options in one hardware-focused workspace.

  • PCI device and MSI configuration inspection
  • Interrupt affinity and timer-resolution controls
  • USB and input power-management review
Before you use it. Driver support is device-specific. Unsupported interrupt changes may prevent a device from working and can require reboot or recovery.
07

Graphics & Display

Review Windows graphics options, driver capability information and shader-cache maintenance without assuming every switch is a win.

  • HAGS, MPO and per-game display setting workflows
  • Supported GPU and driver information
  • Reviewed shader-cache cleanup
Before you use it. Driver features differ across vendors and versions. Cache cleanup can cause temporary shader-recompilation stutter. No universal GPU boost is promised.
08

Network Lab

Compare DNS responses, investigate adapter configuration and review supported network changes against a saved baseline.

  • Concurrent DNS benchmarking and resolver comparison
  • Adapter, MTU and TCP/IP diagnostic workflows
  • Reviewed QoS, reset and configuration actions
Before you use it. DNS response time is not game-server latency. DSCP is a packet marking, not a guarantee that an ISP or router will prioritize traffic.
09

Cleanup & Startup

Bring startup entries, scheduled tasks, service dependencies and cleanup candidates into an inspectable workflow.

  • Startup and scheduled-task visibility
  • Dependency-aware service review
  • Scoped cleanup with previews and locked-file skipping
Before you use it. Deleted temporary files are not generally recoverable through a registry rollback. Review the cleanup scope and keep a separate backup of important files.
10

Audio & Latency

Connect audio-related configuration and optional tracing workflows when diagnosing crackles, pops or inconsistent response.

  • MMCSS configuration review
  • Audio device and power-management inspection
  • Optional ETW-based latency investigation
Before you use it. Audio latency depends on drivers, interfaces and buffer settings. Tracing adds overhead and is opt-in; configuration changes do not guarantee a fix.
11

Security & Compatibility

Inspect virtualization-based security and installed anti-cheat indicators before considering sensitive configuration changes.

  • VBS and Memory Integrity state inspection
  • Known anti-cheat installation indicators
  • Explicit security trade-off and restart warnings
Before you use it. Disabling security features reduces protection and may break a game or anti-cheat. Detection is not a certification of compatibility.
12

Focus & Recovery

Review background-app suspension, profile sharing and rollback records with an independent recovery workflow.

  • Explicitly selected background-app suspension
  • Independent Watchdog recovery and emergency hotkey
  • Rollback history and shareable profile files
Before you use it. Suspending an application can interrupt downloads, voice calls or unsaved workflows. A restore point is not a full disk backup or a recovery guarantee.

Current limitations.

  • The public distribution, signing and final release-verification workflow is not complete.
  • Mutation and recovery success paths need further testing in disposable Windows environments.
  • Game auto-pilot is advisory, not an unrestricted autonomous optimizer.
  • Extreme Overclock automatic execution remains blocked.
  • Vendor APIs, third-party tools and some hardware telemetry require optional setup.
  • No blanket anti-cheat compatibility, FPS gain or fixed resource budget is claimed.
Development notes