Flyoobe 1.40: Debloat Windows 11 OOBE and suppress Copilot at install

Flyoobe 1.40 lands as a single, opinionated utility that claims to remove Windows 11 bloatware — including the newly prominent Copilot AI surfaces — at install time while still offering the legacy Flyby11 capability to bypass Microsoft’s hardware checks for unsupported PCs.

Background / Overview​

Windows 11’s growing on-device AI features and heavier Out‑Of‑Box Experience (OOBE) have pushed a portion of the Windows community to build tools that let users choose a leaner first-boot experience. Flyoobe started life as the small, pragmatic Flyby11 bypass helper and has been expanded and rebranded into a modular OOBE/debloat and installer orchestrator by developer builtbybel. The project’s public release notes and community reporting show Flyoobe now bundles two historically separate capabilities: an installer-bypass assistant (the Flyby11 lineage) and a feature-rich OOBE/debloat toolkit that runs during or immediately after setup.
Version 1.40 is a notable milestone in that evolution. The release adds a pre‑emptive cleanup or “no‑AI from first boot” flow that enumerates OOBE apps and system components and gives the installer the option to disable or uninstall them before the user ever signs in. The developer describes this as a way to avoid the messy, often incomplete job of post‑install debloaters and to keep AI surfaces like Copilot from becoming persistent parts of the experience. Independent coverage and the project’s release notes corroborate this direction.
This article summarizes the 1.40 changes, explains how Flyoobe performs its actions, evaluates the risks and trade‑offs, and offers practical guidance for technicians and enthusiasts considering the tool for refurbishing machines or personal installs.

---

What’s new in Flyoobe 1.40​

Key headline features​

• A new pre‑installation cleanup (OOBE AI discovery) that lists OOBE apps and AI surfaces — including Copilot exposures — and offers options to disable or remove them during installation rather than after first boot. This is the core differentiator called out by reviews and the release notes.
• Consolidation of Winpilot/Autopilot‑style provisioning into Flyoobe’s UI, making guided, one‑click upgrade and provisioning flows available alongside the classic three‑step upgrade. The project’s marketing and changelog emphasize a smoother, more discoverable OOBE workflow and a rebranding that highlights the “OOBE” purpose.
• Expanded debloat presets and modular profiles that run at setup time. Flyoobe structures choices into four main presets that match common needs:
• Minimal — remove obvious advertising/promotional components only.
• Full — remove most consumer inbox apps (Teams, OneDrive, Microsoft Store, etc.) for an ultra‑lean footprint.
• Gaming — disable background services and free resources for gaming.
• Privacy — aggressively disable telemetry and synchronization services.
• Better ISO handling and provider model (Rufus, Ventoy, Media Creation Tool integration) plus improved extension/PowerShell hooks to automate provisioning at scale — features that aim squarely at refurbishers and technicians who image many devices.

Packaging and distribution notes​

Flyoobe is distributed as a portable executable (ZIP) and uses official Windows ISOs where possible rather than shipping repacked images. The project integrates common community scripts for ISO acquisition, reducing the supply‑chain risk associated with third‑party rehosts. The 1.40 release also adjusts the executable branding to emphasize FlyOOBE and merges companion tools into the main app for a single‑tool workflow.

---

How Flyoobe removes Copilot and other “AI” surfaces — the technical picture​

What the tool actually does​

Flyoobe’s approach to disabling or removing Copilot is a configuration and package orchestration strategy rather than a binary surgical removal. The tool executes a combination of:

• Pre‑OOBE and OOBE automation: registry edits, Group Policy flips, PowerShell scripts, and Appx package unprovisioning executed during setup or immediately after OOBE. These actions suppress UI elements (Copilot taskbar entry, Copilot discovery pages), deregister packages and disable services.
• Appx/unprovision operations: Flyoobe can unprovision inbox packages or prevent them from being re‑provisioned in the currently deployed user images. This reduces the immediate presence of Copilot UI and similar inboxed apps.
• Installer routing: The utility uses an alternate setup path (historically a Windows Server style install or LabConfig flags and light ISO/media steering) to run Setup in a way that allows executing those automation steps before the first interactive sign‑in. That timing is central — removing components before first login avoids re‑provisioning behavior that sometimes occurs during OOBE.

What Flyoobe does not (and cannot) guarantee​

• Flyoobe’s routines are not a binary‑level excision of every AI‑related file or a kernel modification. They operate at the configuration and package level. As such, Microsoft feature updates or cumulative updates can and do reintroduce removed components, re‑provision inbox apps, or reset default policies; users should expect to re‑apply some tweaks after major feature updates. The project and independent testing both make this point explicit.
• Some CPU or platform constraints (instruction set requirements like POPCNT, SSE4.2, etc.) are hardware‑level and cannot be bypassed by Flyoobe’s installer routing; those failures are separate from Copilot removal but are an important cross‑cutting limitation of unsupported installs.

---

The Flyoobe presets: how much Windows can you shave off at setup?​

Flyoobe gives users a menu of presets that reflect different risk/comfort profiles. Each preset is an opinionated combination of package removals, policy flips, and telemetry toggles.

• Minimal
• Removes promotional frames and obvious advertising bloat. Low risk, preserves most inbox apps and features.
• Full
• Strips major inbox apps (Teams, OneDrive, sometimes the Microsoft Store) and many consumer services. High impact: creates a very small surface area but increases the chance of missing functionality and software incompatibility with consumer workflows.
• Gaming
• Disables background synchronization, cloud reminders, and non‑essential services to free CPU/Disk/IO for games. Moderate risk.
• Privacy
• Aggressively disables telemetry, synchronization, and online account nudges; attempts to minimize outbound telemetry and integrated cloud features. Highest impact on modern Windows features and some Microsoft services.

These presets are useful for quickly producing repeatable images for a given purpose (refurbishers, kiosks, gaming rigs), but each is ultimately a convenience layer over the same underlying automation. The changes are reversible in many cases but not without manual effort if something critical was removed by mistake.

---

Bypass + Debloat — the double‑edged design​

Why combining bypass and debloat matters​

Flyoobe merges two previously separate workflows — bypassing Microsoft’s installer checks and removing OOBE bloat — into a single screen‑led flow. That makes sense operationally: technicians who refurbish older hardware want to both get the OS installed (even when TPM/Secure Boot are absent) and to ship a minimal system to end users without having to run separate post‑install scripts. Several independent articles and hands‑on tests document that Flyoobe automates ISO acquisition, routing to alternate Setup flows, and OOBE automation.

The risks of combining the two​

• Support and update uncertainty
  Microsoft explicitly warns that installing Windows 11 on unsupported hardware is not recommended and that such devices may not receive future fixes or updates in the same way as supported devices. Bypassing those checks can work in the short term, but there is no long‑term guarantee that Microsoft won’t change Setup behavior or update signing that would render the bypass ineffective. Official guidance on Windows 10 end of support reinforces the safer path: upgrade to supported hardware or enroll in Extended Security Updates.
• Security posture
  Bypassing TPM and Secure Boot removes or circumvents foundational hardware‑rooted features that underpin several modern security primitives (device encryption keys, measured boot, Secure Boot protections). That means even if the OS runs, certain protections and features will be lacking. Flyoobe does not create a hardware TPM nor replicate those cryptographic assurances.
• Potential for breakage after updates
  Because Flyoobe’s debloat is largely package/unprovision and configuration edits, Microsoft servicing or feature updates can reinstall Copilot or re‑enable AI surfaces. That’s not a failing of Flyoobe so much as a consequence of choosing configuration‑level suppression rather than deep binary rewrites. Expect maintenance when Microsoft ships large updates.
• Driver & performance instability
  Older machines often lack vendor support for newer kernel features in Windows 11. The act of installing a modern OS on legacy hardware can expose driver gaps, performance regressions, or missing firmware features. Flyoobe can’t invent drivers or silicon features.

---

Cross‑checking the claims — independent verification​

• The Flyoobe GitHub releases and README describe the shift from Flyby11 to Flyoobe and detail the combination of bypass, OOBE controls, and debloat tools. The release notes are the authoritative project source for what Flyoobe does and how it’s distributed.
• Mainstream tech coverage (Windows Central and other outlets) independently reports Flyoobe’s role as a bypass + debloat tool and confirms recent feature additions around AI and OOBE control. That independent reporting aligns with the project changelog and community write‑ups.
• Community forums and technical digests consistently emphasize that Flyoobe uses documented installer routing techniques (Server variant setup, LabConfig flags) rather than kernel exploits — important context for trust and auditability. Multiple community summaries also warn about update fragility and hardware limits (e.g., CPU instruction checks). Those community signals corroborate both the utility and the trade‑offs.

When referring to the most load‑bearing factual claims — that Flyoobe can disable Copilot at OOBE and that it supports bypassing TPM/Secure Boot checks — at least two independent sources (project release notes + mainstream coverage/community writeups) corroborate the statement. That satisfies a basic cross‑check requirement while still leaving room for real‑world variability on unsupported hardware.

---

Practical guidance and recommended workflows​

If you intend to use Flyoobe 1.40 in your toolbox, follow conservative practices to limit risk:

• Back up everything first: create a full disk image or system image before attempting an unsupported upgrade.
• Test in a VM or disposable machine: run the entire Flyoobe flow on a virtual machine to validate the chosen preset and extension scripts before moving to a production device.
• Choose presets deliberately: start with Minimal on unfamiliar hardware; move to Full only when you understand the consequences for store/apps/drivers.
• Maintain a recovery plan: keep Windows 10 recovery media and a clean official Windows 11 ISO handy in case you need to revert or perform a repair.
• Expect maintenance: after major feature updates, verify whether Copilot or inbox apps were reinstalled and be prepared to reapply deltas or run updated Flyoobe extensions.
• Avoid critical production systems: do not use unsupported installs on machines that must retain enterprise support, compliance, or guaranteed update behavior.

---

Strengths — what Flyoobe does well​

• Convenience and consolidation: One GUI for ISO acquisition, bypass routing, OOBE control, debloat presets, and extension scripting. That reduces human error in mass imaging workflows.
• Day‑one control: Removing unwanted first‑boot nudges before a user ever signs in avoids the psychological and usability burden of “try this” and “buy that” onboarding screens. Flyoobe’s OOBE timing is a genuine advantage for consistent deployments.
• Open‑source transparency: The project’s public repository and release notes make auditing possible and lower supply‑chain risk relative to repackaged ISOs distributed elsewhere.
• Profiles and repeatability: Scriptable extensions and GitHub‑loadable debloat profiles make Flyoobe useful for refurbishers and small IT teams who need reproducible baseline images.

---

Weaknesses and unresolved concerns​

• No guarantee of permanence: Because the tool operates at the configuration and package level, Microsoft servicing may reintroduce removed components, requiring periodic maintenance. This is the single largest practical limitation.
• Support and update risk: Unsupported installs may not receive the same update guarantees; Microsoft’s official guidance remains that installing Windows 11 on unsupported hardware is not recommended. Users must accept that updates, security patches, and future compatibility can be uncertain.
• Security trade‑offs: Bypassing TPM/Secure Boot leaves the device without hardware‑rooted protections. For many users, that is a meaningful security downgrade. Flyoobe’s utility does not and cannot mitigate hardware deficiencies.
• Potential AV/heuristics flags: Community reports have shown that some of Flyoobe’s early preview builds triggered heuristics in antivirus engines due to networked extension downloads. The developer has addressed specific false positives, but admins should always validate downloads in their environment.

---

When Flyoobe makes sense — and when it doesn’t​

Flyoobe is well suited to:

• Enthusiasts and technicians refurbishing older machines for personal or internal use who accept the trade‑offs around support and security.
• Small labs that need repeatable, minimal images and prefer to remove Copilot and telemetry at OOBE.
• Users with disposable or non‑production devices who want a cleaner, privacy‑leaner first‑boot experience without crafting custom unattend files manually.

Flyoobe is not recommended for:

• Production laptops or enterprise devices that require vendor support, guaranteed update compliance, or hardware security assurances.
• Users who lack strong backups or recovery plans and are uncomfortable troubleshooting driver or update issues on older hardware.

---

Final assessment​

Flyoobe 1.40 marks a pragmatic evolution from a single‑purpose bypass script to a full OOBE orchestration and debloat suite. Its ability to remove Copilot and other first‑boot AI nudges during installation — rather than chasing them afterward — is a meaningful convenience for privacy‑minded users and technicians. At the same time, the tool’s design highlights the fundamental trade‑off: convenience and control versus formal vendor support and hardware‑rooted security.
The product’s strengths are operational: streamlined workflows, repeatable presets, and transparent reliance on official ISOs and documented installer routing. The product’s limitations are structural: configuration‑level suppression (not permanent binary removal), update fragility, and the security implications of bypassing platform protections. Both sets of facts are well documented by the project release notes and independent coverage, so the choice to use Flyoobe is ultimately a matter of informed risk management rather than blind convenience.
For technicians and advanced users who understand the risks and maintain robust backup and update practices, Flyoobe 1.40 is a powerful and time‑saving tool to produce a lean Windows 11 image from first boot. For everyone else — especially machines that require long‑term vendor support or rigorous security guarantees — the safer path remains upgrading to supported hardware or enrolling in official Extended Security Updates.

---

Conclusion: Flyoobe 1.40 sharpens a well‑worn community argument — that users should have choice and control over what ships on first boot — and packages that choice into a single, auditable tool. Its innovations around OOBE‑time Copilot suppression are effective in the short term and undeniably useful for scaleable imaging workflows, but they do not eliminate the longer‑term obligations of keeping the system secure and up to date on hardware not designed for Windows 11. Use with care, prepare to maintain, and always verify critical claims on the exact hardware and Windows build you intend to deploy.

---

Source: Notebookcheck Windows 11 debloat: Flyoobe 1.40 removes bloatware and Microsoft Copilot directly during installation