New Update Flyoobe (formerly Flyby11)

Flyoobe (Flyby11) version 1.21

What’s new​

  • The new design guideline has been refined again to better fit into the Windows 11 ecosystem. Many smaller bugs have been fixed, and this part is now already out of Preview.
    (Dark mode is not available yet – I still need to decide whether to slightly dim the whole UI or allow a proper switch. This will take a bit more time.)
  • The patch functionality for unsupported hardware – the true legacy of the original Flyby11 – was once fully integrated into Flyoobe. It has now been decoupled as a separate process to keep the EXE smaller..
    The patch option has of course not disappeared – it has been simplified even further and now lives on as Flyby11, both inside and outside the app ;) Flyby11 can no longer be started standalone. It can only be launched directly as a process from Flyoobe unless you use the totally professional flag "Flyby11.exe --f-u-tpm" (The file Flyby11.exe is located in the app folder of Flyoobe)
    (Yes, that' exactly what you think it means. I love you, TPM… not.) Check out the intro video!
 
Flyoobe version 1.22

What’s new​

  • Streamlined the Bee-UI to make it lighter, faster, and more responsive
  • Updated the Upgrade Bypass Assistant (Flyby11.exe helper, now v3.12) with interactive help shown as soon as actions are triggered, one of the most requested features. Bonus: there’s also the totally professional command line flag
    Flyby11.exe --f-u-tpm
    (Yes, thats exactly what you think it means. I love you, TPM… not.)
  • Updated CpuCheckNative.dll to improve hardware requirements detection
  • Fixed a critical DPI scaling issue at 125% where navigation bar fonts appeared pixelated and oversized
  • Improved the AI feature toggle for smoother control
  • Improved the offline account bypass for a more seamless setup
  • Improved the Extension Store with better stability and integration
  • Expanded detection of unwanted apps to remove even more clutter
  • Code further simplified, optimized, and refactored. If you know me, you know I'm a minimalist (This build comes from a separate branch with the new Bee-UI.
    The code has not yet been merged into the main GitHub branch)

Note on Flyby11 Classic​

Flyby11 Classic is becoming outdated and will no longer be promoted in future GitHub releases.
Since I'm no longer maintaining the Classic version and with mounting issues around ISO mounting and hardware checks I strongly recommend switching to Flyoobe. Flyoobe performs the same checks internally (so you won't even notice them), and inside Flyoobe > app you'll find the updated Flyby11.exe v3.12.
This version can either be launched standalone with the parameter mentioned above, or directly from within Flyoobe.
 
Flyoobe version 1.23

What’s new​

  • Added support for Windows 11 25H2 (app now runs smoothly on the new release)
  • New extension script to upgrade to Windows 11 25H2 via the enablement package (with info, compatibility check and download options). This is an optional helper for users who prefer a simple way to activate 25H2 as many systems are already ready for the update without requiring a full ISO upgrade. The script can be found under (Setup) Extensions > Windows 11 25H2 Enablement Package or by searching for it
  • Setup extensions improved: script output can now be viewed in the internal log window
  • UI refinements: new Flyoobe icon added to the main UI (top left), click opens app info & settings
  • Extension management moved into the More menu (top right) for easier access
 
Flyoobe v1.24

What’s new​


Sprint 21: Codename Loki / Wingman Mode

This sprint is focused on the internal OOBE pages: refined, extended, and with Loki finally unlocked for general use.
As a result, features that were previously hidden behind my own test flags are now live. Existing OOBE pages have been significantly enhanced, not newly introduced.

  • New, vibrant "Bee Fly-Through" app icon with thin honeycomb lines
  • Improved Startsite, Real Default Browser Setter, More powerful extensions, Instant Debloater, Copilot Reality Check, Privacy Scanner, and OOBE Replay now ship with broader coverage, better defaults, and a smoother flow
  • The Windows 11 25H2 enablement package is now better integrated. Activation is simpler and more prominently surfaced in the Dashboard
  • The extensions area has been upgraded and many scripts reworked
  • Finalized placement of the App/Settings entry: it now lives in the right-hand More menu, with an improved presentation
  • Updated Flyoobe's internal Upgrade Assistant (Flyby11)
  • Improved live log viewing during extension processing
  • UI subtly optimized again (font smoothing)
 
Flyoobe v1.25

What’s new​


  • OOBE optimized further for Windows 11 25H2, with extended "debloat" routines targeting AI components, bundled apps, and the overall user experience
  • Navigation now starts with a lightweight Windows 10–style flow focused on upgrades or reinstalls; once switched to Windows 11, the full OOBE navigation is unlocked
  • General UI optimizations and improved color harmony across all OOBE panels. Unlike the Windows 11 OOBE, which leverages WebView2 to render its HTML/CSS/JS-based interface, this app is fully native, so no Webview2 engine, no Chromium layer, just pure system-level rendering. Yet some users still say it feels suspiciously webby 😄
  • Added a navigation collapse feature so the main panel can now go full-screen via the toggle button next to the "More" menu
  • Improved notification area for better clarity and consistency
  • Core integration of PowerShell extensions optimized for faster and cleaner execution
  • Added "Windows Update Tamer" extension, a new tool to manage Windows 11 updates directly from Flyoobe. It allows pausing or resuming updates, disabling automatic updates, setting an extended pause period (up to 10 years), and restoring default behavior
 
Flyoobe v1.30

What’s new​

  • New clean and logical menu structure following Microsoft’s UI guidelines. The navigation is now divided into Install Operating System and Setup Operating System. Flyoobe is growing up
  • Added a Winpilot button next to the Flyoobe branding in the ToolStrip menu. Winpilot acts as an intelligent setup assistant that guides the user and offers help during the process. If the name sounds familiar, yes, it's my old project. Winpilot now lives on inside Flyoobe as the local version of what Windows Autopilot does in the cloud. Automated setup might become a bigger topic in the future.
  • Improved Extension integration in the navigation under “Finalize Setup” Extensions are now organized by category, and the Post-Setup section is its own dedicated extensions group
  • Fixed a network OOBE bug where more than one network could be marked as connected
  • Fixed an installer issue that could prevent some apps from installing correctly
  • Fixed two small DPI scaling issues.
  • Removed several test flags used for Nightly builds
    (The next Nightly is coming soon)
  • Various small UI fixes and layout adjustments
  • Minor efficiency improvements and smoother navigation
 
Flyoobe v1.31

What’s new in 1.31​

  • The OOBE installer has been improved and expanded. It’s now possible to manually search and install app packages directly from the Winget manifest using the new “Install custom Winget package” option. The feature is a bit more barebones than UnigetUI, but intentionally lightweight to keep Flyoobe fast and efficient as it covers everything essential.
  • Leveled up the Apps OOBE page (Debloater) and upgraded both the backend and UI for easier navigation, lightning-fast app removal, and smarter batch operations
  • The navigation system introduced in version 1.30 has been refined, especially the way menus expand, collapse, and guide the user through the interface.
  • The OOBE “Personalization” page has been visually polished for a cleaner and more consistent look.
  • A new log and activity manager has been added, accessible from the “More (⋯)” menu in the top-right corner. It allows you to monitor all Flyoobe operations and notifications in one place. Next to it, the Settings and About App buttons are now separated into their own dedicated menus
  • Cleaned up the Experience OOBE page and removed the "Issues" section, since it's now partially covered by the Extensions and Installer OOBE
  • The predecessor Flyby11, on which this app was originally based a few versions ago, is no longer being promoted here.
    Everything Flyby11 could do is now fully integrated into Flyoobe, which I highly recommend switching to as its far more stable during the upgrade process. The Flyby11.exe still exists within Flyoobe as a native helper and background process.
    However, if you prefer the slightly lighter version of Flyby11 (with fewer options), you can still find it in the previous FlyOOBE releases
  • Minor fixes and improvements
 
Flyoobe v1.40

What’s new in 1.40​

  • Completely reimagined the UpgradeOOBE / Flyby11 process (the Upgrade in FlyOOBE step) and expanded it with AutoPilot features.
    You can now either perform the upgrade manually in three simple steps (choose download source, import ISO, set advanced options) or just hit the new AutoPilot button
    , which guides you through the entire upgrade automatically. One click, one smooth upgrade. It's never been easier. 😉
  • The app name is now officially written as FlyOOBE for better clarity and trust
    Writing OOBE (Out-of-Box Experience) in uppercase makes the acronym instantly recognizable.
    "Fly" + "OOBE" looks balanced and professional, while Flyoobe tended to blur visually.
    With the capitalized version, more people naturally read it as "fly-oo-bee" and not flaiohb? 😆 The app binary now ships as FlyOOBE instead of Flyo.exe “You can spell the name freely. For marketing and external use we stick to FlyOOBE (OOBE in caps) to make the Out-of-Box Experience explicit
  • Winpilot is becoming part of FlyOOBE. I'm merging Winpilot into FlyOOBE as a native module and will keep iterating on it. Going forward, Winpilot will live as an integrated FlyOOBE module and continue to evolve.
    In short: FlyOOBE is Winpilot. Winpilot is FlyOOBE. Note: Windows Autopilot = Microsoft thing, not mine 😉
  • Minor fixes and improvements
 
FlyOOBE v1.41

What’s new in 1.41​

  • Previously, the upgrade process (Flyby11) only worked on CPUs that passed the compatibility check. You can now delete CpuCheckNative.dll from the app folder to skip the CPU check - proceed at your own risk. The CPU check is always performed by FlyOOBE during the upgrade, but there are cases where skipping it is also supported.
  • The update check has been completely redesigned and moved to GitHub Pages. This setup will also allow to offer helpful guides and additional documentation there in the future
  • Fixed an issue where the Installer OOBE Page didn’t properly update the progress bar during app installation
  • Fixed a bug where the Apps OOBE Page (Debloater) didn’t correctly reflect progress while uninstalling apps
  • Several input dialog windows have been redesigned and improved-
  • Updated Bloatware and installer signatures
  • Minot fixes and improvements

Do you prefer the classic Windows-style GUIs and dialog windows without all the modern fancy stuff, the "golden middle ground", modern meets classic (which is where FlyOOBE currently sits), or the latest Microsoft design language with WinUI, Fluent, and all the modern polish?

Vote here

 
FlyOOBE v1.42

What's new in 1.42​

  • Split the upgrade tool out
    • FlyOOBE was tightly coupled with the upgrade/bypass tool Flyby11 (aka UpgradeOOBE). I’ve completely detached UpgradeOOBE (the Windows 10 → 11 migration assistant) from FlyOOBE
    • FlyOOBE now focuses 100% on customizing Windows 11
    • UpgradeOOBE (Flyby11) focuses only on upgrading to Windows 11 and runs as a standalone app
    • Safety-first separation: Due to false positives from security tools, this split was the obvious next step. If Microsoft or other AV solutions ever flag something again, only UpgradeOOBE can be affected. FlyOOBE will remain untouched. Currently there are no detections and FlyOOBE is not classified as harmful or a hack tool.
  • Community input
    • I’m running a poll about FlyOOBE’s future design direction.
    • Even though WinUI + Windows App SDK would blow up the app size (a WinUI build would be ~333× larger than the current WinForms app), I'll keep the poll open and continue iterating on the current version.
  • Modernization & polish
    • The current release got a UI refresh and new features
    • You can now pick a background image (see intro video)
    • Brand-new App Settings view
    • Improved update process
    • Reinstall OOBE page renamed to Advanced
    • Menu reorganized and simplified
  • UpgradeOOBE (Flyby11) specifics
    • Fully standalone, does not require FlyOOBE (and vice versa)
    • Depends only on CpuCheckNative.dll, which can be removed to allow upgrade attempts on unsupported CPUs (SSE4.2 still required in practice)
  • Under the hood
    • Large-scale code refactors
    • Prep work for more extensive OOBE pages
    • UI and navigation tweaks to make things cleaner and more intuitive
  • Future considerations
    • Possible FlyOOBE Lite edition that ships without the Extensions/Scripts folder by default — PowerShell scripts are commonly abused by fileless malware, so a light build could be safer for some users.
    • Potential option to download official scripts on demand from GitHub (like a mini store), rather than bundling them.
 
FlyOOBE v1.50

What's new in 1.50​

  • Background rendering rework: The background selection feature introduced in the previous version has been reworked for better performance and stability.
    You can now select a background style via Settings > Pick background
    The old image-based handler was replaced with an internal gradient-based renderer.
    This removes issues with locked image files, unreleased GDI objects, and redundant event handlers.
    The update significantly reduces memory usage and improves rendering speed and overall UI responsiveness
  • Added support for script-driven input fields for the Extensions engine via # Input: true and # InputPlaceholder: Uses positional args for maximum compatibility, with optional console / silent / log host modes, status + progress, and a clean placeholder UX.
  • New Extension script: ViVeTool Bridge
    Wrapper to enable/disable/query hidden Windows features by ID. Supports comma-separated ID lists
  • New Extension script: Ninite Bulk Installer
    Builds the Ninite bundle URL from app slugs/names, downloads to Desktop (predictable filename), and launches Installer
  • New Extension script: Winget Bulk Installer
    Quickly installs multiple packages in one run (IDs separated by space/comma/newline)
  • Online Update Checker redesigned in full retro style, think Windows 2000 meets GameBoy
  • Updated Extensions docs
 
FlyOOBE v1.51

What's new in 1.51​

  • The extensions system has been improved again. The PowerShell-based engine has been expanded, and Flyby11 (UpgradeOOBE.exe) is now included as a native extension within FlyOOBE. On Windows 10 systems, a dedicated upgrade tile will appear on the home dashboard, allowing users to launch the Windows 11 upgrade workflow directly, with help instructions included
  • Extensions now also display their author or source, such as Flyby11 by Belim or the ViVeTool-bridge by Albacore. This adds transparency and helps users understand where each tool originates from. This feature will be expanded further in future updates, and developers who wish to share their own scripts or tools will be able to integrate them into FlyOOBE more easily.
  • Updated Extensions docs
  • This update improves FlyOOBE’s behavior on some high-resolution displays. Several UI scaling issues on 4K screens and Windows scaling levels above 200% have been fixed. Elements such as tiles, layout spacing, and navigation now scale consistently and no longer overlap.
 

FlyOOBE v2.0 Preview – New UI Overhaul​


I'm currently working on FlyOOBE 2.0 (Preview), featuring a completely redesigned interface focused on simplicity and clarity.
While FlyOOBE originally started as a pure OOBE setup assistant, it has steadily evolved into a flexible customization and modding toolkit.
Through extensions and user-created modules, FlyOOBE is becoming a kind of all-in-one Windows 11 control and enhancement hub – lightweight, extensible, and built for power users and casual users alike.
The new UI is more streamlined, less overwhelming, and makes the initial setup flow much easier for new or casual users.
What’s new in the UI:
  • Reduced complexity with fewer menus and visual clutter
  • Cleaner layout with more breathing room
  • Clear primary actions to keep guidance obvious
  • Less text, more direction, less cognitive overload
  • Overall a much friendlier first-time setup experience
  • This matters, because an OOBE assistant should be something you can complete without prior knowledge or technical experience.
 
FlyOOBE – Preview 2.0.740
Preview Notice
This build is an early preview of FlyOOBE v2.0.
Features, UI, and functionality are work in progress and may change.
Expect bugs, incomplete features, and rough edges.
 
FlyOOBE 2.0 (stable)

What's new in 2.0​

  • Modernized and simplified Interface: cleaner, more focused, and less overwhelming, making the initial setup much easier for new and casual users
  • Improved perfomance: The app is faster and more responsive, with reduced loading times and better resource management
  • Extensions engine completely reworked under the hood, now using a new internal filtering system with a category dropdown.
  • A brand-new app icon finally featuring a smart, friendly little bee inside 🐝 (I might've cheated a bit and let AI help with that one 😉)
  • Improved global search and refresh behavior for smoother control updates across views
  • New centralized Home dashboard that intelligently categorizes and recommends OOBE setup pages and extensions. Many items are now discoverable via keyword tags. (The first experimental Copilot integration has been temporarily removed while refined.)
  • Large-scale refactoring and transition to primarily asynchronous processing. Search, filtering, and loading operations no longer cause UI hangs
  • New back navigation system with a full stack-based history, allowing you to rewind through previous pages just like in a browser
  • Extensions shipped with the app can now also be uninstalled just like user-added ones
  • New native activity monitor logs system actions in real time and can provide contextual help for extensions (when supported).
  • Improved UI scaling and clarity on high-DPI displays
  • New indexing system for all OOBE pages and extensions based on metadata, allowing tools like Flyby11 to be found using simple keywords such as ESU, 10, or 11
  • New modern Copilot-inspired designs can now be found in the settings menu
  • Extensions.md has been updated accordingly
  • Dozens of Minor Fixes and Quality Improvements
 
FlyOOBE 2.1

What's new in 2.1​

The UI introduced back in version 2.0 has now been fully finalized and cleaned up once more. The main form hasn’t looked this polished in a long time. You can now seamlessly switch between the OOBE and Extensions.

Going forward, the focus will shift even more toward Extensions, so a clean UI arrives at just the right time.
  • Several debloating/cleanup modules have been bumped to a higher tier and now dig up even more (and even deeper) AI-infused junk. Still no AgenticOS takeover in sight- but with Microsoft’s latest moves… let’s just say: enjoy the peace while it lasts
  • Memory usage reduced even further
  • Fixed various DPI-related issues
  • Optimized extension loading
  • Extensive code refactoring
    The full source code for v2 will be pushed soon