Flyoobe, the rapidly evolving Windows 11 out-of-box experience (OOBE) toolkit, reached a major milestone with version 1.10, delivering a built-in Extensions Store, a dedicated view for disabling AI surfaces, and a bottom-based navigation model that streamlines first-boot customization. The update marks the project’s transition from a simple requirements-bypass utility into a polished, scriptable platform for debloating and privacy-hardening Windows 11 before the user ever sees the desktop.

Born from the earlier Flyby11 tool that automated Windows 11 installation on unsupported hardware, Flyoobe now fuses bypass mechanics with a comprehensive customization suite. With Windows 10 support ending in October 2025 and Microsoft layering more telemetry, Copilot prompts, and preinstalled apps into setup, the tool appeals to refurbishers, hobbyists, and privacy-minded users who want granular control from the moment a machine first boots.

What’s New: Extensions Store, AI OOBE View, and UI Polish

A Centralized AI/OOBE Page

Instead of scattering Copilot and AI-related toggles across multiple setup screens, Flyoobe 1.10 consolidates them into a single OOBE view. The page uses improved detection logic to surface AI features—like the Copilot button, Start menu tiles, and background services—and prompts users to decide which to disable before first login. Behind the scenes, Flyoobe applies registry edits, policy toggles, AppX package removals, and scheduled task adjustments. The project is careful to label this as configuration hardening, not permanent binary removal, acknowledging that future Windows updates may re-enable some components.

The Extensions Store

Arguably the most significant addition, the Extensions Store lets third-party developers publish PowerShell scripts that run during or after setup. This opens Flyoobe to a community-driven ecosystem of repeatable automations. Version 1.10 ships with several default extensions:

  • Default Power Plan: Toggle between Balanced, High Performance, or Battery Saver during setup.
  • File Explorer Tweaks: Enable showing file extensions, hidden files, and set “This PC” as the default folder.
  • Post‑setup Cleanup: Wipe temp files, component store leftovers (WinSxS/AppX caches), and update caches to reclaim disk space immediately after installation.
  • Windows 11 Honest Mode: An inspector that enumerates telemetry settings, startup apps, and scheduled tasks, showing exactly what Windows runs in the background.

Gone is the old TreeView layout. Flyoobe 1.10 adopts a modern, wizard-like flow with bottom-based navigation and a prominent “Next” button. The refresh control and naming conventions now mirror Windows styling more closely, reducing friction for users accustomed to Microsoft’s setup panels. A small but practical fix now warns that disabling location services can hide available Wi‑Fi networks during OOBE, since Windows ties Wi‑Fi scanning to location—an example of the polish this release prioritizes.

How Flyoobe’s Bypass and OOBE Mechanics Work

The tool never uses kernel exploits. Instead, it packages well-documented community techniques:

  • Server‑variant setup routing – arranges Windows Setup to run a path historically less strict about TPM, Secure Boot, and CPU checks.
  • LabConfig flags – applies known registry tweaks and LabConfig settings to neutralize the hardware appraiser during upgrades or clean installs.
  • Light media/ISO handling – automates ISO mounting and selective file replacement so installer flows proceed on unsupported machines.

Once Windows is installed, Flyoobe intercepts or replaces portions of the OOBE with its own interface that:

  • Allows creation of a local account without Microsoft account requirements.
  • Lets users choose a default browser, taskbar alignment, and personalization preferences upfront.
  • Presents debloat presets and runs PowerShell extensions before first login completes.

What AI Disable Routines Can—and Cannot—Do

The routines can hide or remove UI surfaces (taskbar icons, Start menu tiles), uninstall specific AppX packages, and set policies that block Copilot and other AI features from appearing. They cannot guarantee that a future cumulative update won’t reintroduce those components or reset policies. The project is explicit: Flyoobe treats AI hardening as an opt‑out configuration, not guaranteed eradication.

Cross‑Checking the Claims: Release Status and AV Detections

Multiple community reports and release notes confirm the 1.10 feature set, but the project’s GitHub repository has a rapid release cadence with both nightly/dev and stable channels. Stable tags sometimes lag behind feature discussions, so users should verify artifacts directly from the official releases page. Some reports reference builds by minor version (e.g., 1.7.x) while others use the 1.10 moniker, reflecting potential channel mismatches.

Antivirus engines frequently flag Flyoobe/Flyby11 executables as PUA/HackTool because the tool modifies Windows setup. The developer has acknowledged these detections and attempted mitigations, but users must expect that Microsoft Defender and other AVs may quarantine the binary. Such heuristics are common for installer/multitool utilities and are not proof of malware, but they do require whitelisting or out‑of‑band verification in controlled environments.

Why Flyoobe Resonates: Integrated, Scriptable, and Transparent

  • Unified workflow – combining bypass, media handling, OOBE customization, and debloat into a single guided tool saves refurbishers and technicians repeated manual steps.
  • Day‑one control – selecting defaults for browser, power plan, Explorer behavior, and removing bloat before first login minimizes post‑install cleanup and surprise telemetry prompts.
  • Scriptable extensibility – the Extensions Store and PowerShell engine enable repeatable, auditable automations for small IT teams or hobbyist fleets.
  • Visibility into AI surfaces – Honest Mode and the dedicated AI OOBE page make it easier to see and decide the fate of telemetry and AI features before users ever interact with them.

Risks and Limitations: What to Weigh Before Using Flyoobe

Security and Update Fragility

Bypassing TPM 2.0 and Secure Boot removes platform protections tied to features like BitLocker key encryption and virtualization‑based security. The device’s security posture changes; some mitigations may be unavailable. Additionally, configuration hardening is reversible—cumulative updates and feature upgrades can reintroduce components or override policies, demanding post‑update revalidation.

AV Heuristics and Trust

Because AV engines flag installer‑modifying tools, users must decide whether to trust and whitelist the binary. The open‑source repository helps, but the behavior still increases attack surface. Always verify checksums, prefer reproducible builds, and test in sandboxed environments.

Bypassing hardware gating isn’t illegal for home users, but it voids vendor support and warranties. Enterprises and regulated environments should never run unsupported configurations on production devices. Flyoobe is best suited for hobbyist, refurbisher, and lab contexts.

Not Permanent AI Removal

The tool’s AI disable routines are pragmatic: they hide and disable, but do not surgically remove core binaries. Think of them as opt‑out hardening, not guaranteed eradication.

Practical Guidance: Before You Run Flyoobe

  1. Back up thoroughly – create a full image backup and ensure you have BitLocker recovery keys if encryption is used.
  2. Test on non‑critical hardware – run Flyoobe on a spare laptop, VM, or cloned drive first to verify driver, virtualization, and security behavior.
  3. Download only from the official repository – prefer stable releases, verify checksums, and avoid third‑party mirrors.
  4. Plan for AV flags – whitelist or install offline; never run on sensitive systems without cryptographic validation.
  5. Maintain a post‑update checklist – after every major Windows update, confirm that AI and debloat changes remain applied and that critical security features are still intact—or accept the new posture.
  • Hobbyist upgrades on older hardware that would otherwise be stranded by Microsoft’s gating.
  • Refurbishers and small tech services needing fast, repeatable day‑one configuration for multiple devices.
  • Privacy‑minded users looking to minimize telemetry and AI surfaces from the first login.
  • Lab or test environments where functionality and parity matter more than vendor support.

Flyoobe is not recommended for enterprise production devices, regulated environments, or machines processing sensitive customer data without a formal risk acceptance and support plan.

What to Watch: Developer and Community Signals

  • Repository health – confirm release tags and inspect assets before deploying. The project’s rapid iteration may mean stable tags lag feature announcements.
  • AV vendor telemetry – monitor whether the developer’s mitigation steps reduce heuristic detections over time.
  • Extension ecosystem growth – the Extensions Store’s value hinges on community contributions. Prefer extensions with clear PowerShell code, documentation, and reviewable source.

Flyoobe 1.10 cements the project’s identity as an all‑in‑one OOBE customization platform. Its Extensions Store and refined AI controls give users unprecedented agency during Windows 11 setup—provided they understand and accept the trade‑offs. For refurbishers, hobbyists, and privacy advocates, the tool delivers tangible productivity and transparency gains. But for any machine where security guarantees and vendor support are non‑negotiable, the safer route remains running Microsoft’s supported hardware stack and sanctioned deployment tools. When wielded with caution, Flyoobe offers a powerful way to reclaim the out‑of‑box experience.